4 ms·
I read through the article hoping to join the comments with several hot takes, but alas I'm disappointed. Well written and largely accurate. My primary disagree
by hnrodey 3y ago
I read through the article hoping to join the comments with several hot takes, but alas I'm disappointed. Well written and largely accurate. My primary disagreement is working into nights and weekends. If that's your thing then so be it, but I avoid it like the plague and my career has progressed quite well. I've remarkably committed during the work day and I don't fuck off - I just get my stuff done.
Amongst the biggest risks that comes along with being a senior developer is that, at some point, your skillset adapts specifically to what THE EMPLOYER needs it to be. The trade-off we make is reduced risk of losing job (as the author called out). Even if you avoid layoff, at some point you will want to change jobs. Entering the job search after having an entrenched position that you grew into is like being married for 5-10 years and then entering the dating scene ... the new suitors (employers) want a mate (employee) with abs and a flashy sports car instead you're showing off a dad bod and well maintained minivan. It's a fine decision to make either way, just know the game you're playing.