phL0w's resume

Mein Studium geht bald zu Ende, wird allerhöchste Zeit dass ich endlich mal nen ordentlichen CV schreibe.

Was ist wichtig für nen guten Resume? * A resume is not a statement of facts. It’s a declaration of intent. * How a programmer reads your resume (comic) * Why I do my résumé in LaTeX * How to Write a Cover Letter that Gets Read by Jason Cohen * Joel Spolsky's Guerilla Guide to Interviewing * klml's CV * How to get a job at Google: Humility

Skills

Projects I did and still like

  • Diploma Thesis: Wireless Mesh Networks

Programming languages (in order of decreasing aptness)

  • ECMA Script (a.k.a. Javascript)
  • Java
  • ANSI C (K&R, '99)
  • Shell scripting (bash, zsh)
  • Python
  • C++
  • PHP
  • LISP
  • x86 assembler
  • Microprogramming

Markup languages

  • HTML & CSS
  • LaTex
  • Markdown

Tools

  • Git
  • Vim
  • Shell scripting
  • Some IntelliJ IDEA
  • IRC
  • LAMP
  • Django
  • Node.js
  • Plone
  • Apache, NGINX, Lighttpd

  • Varnish, Squid

  • PostgreSQL

  • Redis
  • Memcached

  • MongoDB

  • YUI3

  • Backbone
  • Underscore
  • require.js
  • jQuery

Continuous Integration

  • Jenkins
  • TravisCI
  • TeamCity

Operating Systems

  • Linux (Debian & Ubuntu, OpenWRT, Gentoo, Suse, Redhat)
  • BSD (Net, Free, Open)
  • OpenSolaris (ZFS, Zones, too little DTrace. Hopefully some SmartOS sometime?)
  • Windos (from v3.1 onwards)

Geile Selbstwerbungs

Marko Topolnik auf StackOverflow Careers

The greatest thing about my profession is that it is also my dearest hobby. I get the best professional results when I do the job the way I personally enjoy it the most. The saddest thing about my profession is that I can rarely share my passion with people outside it. The beauty of the concepts we wield is usually not something the end user can relate to.

I am most passionate about the fundamental stuff: knowing how to get the last inch out of the standard library, mastering the challenges of concurrent and asynchronous programming, sharpening my awareness of the low-level details such as JIT compiler optimizations and the Garbage Collector.

I insist on having code which speaks for itself, code "optimized for reading" just as much as for performance, reliability and other machine-oriented values. Often when I debug, I take the preliminary step of rewriting code to make more sense. Many times the bugs disappear during this step, even those which hadn't been reported yet.

I love doing projects end-to-end, creating the vision of the end product with the customer and then bringing that vision to reality.