The Cost of a Bad Code and Pipelines
summary
Bad code shows up as unreadable variables and magic numbers in loops, pipelines waste time by rebuilding unchanged assets and running slow CI (examples: builds stretching 40–60 minutes versus 15–30), and failures can cause multi‑hour rollbacks (one incident ~3–4 hours). Claims: average developer works 41.1 hours weekly, spends 13.5 hours on technical debt and 3.8 hours on bad code, bugs in production cost up to 100× more to fix. Fixes start by assessing, asking why, measuring build time, adding notification triggers, and adopting prettier js and eslint.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:42Bad code and pipelines
- 4:06Bad code example
- 6:56Bad CI/CD pipeline
- 8:41Cost on productivity
- 11:46Stripe study
- 13:33Financial impacts
- 18:51User experience impact
- 20:20Transforming code and pipelines
- 25:53Summary
related talks
46mLet Them Eat Code
43mClean code, is it really worth it? A story about monsters and...
25mClean Code, is it really worth it?
43mClean Code: Be The Hero
13mShift left the proper way
38mCode Red: The Business Impact of Code Quality
25mCI/CD Delays: Losing Time, Money & Sanity
11mRefactoring: Managing technical debt before it blows up in your face