Development part 1

“What do you do?”
“I’m a computer programmer.”

The conversation usually ends there, thankfully. Sometimes it will continue along esoteric technical paths, but mostly it won’t. And that’s the desired effect. Responding “I’m [insert bullshit job title] in IT” will frequently encourage further conversation, but who wants to talk about IT? It’s going to end up in a discussion about a recent Windows problem some poor cunt or other has experienced and needs help with. Apart from not knowing the answer, I just feel depressed that the wonders of technology have become as bollocksed-up as they are now…primarily thanks to Microsoft’s terrible lack of vision. The word “developer” is another way to extend these moribund conversations – avoid it.

But this is all rendered irrelevant by the fact I spend all of my free time writing crap code for my own amusement. If someone were to ask “what would you do with eleventy-squillion dollars?” I would have to say that it would be doing exactly what I already do on the weekends…writing stupid code.

In terms of dayjob, we “developers” spend our entire lives gaining further experience and honing our skills. Tragically there is a “developer culture” that involves reading the same blogs, books, and then discussing how our interpretations are better than yours. In reality we’re actually just getting more experienced, older and sadder.


Leave a Reply