This whole article resonates with my experience, but especially this:

When you’re responsible for everything, you see a bigger picture. You hear directly from users about design decisions you thought were smart. You hear from yourself when a dependency upgrade is difficult because of a web of intertwined dependencies. It’s humbling. But you learn.

I think this is the aspect I enjoy most about full stack development. Providing a whole solution, rather than just a piece of it, is tremendously powerful. It becomes possible to bring all parts of a system into harmony, every component working toward the same goal.