DEV Community

loading...

Discussion on: The full-stack dilemma

Collapse
thorstenhirsch profile image
Thorsten Hirsch

Actually it's the other way 'round. Back in the days (of PHP and Ruby'on'Rails) a single developer could build frontend+backend since it was all done in the same framework (server-side rendering, of course).

But requirements for the frontend increased over time: responsive, reactive, progressive, more beautiful... so the frontend became more complex, thus you need specialists. The same goes for the backend: building an event-driven microservice architecture running on Kubernetes with a fully automated CI/CD pipelines most likely requires more than one specialist.

If someone is looking for a full-stack developer nowadays he/she is basically saying that they don't have sophisticated requirements or they simply don't care. Because expecting a single developer to master all the technologies I mentioned is crazy.

Collapse
mbarzeev profile image
Matti Bar-Zeev Author

If someone is looking for a full-stack developer nowadays he/she is basically saying that they don't have sophisticated requirements or they simply don't care. Because expecting a single developer to master all the technologies I mentioned is crazy.

I agree. Both disciplines have become much more complex these days and require more experience and mastery to achieve better quality product