Software engineer and coder (both tend to be synonymous) with professional experience in python, php/html5/javascript, Adobe extendScript, plus hobbyist experience in many others - I always try to use the right tool for a job instead of insisting on one I know well. I know my way around unixy OS (debian based, RHEL/centOS, OS X).

I'm an autodidact. I don't have a classic computer science education, but always did it as a hobby until I successfully switched carreers.

For you as a possible employer this means ...

I'm the right guy for

• Code pretty much anything for an existing environment, provided I have access to a minimum of documentation and ressources, and the task is sufficently well defined. See my dev story for details.

• Classic software engineering stuff - maintain your servers, dig through logs, write shell scripts, customize existing software, set up your apache environment and so forth.

• See my profile for details.

I'm not the right guy for:

• Software architecture, i.e. plan a new big project's coding/class structure from scratch. I know the concepts behind it, and I've done it for smallish projects, but I wouldn't feel comfortable to promise anything on a professional level.

• Coding on an overly complex mathematical level (graphics engines, cryptography, compression, new network protocols etc). Give me an algorithm and enough time and I will implement it, but I probably won't come up with that algorithm myself. I'm not John Carmack.

• Windows. I can use it obviously, but I never worked with it's API outside of .net things.