Podcast
Tristan Watson
Senior SRE at Oak National Academy
Serverless removes servers from the developer's view—not from the incident. Tristan Watson explains how observability, Slack, and OpenTelemetry help teams recover the context abstraction hides.
Podcast
Matt Gowie
CEO & CTO of Masterpoint
Matt Gowie has seen infrastructure fail badly enough to remember every detail. He explains when infrastructure as code becomes essential, how to weigh OpenTofu against Terraform, and why he still climbs.
Discover simple yet effective strategies to decrease work-related stress and increase productivity for DevOps and SRE professionals. Transform your work life with these 5 easy tips from your friends at Rootly.
The Google books offer helpful general principles. In practice, however, you shouldn’t assume they are immediately applicable to your environment. Some companies have comprehensive, high-quality documentation, mature incident response tooling, and more importantly, experienced ICs. However, if your
Podcast
Adama Lorna
SRE @ Ticketmaster
Geography led Adama Lorna to maps, curiosity led her to SRE, and YouTube gave her a place to bring both together. She reflects on opening tech's doors without shrinking life to a single identity.
Podcast
Stefan Kolesnikowicz
Principal SRE
What changes when an SRE reaches the principal level? Stefan Kolesnikowicz talks influence, continuous learning, and the open-source tools he trusts—then makes room for cameras and guitars.
Podcast
Tony Holmes
Head of SRE
Tony Holmes was a sysadmin before SRE had a name. Now leading SRE at Affirm, he reflects on what the craft retained, how severity guidelines fail, and why mentorship is leadership infrastructure.
Before I stumbled into the tech industry (a story for another day), I spent several years in the customer service world as a server and front of house manager in restaurants. It was in these jobs that I first honed some critical skills that would later lead me on the path to incident response. In th
Podcast
Chris Ferraro
VP, Platform Engineering
One brutal incident taught Chris Ferraro what resilient engineering leadership actually requires. He explains why people return after failure—and how managers shape what happens next.
Podcast
Kolton Andrus
CTO & Co-founder
Before chaos engineering became a category, Kolton Andrus watched Netflix teach systems to survive failure on purpose. He shares how the idea won skeptics—and became a company.
Podcast
Mason Jones
Director of Engineering, Internal Platform
Startups move fast until their first incident makes time stop. Mason Jones offers advice for that moment, the cultural warning signs leaders miss, and why engineering wasn't his only creative bet.
When incidents reach a heightened level of complexity and scale, Strong argues that companies ought to consider having multiple lead roles present, rather than a single Commander overseeing the entire response. In this post, he breaks down when and how he recommends you consider bringing additional
Page 6 of 9 · 99 entries