[kristopolous]

Do people here anticipate programming being their lifelong career, or do they in good faith, think there will be a switch later?

Personally, I've done this for 15 years and I keep doing contracting to pay the bills but really I'm pretty done with it.

What about you?

[henrik_w]

I've been programming professionally for close to 25 years, still love it.

Reasons I (still) love it: http://henrikwarne.com/2012/06/02/why-i-love-coding/

Why I think it is a good career (even if you are older): http://henrikwarne.com/2014/12/08/5-reasons-why-software-dev...

Why programming experience is valuable: http://henrikwarne.com/2014/12/15/programmer-knowledge/

[reidrac]

I've been doing this for ~15 years too, but things have changed enough over the time (and I've changed too!) so it still feels fresh.

I guess the way technology changes can be a two edge sword, as in you're always catching up, but so far I can't say I'm bored or thinking on doing anything else to pay my bills.

[wobbleblob]

Yeah, that was my thought. If you're still a programmer at age 50, either something has gone very wrong in your career development, or you're such a legend in the field that it would be a loss to the world if you had moved on.

[vidarh]

Or you enjoy what you're doing.

I've had "director" or "head of" or similar in my titles for the majority of the last 20 years, but I keep finding excuses to code because it's what I enjoy doing the most. Whenever my job responsibilities doesn't let me code, I spend more time coding at home.

I'm 40 now, and I can't see that changing. I first started programming when I was 5 years old, and it's an integral, important part of my life.

[arethuza]

Same here - I've had CTO, Director of Engineering, Head of Architecture posts for the last 20 years at everything from start-ups to multinationals and I still keep my hand in investigating bugs (i.e. looking at code and databases) and writing code, most of the latter in my own time.

I wouldn't want a role that had no "hands on" element - personally if you don't occasionally get your hands dirty and stay current with current technology then your capability to make sensible high level decisions decays pretty rapidly.

[Toenex]

Same here. Mid 40's now with a PhD so I'm 'overqualified' as well as 'getting on a bit' if someone really doesn't want to pay for me!

For the last decade I've been in small start-ups where you wear many hats, Head of this, VP of that. However, even when I'm focusing on business development I'll probably find a way to cut some code. "I could use MS Access for this. Hmmm maybe a better idea would be to write some python and plug the data into an sqlite dB instead" - is usually how my brain works.

[wobbleblob]

Of course you still program, but your job title on that MIT gathering wouldn't have been 'programmer'.

[vidarh]

Part of my point is that personally I would describe myself as a programmer first.

Those titles for me has been a means to a higher salary, not something that defines me, and often not something that have defined my roles very well. Despite being "technical director" at present, I spend most of my time on architecture and devops.

But if you care less about the money, then staying in a pure developer role saves you the aggravation, and I know many people who have opted to refuse to be promoted into management positions because what they enjoy doing is the programming and they've been less willing than me to take the titles and find ways to program anyway.

I've personally offered people management positions more than once and had them turn it down for that reason. Including people above 50.

[wobbleblob]

But that's not what the blog post we're responding to was about - this was about anecdotal evidence that the MIT alumni who were still 'engineers' at 50 were worse off than their peers with more glamorous job titles. Maybe quite a few of the ones who answered 'not an engineer' were actually like you. Chief something, CTO, head- lead- something.

If you were interviewing an applicant for a dev position, have you never wondered "you worked there for 15 years, why were you never promoted?". I doubt the same would be asked of someone who had been working as a surgeon for 15 years.

[gohrt]

ahem https://www.google.com/search?#q=%22I+am+a+programmer.+On+my...

[sanoli]

What?? Are you serious? Why would programming be different from other activities/occupations? "Oh, this guy is still operating after 3 decades and never became a hospital director. Something's wrong with the guy."

[wobbleblob]

When you're my age, you'll know what I mean. If your job title still reads 'programmer' or 'developer', rather than 'architect' or 'chief/lead/head of-'etc , something has gone wrong.

[vidarh]

Or something went very right and you found something you really loved to do. Personally I kind-of wish I'd have gone that route and not had to deal with all the management bullshit that I've spent time on over the years.

[kristopolous]

There's nothing wrong with wanting to do it as a lifelong career. There's plenty of well-adjusted responsible adults that do. I just don't think it will be my decision, personally.

[wobbleblob]

It may not be your choice. At some point it becomes more and more difficult to get a job interview if you don't have more impressive sounding job titles on your resume.

[hga]

What I discovered after I turned 35 was that erasing all evidence of my age from my resume made a massive difference in getting interviews. Of course, further success depended on being able to fake being young as fortunate genetics helped me to do. Just be careful about specifics in what you talked about, in a 2003 interview I slipped and mentioned PDP-11s, which prompted the interviewer to exclaim "Just how old are you?" I was hired, probably in part because the job was particularly difficult software archaeology, but my younger boss ... well, it didn't last long, or end well.