undefined | Better HN

0 pointsdiggan1y ago0 comments

I think we've all came across people who chose technologies based on not what would be the best for the problem at hand + what they have the most experience with, but instead what is trendy today and can help them get hired in the future at the next workplace.

I'd probably describe that as "bad behavior" as you hire people believing they'll focus on improving things inside the company, inside of focusing on padding their CV. Of course, wouldn't be bad if it's both, but selecting the latter in front of the other seems non-optimal for the employer.

If you go through enough people like that, you end up with a ball of software spaghetti that anyone working on will struggle with, instead of a polished architecture ready to nimbly be changed when needed.

0 comments

CM301y ago

Unfortunately, I suspect the structure of the tech industry has kinda made this inevitable. If you need to jump ship every few years to get a meaningful wage increase, and companies are happy to drop the axe on an entire team because profits went down 0.01%, the incentives are to do whatever's needed to keep yourself hireable at all costs.

So everyone picks what will look good on their resume in a few years, not what actually solves the issue in the most optimal way possible.

j / k navigate · click thread line to collapse

0 comments

CM301y ago

So everyone picks what will look good on their resume in a few years, not what actually solves the issue in the most optimal way possible.

j / k navigate · click thread line to collapse