In my view this is off base because it's a bit intentionally obtuse.
I think the real maxim is more along the lines of "if you need actual full stack engineering, you don't want a full stack engineer."
Because full stack engineers are not there for large, highly engineered, Amazon/Google scale sites.
They are there for the MVPs, the startups, the moderate scale internal line of business tools, your local city government, or one-off moderate projects.
A full stack engineer is not there to have expert knowledge of every single micro detail of front-end, back-end, databases, site performance, SEO and such.
They're there to have a general knowledge of them, produce something reasonable, and know enough of all the ends to ship in a timely manner, hopefully with design decisions that can be easily tweaked, meet requirements, and don't have boatloads of technical debt, until 'till it justifies a larger, more specialized, engineering investment, or just putters on with light support 'till end EoL because it's good enough for the scale of operation.
I think the real maxim is more along the lines of "if you need actual full stack engineering, you don't want a full stack engineer."
Because full stack engineers are not there for large, highly engineered, Amazon/Google scale sites.
They are there for the MVPs, the startups, the moderate scale internal line of business tools, your local city government, or one-off moderate projects.
A full stack engineer is not there to have expert knowledge of every single micro detail of front-end, back-end, databases, site performance, SEO and such.
They're there to have a general knowledge of them, produce something reasonable, and know enough of all the ends to ship in a timely manner, hopefully with design decisions that can be easily tweaked, meet requirements, and don't have boatloads of technical debt, until 'till it justifies a larger, more specialized, engineering investment, or just putters on with light support 'till end EoL because it's good enough for the scale of operation.