Welcome to HN and for making this place more magical by your presence. Have seen other very senior programmers here over the years. Paul Lutus comes to mind now[1]. One question: Do you go through a mid life crisis in programming in your 40s/50s? My story (just felt like sharing): I am in my 40s and have been programming for 30 years (I first wrote in Fortran in my Engineering College, 1st semester). Later profession…
> genedangelo 1 day ago
> The one thing that comes to mind is to avoid the "hammer looking for a nail" syndrome. I see this all the time, especially in academia. Rather than worry about learning all the latest stuff, concentrate on solving the problem at hand in the simplest and most effective manner. If that requires you to learn new things, then that's a great time to expand your repertoire - working on a specific problem. Of course you have to strike a balance, but mainly concentrate on solving problems rather than being up-to-date on all the latest stuff and trying to find the proverbial nail for your new hammer.
Additionally, I am in a coder in my 50s and I have to say I am not going through any kind of mid life crisis in programming!
Like genedangelo, I just focus on problems that need to get solved and I really don't care how I solved it as long as I use a great tool that is meant for that job.
Super happy to learn a new tech if it makes sense for the problem.
There was a phase a few years ago where folks were using node.js to build all kinds of websites, including content heavy text based sites that would be better served as static html or dynmaic Ruby, PHP etc.
I think that's the classic mistake of a hammer looking for a nail and I can imagine it was really unsatisfying to build those kinds of sites with that kind of tech and might even contribute to burnout (just speculating).