3 ms·
@aws_ls I wanted to surface this answer to a question about burnout answered by genedangelo. I is on page 2 here but I think it is relevant to what you are ask
by jv22222 6y ago
@aws_ls I wanted to surface this answer to a question about burnout answered by genedangelo. I is on page 2 here but I think it is relevant to what you are asking.
> 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).
- aws_ls 6y agoThanks a lot @jv22222 for sharing your own perspective apart from highlighting @genedangelo 's reply. Just to clarify, I am also not going through a crisis as such, thankfully. Just a doubt on future continued ability lingers on occasions. What you say, makes sense to me. After a few decades, we just see some patterns repeating with different names - RPC -> CORBA -> RMI -> Web servcies (based on SOAP) -> REST (based on JSON) -> Google RPC (going again to binary style) ... and so on. Not being cynical. Things progress in a way, but also have echos of the past.