I think that a stack can help or hurt you on an individual project, much the same way that using a hammer instead of a drill to put in a nail can make things easier.
However, I think that this effect is often overstated. The best programmers I've worked with isolate their "important" code from their framework/stack, which makes the stack an easily-changeable detail.
An analogy I use often when people (usually devs-turned-managers with an axe to grind) try to blame bad code on a language/stack is that "You can't blame the English language for Twilight. That's the fault of the author and editors." (Apologies to those who genuinely like Twilight)
At a personal level, I believe that I can teach any junior the ins and outs of any stack. What I struggle to teach them is how to break a large problem into manageable chunks, so I think that is the skill most people should focus on developing, in whatever stack they're currently using.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think that a stack can help or hurt you on an individual project, much the same way that using a hammer instead of a drill to put in a nail can make things easier.
However, I think that this effect is often overstated. The best programmers I've worked with isolate their "important" code from their framework/stack, which makes the stack an easily-changeable detail.
An analogy I use often when people (usually devs-turned-managers with an axe to grind) try to blame bad code on a language/stack is that "You can't blame the English language for Twilight. That's the fault of the author and editors." (Apologies to those who genuinely like Twilight)
At a personal level, I believe that I can teach any junior the ins and outs of any stack. What I struggle to teach them is how to break a large problem into manageable chunks, so I think that is the skill most people should focus on developing, in whatever stack they're currently using.