How my children forced me to adopt DevOps at home, and how it helped at work, t
summary
Home cleaning example shows small batches beat big bangs: vacuuming every room fails when kids interrupt and one job stretches from one or two hours to three. Company shifts from outsourced code to an in‑house team building the Suru water sensor IoT product for insurers. Deployment cadence moves from months to six weeks then four then two weeks with a goal of on‑demand. Engineering adds monitoring and live testing, a quality gateway that runs unit and integration tests plus SonarCloud and coverage gates, and migrates new code to TypeScript to reduce bugs and enable trunk based, cross functional teams so errors surface early and deployments become lower risk.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:48Children disrupt home workflows
- 3:33Optimizing workflows with small batches
- 4:56Suru challenges
- 8:07Balancing stability and adaptation
- 8:48Bottlenecks in deployment
- 10:54Code quality and testing
- 13:02Adopting TypeScript
- 14:29Quality gateways for PRs
- 16:16Dev and Ops team issues
- 18:02Unifying team ownership
- 19:45Trunk-based development
- 21:12Reducing handoffs
- 22:40Cross-functional teams
- 24:07Frequent deployments benefits
- 25:52Key takeaways
- 26:53Q&A
related talks
34mYou only have to change one thing to do the DevOps
30mWhat's It Like When DevOps Is Just Another Day at the Office?
36mDevOps in Outsource… Really!
21mBuilding A DevOps Culture in a Remote World
17mBeyond DevOps – Holistic transformations in uncertain times
22mA Healthier Software Development Life Cycle with DevOps
25mDevOps Bringing a New Concept to Software Quality
25mDevOps Handbook Experiments in Accelerating Delivery