DevOpsDays Boston 2022 - We can’t all be Shaq: why it’s time for the SRE hero... by Malcolm Preston

Channel:
Subscribers:
42,400
Published on ● Video Link: https://www.youtube.com/watch?v=9EYAtsn0e9Y



Duration: 16:29
38 views
1


We can’t all be Shaq: why it’s time for the SRE hero to pass the ball and how to make it happen by Malcolm Preston

Shaquille O’Neal is one of the most celebrated NBA players of all time. He played for six teams over his 19-year career and won countless awards — and for good reason. When the team needed two points, they knew they could throw the ball to Shaq, and let him go to work. He’d inevitably push someone around (hard not to do at 7’1” and 300+ pounds), dunk the ball, and the crowd would go wild.

The skills (and probably the size) are different, but there are a lot of engineers playing the Shaq role at their company. When the 2 a.m. outage page goes out, they’re the first to respond. These nebulous heroes find the problem, determine the affected areas, fix the issue (or know who to call to fix the issue), wake up the VP, draft messages to send to customers and stakeholders, create tickets to address why things went bad. Then at 9 a.m., they go back to the job they were hired to do. Backs are patted, and life goes back to normal until the next 2 a.m. page.

So what’s the problem here? Games are getting won, incidents are getting solved, it’s true. But are you truly setting your organization or team up for success by just “doing it for them” every time? A win doesn’t always have to come from a backboard-shattering slam dunk, and relying on the most dominant player to save the day isn’t a scalable solution for an organization’s continued success. Attend this talk to understand why it’s time to pass the ball and learn three ways you can take fast action to get there today.




Other Videos By Confreaks


2023-03-01RubyConf Mini 2022: Ruby Office Hours with Shopify Engineering by Rose Wiegley, Ufuk Kayserilioglu
2023-03-01RubyConf Mini 2022: Splitwise Sponsor Session: Declare Victory with Class Macros by Jess Hottenstein
2023-03-01RubyConf Mini 2022: Weaving and seaming mocks by Vladimir Dementyev
2023-03-01RubyConf Mini 2022: From Start to Published, Create a game with Ruby! by Cameron Gose
2023-03-01RubyConf Mini 2022: Anyone Can Play Guitar (With Ruby) by Kevin Murphy
2023-03-01RubyConf Mini 2022: The Case Of The Vanished Variable - A Ruby Mystery Story by Nadia Odunayo
2023-01-30DevOpsDays Boston 2022: Thomas Stringer - Zero to Secure: Using Open Service Mesh to Easily...
2023-01-30DevOpsDays Boston 2022: Andreas Grabner - DevSecOps by Default: What have, can and must we learn...
2023-01-30DevOpsDays Boston 2022: Kavitha Govindarajulu - Evaluating Your Toolbox
2023-01-30DevOpsDays Boston 2022: Steve McGhee, James Brookbank - Enterprise Roadmap for SRE
2023-01-30DevOpsDays Boston 2022 - We can’t all be Shaq: why it’s time for the SRE hero... by Malcolm Preston
2023-01-30DevOpsDays Boston 2022: Gad Salner- How to scale a unicorn-building engineering team (and stay sane)
2023-01-30DevOpsDays Boston 2022: Daniel Kim - Achieving 99.99% uptime with Open Source Observability
2023-01-30DevOpsDays Boston 2022: Peter Chestna - Feedback: You don't have to be bad to get better
2023-01-30DevOpsDays Boston 2022: Kam Lasater - How to Fail at Serverless (without even trying)
2023-01-30DevOpsDays Boston 2022: Adarsh Shah - From Infrastructure as Code to Environment as Code: ...
2023-01-16RailsConf 2022 - Diversity in Engineering; a community perspective
2023-01-16RailsConf 2022 - Keynote: RailsConf 2022 - It's been a minute! by Aaron Patterson
2023-01-16RailsConf 2022 - Testing legacy code when you dislike tests (and legacy code) by Maeve Revels
2023-01-16RailsConf 2022 - Don't page me! How we limit pager noise at New Relic by Chuck Lauer Vose
2023-01-16RailsConf 2022 - ELI5: A Game Show on Rails by Andy Glass



Tags:
DevOps
DevOpsDays