Chris, I am approximately a decade younger than you, so in my 40s staring at 50. I started off my career at a pretty severe disadvantage, so it took off late. My golden age is now.
You are correct that my unique expertise affords me some significant advantages. For certain fascinating classes of computer science problem, I’m the person everyone calls. My true CV is far weirder than the public ones. But ironically, that isn’t what companies typically pay me for except tangentially. I mostly get paid to fix broken engineering organizations because apparently I am good at it and there is no version of “broken” I haven’t seen before. I still think of myself as an engineer, and remain extremely technical, but most days I am solving people and organization problems. I am valued more as an executive fixer than for my technical ability despite having some extremely unique technical capability. The market has made it abundantly clear which is more valuable.
I will always love writing code but it is more enjoyable as a (very serious) hobby and craft, albeit with an end product that has often been licensable. I’m not even sure this is a bad thing, since it allows a level of code quality that would never happen in a commercial environment.
FWIW, I’ve always been able to get on with young people and old people, whatever that meant for whatever age I was. I genuinely don’t classify people that way, I am more interested in their experience and knowledge. Especially for engineers, if you are doing cool shit age doesn’t matter.
I'm used to dealing with folks across pretty much all ages. I have an "eclectic" social circle that includes (but not limited to) kids still in high school, bikers, ex-cons, scientists, bankers, retirees, and CEOs.
You are correct that my unique expertise affords me some significant advantages. For certain fascinating classes of computer science problem, I’m the person everyone calls. My true CV is far weirder than the public ones. But ironically, that isn’t what companies typically pay me for except tangentially. I mostly get paid to fix broken engineering organizations because apparently I am good at it and there is no version of “broken” I haven’t seen before. I still think of myself as an engineer, and remain extremely technical, but most days I am solving people and organization problems. I am valued more as an executive fixer than for my technical ability despite having some extremely unique technical capability. The market has made it abundantly clear which is more valuable.
I will always love writing code but it is more enjoyable as a (very serious) hobby and craft, albeit with an end product that has often been licensable. I’m not even sure this is a bad thing, since it allows a level of code quality that would never happen in a commercial environment.
FWIW, I’ve always been able to get on with young people and old people, whatever that meant for whatever age I was. I genuinely don’t classify people that way, I am more interested in their experience and knowledge. Especially for engineers, if you are doing cool shit age doesn’t matter.