Someone on a developer forum referred to Shift Left as a "psy-op" last week. I found it amusing. Then I realized they were correct. The concept of Shift Left was sold as a way to empower product developers. However, in practice, what it really meant was giving the product developers a pager and getting rid of the operations team that previously had it. ## The rebrand nobody voted for
Here's how it's done. You reduce the number of employees and present it in a positive light as an improvement in company culture. The tasks didn't go away, they just shifted to the left, to the developers. The way it was presented was actually brilliant. I mean, who's going to fight back on "empowering developers" - You're for silos, buddy? Meanwhile, the product engineer was given the responsibility of dealing with Terraform, Kubernetes manifests, IAM chains, and ended up receiving a 2am Slack ping. Hooray! 🎉
The numbers are ugly
This is not just a feeling. According to SoftwareSeni's report from January 23, 2026, titled "Organisational Transformation in the Post-DevOps Era" 74% of developers are actually spending more time on operations work than product development. I need to read that again. Three out of four people we've hired to actually ship features are babysitting infrastructure. According to that same SoftwareSeni report, 83% of developers experience burnout specifically from juggling operational responsibilities they were never equipped to handle. It's ops burnout, not burnout in general. Also, the variety of tools used in an organization is so funny. According to the report, on average, one organization requires a developer to interact with 8 to 12 CI/CD tools. You didn't receive a platform. You were given a scavenger hunt. ## Your brain wasn't built for this
Here's the part that really annoys me. Human working memory can only hold 4 to 5 items at once. That's all. The philosophy that "everyone does everything" overlooked that hard limit and added testing, security, and deployment on top of it. It was well put by Steve Corndell in The New Stack on January 30, 2026. He said orgs "shifted massive amounts of cognitive load onto individuals whose primary job is delivering business logic" and "turned their IDEs into cockpits with 50 flashing warning lights."
Fifty warning lights. Corndell highlighted that we were expecting frontend engineers to become proficient with Kubernetes ingress controllers while our backend devs were unraveling AWS IAM role chaining. This didn't result in faster delivery. It was "decision fatigue, context-switching paralysis, and burnout."
Even Kelsey Hightower said what everyone was thinking in 2024: "we are asking developers to do too much by shifting everything left including security... the idea that developers need to become security experts, in addition to everything else, just isn't sustainable."
If the author of the book Kubernetes Up and Running feels that there is an overwhelming amount of knowledge about Kubernetes, then it really may be the case. ## "You build it, you run it" became something worse
The initial pitch was quite honest. You control your service from A to Z. Great. Developers spend hours debugging 300-line Kubernetes manifests to increase a memory limit on a simple service. This is what Salwan Mohamed claimed in a Medium article of January 12, 2026, subtitled "You Build It, You Fix 1,000 YAML Files". That's not owning. That's just punishment dressed up in a more complicated way. I operate a small startup. I feel this in my bones because when you have a tiny team, truly everyone does touch everything. The distinction here is that I was fully aware that it was a compromise we were making out of necessity as a small organization. Large organizations did the same things and heralded it as a movement. → We were scrappy. They were being cheap and putting it on a t-shirt. ## What Shift Left actually optimized for
Remove the cultural language and all you have left are the incentives:
→ Fewer ops salaries on the books
→ On-call responsibility pushed to people who can't push back
→ Cognitive load treated as free because it doesn't show up on a budget line
→ "Autonomy" as the word you use so nobody feels demoted while getting more work
However, this doesn't imply that developers shouldn't have an idea about their infrastructure. They should. Being responsible for your deployment process improves your skills. However, there is a distinction between having the knowledge of how infra works and having all the onus on you, no platform team, no guardrails, and no raise. One is a growth opportunity. One is a headcount spreadsheet wearing a hoodie. The actual solution is not to shift right once more. We need platform teams that prepare the ground so that a memory bump is just one line of code, and not a 300-line configuration file. So let me ask you this. Did Shift Left at any point in time actually help you increase your shipping speed, or did it just gradually pile more work on your plate without any salary increase?
Top comments (0)