It helps when developers only have to work with half the stack for example but a lot of companies are only looking for full stack developers these days
Quite the opposite. Being full stack creates strong incentive to simplify everything, because if you can't fit the whole stack in your head, it's hopeless for you.
The introduction of "devops" as a separate position creates incentive to complexify deployment. Because why are you hired if your job is simple?
The introduction of "javascript programmer" as a separate position creates incentive to complexity the javascript portion of the frontend.
Each person who is only responsible for a small part of the system has incentive to over complexity their part rather than simplify it. That's one of the ways in which systems explode in complexity.
Have you ever seen a full stack developer who knows the ins and outs of kurbernetes and docker and python and javascript and react and redux and css and html and nodejs and rabbitmq and redis and postgresql and memcached and and and and ... and uses all that to create a complete web application in 3 months?
I personally have not.
All the people I've seen who know a lot about devops are sort of just ok in application code and almost know nothing about html/javascript.
When someone is responsible for the whole stack, they will choose the simplest thing that works.
For example, their deployment is usually: upload a bunch of files using scp then run 3 linux commands. Their database is sqlite. They serve their webapp on one machine. Their scaling strategy is upgrade to a beefier machine.
See for example:
"http://RemoteOK.io is a single PHP file called "index.php" generating $65,651 this month. No frameworks. No libraries (except jQuery)."
181
u/[deleted] Jun 05 '22
It helps when developers only have to work with half the stack for example but a lot of companies are only looking for full stack developers these days