The full stack developer is a myth
Scott Hadfield

This is both true and yet not fully so. I’m actually in the process of writing my own step-by-step guide of becoming a full-stack developer, after working on a relative complex project all by my lonesome for about a year. To cover everything in your graph is out of anyone’s ability (aside from Sheldon Cooper, perhaps), but you can narrow it down considerably if you can set the devops stack beforehand. Also, you can scope each “layer” down to “just-enough-knowledge”, especially at the beginning of the project. I’m actually training a team to become “full-stack engineers”, but each focus on a specific area of the development, one on iOS, one on Android, one on Web and one on API. However, since my stack uses JavaScript almost exclusively and all front-ends use React/React Native, I can interchange anyone of them to another position. Eventually, once the framework is complete, I can reassign each to a specific vertical stack, for example, one on consumer, one on service providers, one on admin, and one on devops, and still, all four would be interchangeable, provided I have enough cross-training sessions. The point is, yes, one CAN become sufficient enough on all “layers”, but it will take forever to complete a real-world project. But you can have a team of “full-stack engineers” that could potentially cut down your HR expense and down-time significantly.