People labeling themselves as a “full stack developer” often have a very different idea.
Your version is the cross-functional team in a single person. Cross-functional teams resulted from the realization that functional teams will tend to “fix things” in areas they have access to rather than being delayed by issuing a request to another team (in charge of the functional area where the logic actually belongs) - usually ending up with business logic in all the wrong places. However members within cross-functional teams need to communicate effectively with one another so a certain amount overlap is required and each member often needs to wear multiple hats so that absences can be covered - leading up to the notion of a team of “full stack” developers.
Now it makes sense that one should understand all these areas - but how many years will it take to become competent, much less proficient in this laundry list of skills? Also there still seems to be the notion that “leveling up” is moving into management - not to become a senior developer.
Furthermore the full stack skill set seems to focus on solution-oriented skills - what about the problem-oriented, non-technological skills like domain knowledge, domain-analysis and related methodologies?
(Aside: AWS, Azure, and Google cloud present themselves with serverless as requiring a much reduced Ops skillset).
Lately I’ve even heard the term of “full stack designer”. Apparently some “web designers” simply delivered design mockups; HTML and CSS was purely part of the “web developer’s” job. So a designer also delivering HTML and CSS (and a smattering of JavaScript) is now a “full stack designer”.
So the “full stack” terminology is about as useful as “component”.
