This is bad advice. OP has experience in a popular stack, no way that the language is their problem. They'll have an even more difficult time finding a job if they decide to switch stacks now.
*For you. I think it's a obvious and great advice, software engineers shouldn't define themselves by their stack (Java programmer?).
> They'll have an even more difficult time finding a job if they decide to switch stacks now.
That's why planning your career on changing stacks is such a good advice: you do it before you really need. I have kept a main stack and a "side project" stack for my whole career, going from PHP, ASP, .NET, RoR, clojure, Python then JavaScript for the longest with Rust currently as the side stack I'm learning. Had I got stuck on PHP I would regret it badly.
You're confusing the general "don't limit yourself to one language" which is good advice, with the specific "OP's problem in the past year has been that they know Java and are looking for Java roles" which the GP commenter has no way of knowing and is extremely unlikely to be the case.
meiraleal|2 years ago
*For you. I think it's a obvious and great advice, software engineers shouldn't define themselves by their stack (Java programmer?).
> They'll have an even more difficult time finding a job if they decide to switch stacks now.
That's why planning your career on changing stacks is such a good advice: you do it before you really need. I have kept a main stack and a "side project" stack for my whole career, going from PHP, ASP, .NET, RoR, clojure, Python then JavaScript for the longest with Rust currently as the side stack I'm learning. Had I got stuck on PHP I would regret it badly.
ps256|2 years ago
quickthrower2|2 years ago