Continuous Disintegration
summary
Asks whether current systems gate who's allowed to ship and discovers that a company tool called Glitch lets anyone edit and push to production — a colleague edits a recruiting survey and it goes live mid-conversation. Shows the concrete tradeoffs: empowering non-engineers reduces friction but requires rollout controls, rollback and audit tooling, and clearer permission models. Notes a concrete diversity target — 50/50 gender balance goal — and frames changing assumptions about who should have permission as an operational design problem with measurable outcomes.
AI-written summary · about
chapters (4)
related talks
20mFireside Chat with Emily Freeman
05mRadical Transparency for Software Teams
44mDevCorp: Choose Your Own Adventure
33mWhat Got Us Here Won’t Get Us There: A Story of Transformations
45mThe DevOps Revolution: We Haven't Always Known Everything
29mDevOps Anecdotes
35mHow DevOps Friction Turns into Real Products
36mWe Have a Complex Systems Problem…and We Need to Talk About It
