HNHacker News
TopNewBestAskShowJobs

throwawayoldman

8 karma · joined June 27, 2021

submissionscomments
throwawayoldman··on Challenging the Myth That Programming Careers End at 40
Congratulations, looks like you made it.

Let's say you are not CTO but developer, and your CTO is 32yr old. Would you be as happy?

throwawayoldman··on Challenging the Myth That Programming Careers End at 40
> "The difficulty is to remember arbitrary decisions based on temporal situations."

That is the difference today. As you said lot of things you learned decades ago is still applicable knowledge. The AWS ad-hoc stuff we learn today will be outdated and mostly useless information very soon. The undelying principles (even distributed computing) we already learned years ago.

throwawayoldman··on Challenging the Myth That Programming Careers End at 40
> "I don't know if you lose much learning power or if you just lose interest."

Both.

- As we accumulate knowledge while aging it becomes more and more difficult to learn new things. We are smarter and smarter though. (Most of us :)

- Losing interest sooner is natural. For example by the time I read through the documentation of one service that deploys containers on AWS the information is already outdated and two other, newer AWS services released doing almost the same. When someone says: "we need to investigate this new AWS ..." I am already shutting my ears.

throwawayoldman··on Challenging the Myth That Programming Careers End at 40
You will still need to re-learn infra frameworks in every 3-5 yrs.

Also, after 10-15 years, you will be increasingly frustrated to be managed by 32 yr olds.

throwawayoldman··on Challenging the Myth That Programming Careers End at 40
Those 28-33yr old teamleaders/managers are immediataley alarmed by two things:

- "How am I going to manage this person 15-20 years my senior?" Also this "will want to be manager soon."

- "This old man must be stupid when applying for a non-leadership role at that age."