"Since the term was originally coupled to the use of the MEAN/MERN stack, maybe what the community meant was just JavaScript Developers? Why didn't we use it?"
Yes, I have full-stack on my resume and some of my profiles. But you'll notice that if I use the term at all, I almost always put either "full-stack web developer" or "full-stack JavaScript developer" because I am comfortable referring to myself as such while still keeping a straight face. That doesn't make me a "full-stack developer" nor a "full-stack engineer".
Quite frankly, I think web/JavaScript developers and software engineers are two completely different categories with minimal overlap. Some might disagree, but I don't consider myself a software engineer and I'm okay with that. It doesn't make me better or smarter than you and vice versa.
I think the T-model is probably the best learning approach overall, but it's also perfectly fine just to be exceptionally skilled in only one or two languages or frameworks. Some companies may pass you up, but eventually someone is going to notice your skill level and decide that it's worth it to hire you because you can outperform the others, even if it costs them a little more.
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 agree with this part in particular.
Yes, I have full-stack on my resume and some of my profiles. But you'll notice that if I use the term at all, I almost always put either "full-stack web developer" or "full-stack JavaScript developer" because I am comfortable referring to myself as such while still keeping a straight face. That doesn't make me a "full-stack developer" nor a "full-stack engineer".
Quite frankly, I think web/JavaScript developers and software engineers are two completely different categories with minimal overlap. Some might disagree, but I don't consider myself a software engineer and I'm okay with that. It doesn't make me better or smarter than you and vice versa.
I think the T-model is probably the best learning approach overall, but it's also perfectly fine just to be exceptionally skilled in only one or two languages or frameworks. Some companies may pass you up, but eventually someone is going to notice your skill level and decide that it's worth it to hire you because you can outperform the others, even if it costs them a little more.