Navigating the SRE Landscape w/ Ricardo Castro

Navigating the SRE Landscape w/ Ricardo Castro

Join Robert Ross and special guest Ricardo Castro in a dynamic discussion that dives into the world of DevOps and the challenges and career progression of Site Reliability Engineers (SREs). They highlight the ambiguity surrounding the SRE role across different organizations and the difficulty in defining SRE levels. The importance of both technical and communication skills is emphasized, and the hosts address the difficulties in measuring the contribution of SREs, particularly in managing incidents.

Alerting, Incident Response, and the SDLC

In this episode we chat with veteran cloud architect Masaru Hoshi about the challenges of alert fatigue, the importance of effective alerting systems, and fostering ownership in software teams. Masaru shares insights from his 30-year career, emphasizing the need for balance, trust, and collaboration in incident response.

Practical Ways to Implement Incident Management with Shannon Schulte

Engineers have been managing incidents for about as long as they've been building software, but it's only in the past few years that incident management has become a primary focus for software teams. Today I'm talking to Shannon Schulte, an engineering manager of incident response about practical ways to implement incident management.

Focus on Assembly Time with Great Circle's Brent Chapman

When it comes to resolving an incident there are a number of metrics that can be misleading. Resolution time, for example, can fluctuate wildly. However, there’s one that we have a significant amount of influence over. Today, I’m talking to Brent Chapman, Founder at Great Circle, about how engineering teams should ditch metrics like MTTR and instead focus on what we can control; assembly time. Brent's Information: Website: https://greatcircle.com/ [https://greatcircle.com/] LinkedIn: https://www.linkedin.com/in/brentchapman/ [https://www.linkedin.com/in/brentchapman/] Twitter: https://twitter.com/brent_chapman [https://twitter.com/brent_chapman] ⁠https://esd.burningman.org/⁠ WW2 plane improvements [https://www.inc.com/minda-zetlin/steve-jobs-boeing-b-17-wwii-paul-fitts-alphonse-chapanis-code-shaping-ergonomics-design.html] Book - The Checklist Manifesto [https://amzn.to/3IcwJy2] https://slack.com/events/resolve-incidents-faster-in-slack [https://slack.com/events/resolve-incidents-faster-in-slack] https://slack.com/blog/collaboration/engineers-netflix-pagerduty-slack [https://slack.com/blog/collaboration/engineers-netflix-pagerduty-slack] https://slack.com/resources/using-slack/the-modern-incident-response [https://slack.com/resources/using-slack/the-modern-incident-response] https://slack.com/resources/using-slack/slack-for-incident-management [https://slack.com/resources/using-slack/slack-for-incident-management] https://slack.com/blog/transformation/incident-management-slack [https://slack.com/blog/transformation/incident-management-slack] https://slack.com/intl/en-in/events/minimize-incident-response-times [https://slack.com/intl/en-in/events/minimize-incident-response-times]

The Importance of Retros with CrowdStrike's Chad Todd

After the dust of an incident settles, it's normal for us to want to move on and get back to less stressful work. But doing so would skip an essential part of the incident management process, the Retro. Today, I’m talking to Chad Todd, Site Reliability Manager at Crowdstrike, about the importance of retros to avoid what he calls “Incident amnesia”.