(2) Talks - Putting 200 Developers On Call and Failure is Inevitable

Hello Seattle DevOps Meetup friends! 🙌🏽

Meetups will continue to be held during one Wednesday each month via Zoom. Each meetup will feature 2 talks about 20 minutes long with 5 minutes reserved for Q+A. No product demo or pitches please—we want to focus on learning, not selling.

Agenda:

4:00pm - Welcome + Networking

4:15pm - 4:45pm - Alina Anderson, Senior TPM at Outreach "Survival Guide: What I Learned From Putting 200 Developers On Call"

4:45pm - 5:15pm - Julie Gunderson, DevOps Advocate at Gremlin "Failure is inevitable in modern, complex applications"

5:15pm - Wrap up

** Times are approximate

Alina Anderson - Bio
Alina is a Senior TPM, cat herding organizations through complex challenges at the intersection of humans and systems. Over the last six years, she has navigated on-call through pre-IPO hypergrowth to Enterprise scale. Alina is committed to giving back to the Seattle Devops community through Ada Developers Academy mentorship, co-organizing DevOps Days Seattle and volunteering on the King County crisis hotline.

Abstract
Survival Guide: What I Learned From Putting 200 Developers On Call
We want to live in a world where the development team who writes the code, also owns that code’s success...or failure, in production. Nothing incentivizes a team to ship better quality software than getting paged at 2am, but how do we do this? In this talk, you’ll learn some tips and tricks for easing less than enthusiastic development teams into on-call rotations, how SRE facilitates the transition to production code ownership and why SLOs are critical to your success.

Julie Gunderson - Bio
Julie Gunderson is a Sr. Reliability Advocate at Gremlin, where she works to further the adoption of Chaos Engineering principles and methodologies. Over the last seven years, Julie has been actively involved in the DevOps space and is passionate about helping individuals, teams, and organizations understand how to leverage best practices and develop amazing cultures. Julie is also a founding member of DevOpsDays Boise.

Short Description:
Failure is inherent in complex systems. But rather than being painful and costly, you can intentionally inject failure, using Chaos Engineering to improve your applications and processes.

Abstract:
Failure is inevitable in modern, complex applications, but with Chaos Engineering, you can minimize the effect on your organization and customers. We’ll share why Chaos Engineering is a critical part of the software lifecycle and how you can implement it in your organization.
In this session we’ll cover the cost of incidents, where Chaos Engineering came from and why it’s important, how you can begin implementing Chaos Engineering in your organization, and we’ll share a couple case studies to highlight the real-world benefits of practicing it.