Site reliability engineering

Once you have logged in or zeroed in to a vendor, then coming to deployment, you have to have buy-in from your stakeholders.

Because let's say, you could be running a microservices architecture or you can't, but essentially you have to have DevOps or SRE team or the entire engineering team giving you a buy-in that, hey, we want to support you for the deployment.

Because service owners need to know what's happening, what you're going to deploy within their service.

So all in all, it took us almost, I think, 90 days from zeroing down from a vendor to full-scale deployment.

You start with just deploy.

Can we deploy everywhere? What can we observe? And then start to go from that observation to blocking as it makes sense.

Along those lines about just working with the developers, working with SREs, for example, SREs in particular are very sensitive to latency or performance.

Were there aspects of the rollout or aspects of just the eBPF that were actually pointed to as benefits for the developers? The developers got something...

Yeah, we probably do have a lot of great favorites in SREs.

I have been on the record as saying AI SRE is one of the hardest categories for agent startups.

I think I might be wrong soon, but so far it's been correct.

AI has not cracked SRE for whatever reason.

No, no, no, not yet.

I agree.

decreasing in the industry.

And then to be able to support many, many teams that are developing much more software, I think the SRE, the infrastructure, the developer experience or developer platform type teams or roles, I would expect those to continue to hold or there's going to be an increased demand in those types of roles.

And that really doesn't get into anything that's more agentic or AI focused on the development side.

That's just more holistically, more kind of broader generalist type engineers, more folks that can support more engineers and the infrastructure that would be required to to support the development and the deployment of just more software being created.

I'm Brian Teller from Teller's Tech, and this is Ship It Weekly.

Welcome back to Ship It Weekly, the show about the DevOps, SRE, cloud, platform, and security stories that matter when you're the person keeping the thing running at 3 in the morning.

For the weekly story list and source links, check out OnCallBrief.com. For past episodes and show notes, head over to shipitweekly.fm.

This week is very much a supply chain week.

If your alert roles filter on the name, move them to business ID before then.

The human closer this week comes from Brent Chapman of Great Circle Associates, who used to lead incident management at Google and Slack.

It's a piece featured in SRE Weekly called Stop Paging on How Your Machine Feels.

He starts with the customer who finds the outage before your monitoring does.