SRE was created by Google to balance prioritization of features needed for reliability and operations against others - like that shinny new product feature. However, just because we say we embrace SRE culture, mindset or have an SRE team, doesn't mean this problem is magically solved.
Ron Baker, IBM Distinguished Engineer of SRE Operations in Sustainability Software shares how he successfully negotiated and drove this balance and deliver on SRE features.
Timestamps:
[00:00 - 00:59] Intro to the episode
[01:17 - 02:14] What SRE means to Ron
[02:28 - 03:30] Ron shares what success in SRE looks like
[04:02 - 08:44] Solving the prioritization problem
[09:01 - 10:31] Connecting risk with emotions
[10:53 - 14:04] How Ron drives SRE features to reality once prioritization is tackled
[14:32 - 16:52] Words of wisdom for those in SRE professions
[18:00 - 20:24] Where SRE needs to go to stay competitive and help solve problems
[21:33 - 21:53] Ron's ingredient and recipe for the SRE Omelette