Re:Ask HN: Are older devs more resistant to adopting new tech?
by twunde on Monday January 20, 2020 @04:37PM
(#22102282)
2.5 I want tech to be either mature enough or beneficial enough that I'm willing to deal with all the bugs AND specifically the very real possibility that the application may need to be rewritten to replace a bad tech bet. A good example was that around 2011 MongoDB was really taking off. HN routinely had articles about migrating to Mongo and how it was the new hotness. It turns out that MongoDB had a number of problems including dropping data regularly :/
Those of us that had to deal with debugging issues like that and potentially porting away from Mongo, are a bit gun-shy about adopting new databases, especially without the ability to call someone up and chat about what issues they encountered after running the tech on an application supporting a million users.
Re:Ask HN: Are older devs more resistant to adopting new tech?
by twunde on Monday January 20, 2020 @06:28PM
(#22102931)
Ah, and of course I found the essay I wanted to reference when I wrote this: https://mcfunley.com/choose-boring-technology
When you're new everything is new so you're willing to try a bunch of new tech. You haven't seen people get burned (repeatedly) on using a whole bunch of new tools at the same time.
The thing that many younger devs don't (yet) get is that tech works in cycles. Today's hotness is yesterday's tried-and-true. As an example, Java (J2SE) came out in 1998 and my guess is - based on open positions on e.g. Stack[1] - that you'll still be able to write Java for decades.
So for an old guy to adopt new tech:
1. I'd want there to be obvious benefits that outweigh the costs for the new approach. As an example, I'm not convinced FE frameworks are the best approach for CRUD apps. If you're building Trello and need crazy interactivity, sure. But you incur a bunch of cost vs. say Django / Rails / Laravel with intercooler or Stimulus sprinkled into interactive pages. And what's the huge cost for? Skipping a few page refreshes?
2. I'd want tech to be mature enough that I feel good it's going to be around and therefore is worth investing in. As you get older your time becomes more valuable as you tend to take on other obligations (kids, spouse). Hacking on new tech late at night or all weekend is less palatable or possible than it used to be.
Curious to hear what others think though.
1- As of writing there are 425 jobs that mention Java (https://stackoverflow.com/jobs?q=java). Surprisingly there are only 341 that mention React (https://stackoverflow.com/jobs?q=react).