> Interestingly, full-stack teams have been heads and shoulders above in quality in my experience. I agree with that. The way I think about it is that in web y

> Interestingly, full-stack teams have been heads and shoulders above in quality in my experience. I agree with that. The way I think about it is that in web you benefit from thinking about a system holistically. The divide between front vs back end is merely a technical detail, and an organizational structure that mirrors that divide has a strong potential to artificially create friction between two parts of what should be a whole. Beyond that, I personally feel more empowered to take on responsibility as a full-stack dev, compared to when I was previously focusing on just the backend. For me, I think it’s mostly a psychological shift: I have more confidence to focus on solutions instead of deferring responsibility and thought power to someone else because it’s not my domain. So, while full-stack may be a generalist (which for some is a pejorative) in a technical sense, I see the general technical acumen as just one aspect of a higher level, more intangible specialization: solving problems and getting shit done. That sounds a bit lofty but I think it has analog to the bigger conversation here about managing. Manager with holistic responsibility for a project > manager with isolated responsibility for a single aspect of a project.