de tomKronieken

Marc is asking me about my new job. Since he's the guy who hired me for my first job (regular readers should hear some bells ringing now -- "whiteboard" and "balloons"), I'll oblige.

First off, read the announcement, and, of course, my description of my ideal job. Add my personal view on time management, and you'll have a pretty good idea of what it is all about.

My official title (I think, I've not yet seen any business cards) is "I.T. Architect". I'm working in the "Architecture & Support" departement of a Java end-user. And that title pretty much describes my job: to help in the architecture of applications, and to support developers when they encounter problems. Other aspects are code reviews (thank God for PMD), guidelines, setting up development environments, selecting frameworks, etc etc. In short, "be supportive".

What I like about it? Especially the short bursts in which everything happens. You get a problem, you help solving it (my most favorite input: to be the cardboard engineer), and you're done. Onto the next problem. No "if I code a little faster today, I will probably have another piece of functionality ready by the end of next month." I happen to like variation.

No rants then? Of course there are. It's incredible how car drivers treat bicycle riders. When starting at a traffic light, they pass you at 10cm next to your steering wheel, just to ... see you ride by on the queue at the next traffic light. Yes, they do get my finger then.

Oh, and yesterday, I fell. Bruised knee and elbow. Damn those wet tram rails.