4. I was always programming for fun and intellectual curiosity. That means I was always very much interested in creating a "nice" program as well as solving som

4. I was always programming for fun and intellectual curiosity. That means I was always very much interested in creating a "nice" program as well as solving some problem. And "nice" involves low maintenance, robustness, little external dependencies, understandable, well abstracted and documented code, that is as perfomant as possible given the constraints. Because I did these things mostly for myself, the span of problem domains is big, I did backend web stuff, frontend stuff, CLI tools system daemons, embedded things, game-related things, audio-related things etc. This breadth of topics helps tackling anything my current employer throws at me (which is mostly also interesting problems). This is success to me: I do what I like to do and am able to do it well enough to be happy with the results and I am fast compared to others while doing it. E.g. last week I was asked if I could do a local groupchat webservice for the wifi of a theatre piece (so visitors can interact with the actors on stage, without having to install some kind of internet bound app). Four hours later the working prototype including nice handwritten CSS and realtime message-passing was done. Feels good.