> You might be dead tomorrow; you might as well enjoy today.
Just for this remark I wish I could have upvoted you more than once.
This is something that those that live for the job, without paying attention to family and friends seem to forget.
And yes, Ican relate to the article; I've seen (I still see) junior managers who can barely tie their shoes make more money than excellent engineers with 25y experience, but that's the way the world is...
Basically 'engineer'/'programmer' is a calling for some; it is for me. People for whom this is not a calling will never be /really/ good at it (for one thing, they don't spend their spare time doing it!) and eventually gravitate out of it.
But the ones for whom it is a calling, well, sod the money, give me some nice project/people to work on/with and I'm happy.
Or, do that but also get the money by going consulting. That's what I do for the last few years. It's quite exciting being a 'mercenary' in a way, and you can dissociate yourself from the companies/products and focus on the engineering.
My very first paid project was designing the PA audio system in the Lille (france) metro. It was a fancy Mac SE/30 with a IEEE GPIO card. That was driving two big Revox Tape machines, and was playing one, rewinding the other etc. Occasionally it would also play a digital audio file (w000t!).
It was all in Pascal at the time, and I had a whooping 4MB of ram. System ran for well over 10 years!
On my first internship after high school while waiting for university applications to come out was done in Clipper and Access/Visual Basic. Also starting OS/400 backup jobs.
Not the set of languages that I already enjoyed most, but it kept myself busy during the Summer.
I can't imagine having done anything else. Sure, many other careers sound appealing. But software has been stimulating and sustainable while affording me a managable level of stress and downtime as needed. (Try doing that as a physician or veterinarian, both careers that I once considered).
That said, I sympathize with the OP's frustrations. Software jobs usually imply a rather flat hierarchy, with little opportunity for advancement other than leads or principals. Any further rise in responsibility requires that you leave tech behind and spend your days in meetings. Not for me.
However if you work in R&D without a PhD, I've found a severe glass ceiling (especially at larger companies). In general, no advancement beyond lead staff for you. If I'd known that 10-20 years ago, I would have handled that differently (get a PhD, work at smaller firms, or leave R&D). The road not taken, I guess...
The past is just a memory, the present moment is so fleeting that it cannot be grasped, and the future hasn't happened yet:) I think being in a flow state is about living with this fact, in the moment, as it is, without all the mental overhead that is past and future. You're not 58, you are brand new, right now, just as you are.
It's hard to beat the feeling of having a computer make your life easier. There's a triumph in it.
Screw that. I'd never work for a place like that.