This is kind of funny because you’re fighting hubris with hubris, and a large part of what you’re saying is based on a huge misunderstanding of the industry’s d

This is kind of funny because you’re fighting hubris with hubris, and a large part of what you’re saying is based on a huge misunderstanding of the industry’s dislike of the term “full stack developer”. I’ve never worked with a self-proclaimed “full stack” developer that does what they say they can. On my teams I always have an expectation, even if unwritten, that a developer will naturally end up specialising in front end or back end technologies. It’s always the case. And honestly in my experience it’s usually front end developers that have vastly miscalculated the complexities of the back end. The argument has never been that nobody can be a mediocre front end developer and a mediocre back and developer at the same time. The argument has always been against the allure of ‘full stack’ developers in the eyes of management and PMs. Suddenly all your team balance concerns go out the window. Communication overhead between front and back end developers goes out the window. Yada yada. The reality is that full stack developers only really work when the bar is low or the team/org is big enough that ‘Jack of all trades’ types can sustain themselves with a workload whilst leaving some other stuff up to specialists. My speciality is in back end development. I also know a bit of client-side JS and can put together a sorta-decent HTML/CSS interface. I’d never self-identify as “full stack” because I know what expectation that sets.