Breaking Hero Behaviour
summary
Builds a quick prototype pipeline to replace legacy sneakernet deploys and shows it still runs years later as the company’s only gateway to production, creating a single point of failure. Describes automations that become maintainable only by one person, repeated 3am firefights, and burnout. Switches strategy: stops immediately fixing alerts in a neglected Slack channel, lets incidents surface, documents fixes, and redesigns for transparency and resilience so the team, not one hero, owns production.
AI-written summary · about
related talks
21mEliminating Hero Culture on our Engineering Teams
17mEliminating hero culture in software engineering teams
19mFireside Chat with Quintessence Anx
26mPrevent Heroism: How to Work Today Reduce Work Tomorrow
42mFrom Chaos to Control, from Control to Freedom
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
15mIncident Ready: Chaos Engineer Your Incident Response
28mDevOps Stories; Think outside of your Pipelines
