> It’s practically a trope that every time this subject comes up, the top-rated comment is a skeptical response...from a junior developer.
I looked at the top rated comment for the other times this exact same article was posted on hacker news. For none of those, the top rated comment "is a skeptical response...from a junior developer".
Actually, it's more often (https://news.ycombinator.com/item?id=16934500, https://news.ycombinator.com/item?id=9361580) from a self declared senior developer. And none of those top comments really collaborate the article. Talk about confirming one's biases...
But taking into account all the anecdote from senior devs available just on hackernews, there's no consensus emerging whether the article makes sense or not.
So, at this point, I don't really feel the need for a plan B, even if being 40 years old is not really this far away for me. And it seems from the shared stories that whether this is needed or not is really based on personal experience, and is not a generally needed advice. I certainly hope to be in a path where I'm honing my skills well enough to be able to continue beind paid to engineer software after I'm 40.
Well, sure: you disagree, and you’re seeking out arguments that confirm your existing beliefs.
In any case, I’ve said what I have to say on the subject. I can’t make you listen to my
direct experience, but I’m not going to spend time arguing with you about it.
> It’s practically a trope that every time this subject comes up, the top-rated comment is a skeptical response...from a junior developer.
I looked at the top rated comment for the other times this exact same article was posted on hacker news. For none of those, the top rated comment "is a skeptical response...from a junior developer". Actually, it's more often (https://news.ycombinator.com/item?id=16934500, https://news.ycombinator.com/item?id=9361580) from a self declared senior developer. And none of those top comments really collaborate the article. Talk about confirming one's biases...
But taking into account all the anecdote from senior devs available just on hackernews, there's no consensus emerging whether the article makes sense or not.
So, at this point, I don't really feel the need for a plan B, even if being 40 years old is not really this far away for me. And it seems from the shared stories that whether this is needed or not is really based on personal experience, and is not a generally needed advice. I certainly hope to be in a path where I'm honing my skills well enough to be able to continue beind paid to engineer software after I'm 40.