Newsletter argues AI is deskilling SREs, not replacing them
A Signoz analysis warns that as AI automates incident response, site reliability engineers may lose the hands-on expertise needed for rare, complex failures.
What to know
- A Signoz newsletter applies 1983 automation research to argue AI automates the routine work SREs do daily—incident triage, runbook execution, log analysis—leaving them unpracticed for the rare, complex failures only humans can handle.
- The core concern: when AI handles 95% of incident response, SREs lose muscle memory on the 5% that matters, mirroring how industrial automation left blue-collar workers ill-equipped for exceptions they'd stopped practising.
- Commenters debate solutions (mandated manual incident handling, monthly quizzes, aviation-style oversight) and whether deskilling is a real risk or simply a shift from old to new skills.
- The piece frames the challenge not as job replacement but as preserving expertise under increasing automation—a debate echoing broader concerns about AI's effect on knowledge workers.
The dispute Whether AI adoption deskills SREs (and whether that can be mitigated) versus simply shifting skill requirements in ways that may be benign or even positive. · positions read across 33 posts and comments
AI deskilling is a real risk; SRE teams need structured safeguards like mandatory incident practice and human-in-the-loop requirements.
-
“Aviation is a perfect industry to learn from, they figured out a lot of things about how to keep humans from making mistakes.”
andix · Hacker News ↗
The deskilling framing is circular; AI adoption replaces old skills with new ones, not necessarily worse ones.
-
“I don't understand what this title is saying, feels a bit circular. You could say this about so many jobs that are or are not being replaced by AI. I suspect we are just replacing old skills with new skills.”
MetaMalone · Hacker News ↗
Real understanding and deep expertise in SRE cannot be replicated or maintained by AI; humans who rely on AI lose fundamental knowledge.
-
“SRE was always about understanding; understanding data flow, understanding bottlenecks, understanding logs, understanding application architecture, understanding end user functionality… There is no understanding with AI-generated…”
pluc · Hacker News ↗
Lisanne Bainbridge Cognitive psychologist (1983 researcher)Signoz (via newsletter author) Observability platform / newsletter publisher
How it unfolded 2 developments, newest first · click a bar or a number to jump articlespostscomments
-
2
SREs and engineers debate deskilling risk and proposed safeguards
Hacker News commenters engage with the deskilling thesis, with some proposing aviation-style interventions (mandatory manual incident handling time, quizzes before deployment) and others questioning whether AI truly deskills or simply replaces old skills with new ones.
“Aviation is a perfect industry to learn from, they figured out a lot of things about how to keep humans from making mistakes.”
— andix, HN commenter · source -
first by HN Best, 13d ago · also HN Frontpage
-
This was just the default where I worked. We called the exercise Wheel of Misfortune: facilitator sets up an outage / bug in a non-prod environment (inspired by real events or not), spins a wheel, picks a victim, and the problem is solved collectively, manually. That's the standard format, but it could be much more freeform than that: the point is…
2 more of the top 3 · 31 posts in this stretch
-
I had never heard about SRE before and suddenly it's all I see. Modern problems (slop fest) require modern solutions (someone to babysit broken systems)? Site reliability engineering (SRE) is a discipline in the field of software engineering and IT infrastructure support that monitors and improves the availability and performance of deployed…
-
A (very) key difference is that this behaviour is mandated by the FAA, and consistent across all providers. There isn't a (legal) option of just not-doing-it because it's "cheaper".Modern companies generally do not have the same incentive to keep their SRE (or engineers in general) upskilled. Cutting SRE because "we don't really have incidents…
-
-
1
Signoz newsletter claims AI deskills SREs through automation of routine tasks
A Signoz newsletter piece argues that as AI takes over incident response, alert grouping, runbook execution, and root-cause analysis, SREs lose the hands-on practice needed to handle the rare, complex failures that remain. The piece cites Lisanne Bainbridge's 1983 paper 'Ironies of Automation' to argue that humans left to manage exceptions they've stopped practising become poorly prepared for high-stakes crises.
“When AI handles 95% of your incident response, do you get worse at handling the 5% that actually matters?”
— Signoz newsletter -
I dug into general AI deskilling a couple days back[1] - no good signs anywhere, but there's a few things we can do like make concerted efforts to do programming (like a coding hour every week), do a Leet code question, and getting the agent to quiz before merging something (stolen from Notion).[1]
1 more of the top 2 · 2 posts in this stretch
-
SRE was always a lame job description and so was the entire "DevOps" movement we had to suffer through during ZIRP. Real ones are oncall for the systems they build.
-
What people are saying 19 voices from 1 site · best of 33 · verbatim
- What structural incentives or mandates would be needed to ensure SREs maintain hands-on expertise in a heavily automated environment?
- Can software organizations adopt aviation-style safeguards without the same regulatory and safety-critical pressure?
- Are there metrics to detect when an SRE team has lost critical expertise before a novel outage forces the issue?
- Oct 31
-
The thing is that the learning curve for any tech has never been easier. You can ask a question and AI will help/tell you which command can answer that question. You can write that down. You can poke around the system.You can ask how your current automation code handles XYZ situation to get a better understanding, then ask if a code patch (you're…
-
AI isn't the only cause of deskilling. I've seen a few people go from coder to architect roles. Architects, being the decision makers, talk to vendors, CxOs, consultants,... and mainly spend their lives in powerpoints and visions.When an engineer stops coding, managing servers, ... it takes about 6 months to transform even a really smart person…
-
Deskilling has been happening for centuries. One doesn't farm their own vegetables, hunt for their meat, slaughter their own livestock, maintain their own vehicles (ahem - remember the horses and carriages). We've even stopped shifting the gears on our cars. Why are we complaining about AI?The biggest problem I see with AI isn't deskilling. It's…
- Oct 30
-
It's not a great example.The plane lands in the same amount of time whether an autopilot lands it or a human, so there's no incidental cost.If you let a human SRE handle a problem completely, not only will it likely take longer than an AI, but since that SRE is now deskilled, it may take FAR longer. And that's a cost. Who's going to pay it?
-
Reminds me of Children of the Magenta Line: https://youtu.be/5ESJH1NLMLs?si=wozPZOKAFKNcjPSmFly the plane, not the automation.
-
The thing is, without the FAA mandating something like this for SRE’s, no one will do it. In the moment, getting the broken thing back up and running is seen as far more important than the learning opportunity.I noticed this constraint a few years ago when the SRE/DevOps hiring market was really tight, but no one was investing in non-senior…
-
This has been going on in other professions for a long time. See the "children of the magenta line" talk about pilots losing the ability to hand-fly.Another oft-cited article here is William Langewiesche's article on the AF447 crash (https://archive.vanityfair.com/article/2014/10/the-human-fac...):> To put it briefly, automation has made it more…
-
Terraform deskilled us too. No one is saying, "SREs should configure their infra by hand sometimes to not lose that skill".If AI can handle it, great! We have a new tool -- let's make the tool better.Let's figure out how to use AI to make us detect and resolve issues faster, and even better, prevent issues. I've always said we can't consistently…
-
I don't even know if this is an AI thing. I've worked at places that have varying levels of operational maturity, and some of the ones that had very old SRE orgs also had a lot of their SREs operating mostly in the tier 3 given by the article.One of these orgs had basically all of the noisy pages under control through automated remediation and a…
-
I work at a startup and often deal with every part of the stack--programming, deployment, db, cloud environment, networking blah blah. AI agents have just gotten superhuman at computer use. I will never be able to use AWS CLI as well as claude does. I can spend time poking around in AWS, manually reading logs, looking at routing tables, cross…
-
Fuck aviation, stop using it as a dead horse metaphor for safety through human protocols. I am private instrument rating holder and there's very much a top down push for single pilot ops. Your newer jets (even the jetliners) are all designed with that in mind even though they may not be certified as such.
-
Previous discussion on an extremely similar article, down to the name-checking of The Ironies of Automation:
-
I don’t understand what this title is saying, feels a bit circular. You could say this about so many jobs that are or are not being replaced by AI.Do LLMs “deskill” us in general? I suspect we are just replacing old skills with new skills.
-
I think people are getting funneled into a new career path of being a technologist or technology director. People who can ask the right questions at the right time and direct attention to the appropriate areas given the goals and feedback.
-
Aviation is a good example if you want to have zero fatal mistakes. There is a way and there is a cost to do so.The same way erlang is good example of how to run a highly available system with hot reload and observability and stuff. There is cost for that too.Maybe not all of the projects need the same properties. I'm fine if some of the stuff is…
-
Aviation is different because their rent-seeking is enforced by the required legal hedging. I'm not sure the same incentive structure exists in the software side of things.In other words, we might need to find some hobbies.
-
SRE was always about understanding; understanding data flow, understanding bottlenecks, understanding logs, understanding application architecture, understanding end user functionality, understanding break points, SLIs, SLOs. Understanding how to mitigate, gracefully deteriorate, restart, restore, recreate, scale, etc.There is no understanding…
-
> "Just as the FAA mandates manual flying time even when the autopilot is perfectly capable, SRE teams can designate certain incidents, even the ones the AI could handle, as human-practice opportunities"This is a great example. Aviation is a perfect industry to learn from, they figured out a lot of things about how to keep humans from making…
-
We use AI at work, Claude specifically, and it’s faster than avg SRE for trivial tasks like cross signals correlation. But it requires a lot of effort to build a harness from your company contexts for it to work like an SRE. And it’s just a tool so if you have to build your knowledge to make it useful, otherwise it’s just a blunt. Or in other…