Nowhere on XKCD’s map of The Contiguous 41 States does it say that you need to find the missing seven states, but that’s immediately where my mind went. And it was a little more challenging than I anticipated — all of New England is present & accounted for somehow?

The answer key is here, along with this tidbit:

The United States did have exactly 41 states for a few days in 1889, from the admission of Montana, the 41st state, on November 8, to the admission of Washington (the state, not DC), the 42nd state, on November 11.

See also this super-sized US map with 64 states.

And then after I wrote all of the above, I decided to check and of course I’d posted about this map before, soon after it came out. *sigh*

Tags: maps · usa · xkcd

The Secret to Success Is ‘Monotasking’. “We find that in ­real‑world work, the more switches in attention a person makes, the lower is their end‑­of‑day assessed productivity.”

Do I Belong in Tech Anymore? “Why am I here? Does any of this work actually matter? And if I stop caring about the quality of my work… will anyone notice?”

I had somehow missed (or forgotten) that Greta Gerwig is writing and directing an adaptation of The Magician’s Nephew, one of The Chronicles of Narnia books by C.S. Lewis. Filming has wrapped and it’s out in theaters on Nov 26.

My SREcon talk is now up.

The role of a Site Reliability Engineer (SRE) is evolving. The focus has shifted from simply working harder during an outage; A new kind of teammate is here to help: the SRE Agent.

But what are the key differences when you compare an SRE agent versus a traditional site reliability engineer? This isn’t just a superficial change. It signifies a fundamental alteration in how teams construct and sustain dependable services.

Scope of work: Direct intervention vs. autonomous action.

A traditional SRE: Does the work hands-on. 

• The process: An alert fires, they log in, run diagnostics, and apply fixes. They write automation, but they are the ones who run and oversee it. The work is guided by runbooks, which they either follow or improve.

An SRE Agent: Acts on its own. 

• The process: The agent doesn’t just run a script. It gets an alert, understands the context, and executes a series of actions to solve the problem. Think of it as a direct report for routine incidents. It handles the tedious tasks, letting you resolve incidents faster with an SRE Agent.

Problem-solving: Human experience vs. data correlation.

A traditional SRE: Relies heavily on experience. That “I’ve seen this before” moment. They connect dots based on past outages and knowledge of the system. Powerful, but it doesn’t scale. Caveat: it’s a huge risk if your experienced team or person is unavailable.

An SRE Agent: Uses data. An agent processes vast amounts of information in seconds. This can include telemetry, incident histories, recent code changes, and alerts from every system. It’s about recognizing probabilities and patterns on a massive scale, rather than relying on intuition. That’s one reason memory is so important. We found that when we built an SRE Agent with memory, it transformed incident response.

Speed and scale: Human pace vs. machine speed.

A traditional SRE: Human. They need sleep and get tired, and are prone to risk with manual processes. An alert at 3 a.m. might be handled by a groggy engineer. Their alertness and availability directly affect MTTR.

An SRE Agent: Operates 24/7 at full capacity. It doesn’t run the risk of getting tired or making mistakes from fatigue. It can run diagnostics and apply fixes in milliseconds, rather than minutes. This directly reduces MTTR for common incidents and scales your operations from human pace to machine speed.

Toil management: Reduction vs. elimination.

A traditional SRE: Works to reduce toil. A core SRE principle is to minimize ‌manual, repetitive work that provides no lasting value. A lot of time goes into scripting these tasks, yet someone often still needs to start them or watch them.

An SRE Agent: Works to eliminate entire classes of toil. Instead of writing a script to restart a service, the agent does it when it detects the need (or is alerted). That’s the difference between making a task easier and delegating it entirely. This is the heart of The Agentic SRE Vision, where the agent acts as a member of the team.

Daily focus: Reactive fixes vs. proactive strategy.

A traditional SRE: Is often stuck in a reactive loop. A large part of their day is spent firefighting, which leaves little time for the “engineering” part of their job that improves system reliability.

An SRE Agent: Changes the team’s focus. Automating incident response allows SREs to focus on critical tasks like system resilience, observability enhancements, and future planning. The role shifts from “system fixer” to “system architect,” transforming the incident lifecycle with AI agents.

Skill set: Technical depth vs. context engineering.

A traditional SRE: Needs deep technical knowledge of specific systems, scripting languages like Python, and infrastructure tools to be successful.

An SRE Agent: Shifts the human’s role to context engineering. You teach the AI agent about your environment by answering questions like:

• What tools can it use, like kubectl. 
• What are the service dependencies? 
• Which actions are safe to take without approval? 

The job becomes less about running the commands and more about defining the guardrails for the agent.

The human role: Total ownership vs. strategic oversight.

A traditional SRE: Owns the problem. They carry the stress and responsibility from the first alert to the final postmortem.

An SRE Agent: Makes the engineer’s role one of oversight. You become the manager and strategist. You review the agent’s work, handle escalations for new or complex problems, and refine its logic over time. The agent takes the first hit. The human provides the final judgment. 

The new SRE: Shifting from doer to strategic leader.

SRE agents augment your capabilities; they do not replace human team members. By delegating routine incident response to your new digital teammates, you elevate the department. You transition engineers from  tactical doers into  strategic leaders who design, manage, and   an automated workforce. 

The SRE of the future focuses on high-impact work:

• Architecting reliability: You design resilient systems from the ground up and engineer the sophisticated, automated responses to manage them.
  
• Managing a digital workforce: You oversee, train, and refine your team of AI agents, continuously improving their effectiveness and expanding their capabilities.
  
• Solving novel problems: You apply your deep domain expertise to tackle ‌complex, high-stakes incidents that automation cannot resolve alone.
  
• Driving innovation: You reinvest the time reclaimed from toil into long-term reliability initiatives, proactive system improvements, and business-critical feature development.
  

The future is human-managed, not just human-powered.

The goal is elevation, not replacement. The shift moves from a reactive, human-centric model that burns people out to a proactive, human-managed one that scales with your business. 

The SRE agent handles the noise, the toil, and the first-pass analysis, making the SRE role more strategic and ultimately more sustainable.

Engineering leaders who invest in agent-assisted operations spend less time reacting and more time building. 

For teams ready to take the next step, how to choose an AI SRE solution is a strong starting point

The post SRE agent vs. traditional engineer: 7 key differences appeared first on PagerDuty.