←back to thread

"No, it's less effort than that"

(smartguess.is)
388 points replyifuagree | 1 comments | 21 Oct 23 04:43 UTC | HN request time: 0.228s | source
Show context
ThinkBeat ◴[21 Oct 23 11:06 UTC] No.37965805[source]▶
If developers did not approach projects with the goal of adding acronyms to their resumes and infuse every project with the latest cargo cult du jour it would improve the ability to predict timelines.

Pick boring technology, that the team is already comfortable with, when possible. Keep the teams as similar as possible, Keep running projects the same way, when possible

I am not saying it will get things perfect, but it will be an improvement.

replies(2): >>37965853 #>>37967200 #
1. cityofdelusion ◴[21 Oct 23 14:45 UTC] No.37967200[source]▶
The problem is that developers have a very strong incentive to add new technology to their resume, as their job is not guaranteed. I think most junior devs have seen some old hat at their first real job who codes in one, ancient tech stack; someone that they perceive as un-hirable if the economy takes a turn.

We all see the job listings out there and the tech they desire. It is self-preservation, and it is in direct conflict with what is best for the company itself. To use myself as an example: I have zero regrets with pushing for JavaScript over VBScript many years back, for moving from Microsoft HTA to React, or for moving from Yahoo's YUI to jQuery. Being infused with old tech can very severely limit your ability to survive. Most of my interviews after my first job were simply explaining/defending the ancient tech I had specialized in. It is all risk, no reward at the employee level.