i became a professional programmer when i was 20, not-quite 38 years ago.
bob martin’s back-of-the-envelope estimate of the doubling rate for programmers is that it’s been about 5 years for at least 3 decades. that means i have more time in this trade than more than 99% of the other programmers in the world today.
what does that mean about me? idunno, really. a bunch of things.
- it means i’m a bitter old man, of course. even if we put a pleasant face on it, surely the least one could say is that i am skeptical by default stance.
- it means i’ve failed more often to ship on time and under budget than any 20 random geeks you know. also succeeded more than them.
- it means i’ve climbed one helluva lotta mount stupids. and by induction, that i’m fighting my way up one now.
- it means i’ve written just about every kind of software there is to write, tho of course the spectral analysis would show lots of imbalances.
- it means i read almost no books on “mere coding” these days. not that i *didn’t*, of course. i’ve read i’m sure hundreds of them, and kept some of them in the bathroom for years at a time.
but mostly, i think, what it means is that i have no patience for over-simplification of what programmers do or should do.
programmers are translators. we translate from the sense made by human language into the sense made by computer language.
our work is fundamentally sociotechnical, inconceivable without the strange fractal border between wildly complex human interaction and rigorously simple mathematical formalism. it requires at different times tremendous sensitivity and crude indifference, patient persistence and an openness to lightning, a taste for the solo and the collaborative, tremendous balanced love for lofty abstraction and gritty detail.
programming for a living is infinitely delightful and exasperating, and i have spent nigh on forty years living the life of the mind in the lap of luxury.
on my good days, i recommend it.