How DevOps Friction Turns into Real Products
summary
Panelists argue the marginal cost to prototype internal tools is now near zero but long tail maintenance and interoperability are the real costs; an incident tool built at Monzo becomes Incident.io and open source Backstage rollouts clarify requirements at a 55,000‑engineer shop. Advice: build first 20% to learn depth, use CI/CD, golden paths and project bootstrappers to drive adoption, don’t reimplement orchestration primitives, and design every system for agents as default end users while keeping humans in the loop.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 1:09Panelists and their backgrounds
- 4:16Build vs buy internal tooling
- 17:49Driving adoption of DevOps tools
- 24:08Building with AI in mind
- 26:59Q&A session begins
- 35:00Closing remarks
related talks
25mBringing Product thinking to DevOps
26mTen Product Mindset Rules for DevOps Teams
47mDevOps is for Product Engineers, too.
30mEverything Is A Product...
17mBeyond DevOps – Holistic transformations in uncertain times
32mTales from the DevOps Transformation Trenches
05mHelp! My DevOps team is stuck!
30mA Story of DevOps Transformations