Shipping Quality Software in Hostile Environments
summary
After eight years of features-only development the codebase reaches tech bankruptcy with a 10GB monorepo that stalls work and a deploy pipeline where a single commit takes hours. The team rebuilds the Jenkins pipeline in the cloud with Ansible rebuild recipes, introduces database schema changes via reviewed SQL scripts, removes VPN for daily dev, and incrementally splits into 40 smaller repos, cutting commit-to-live from hours to seconds over 18 months while preserving history and improving morale.
AI-written summary · about
chapters (13)
- 0:00Who am I?
- 0:45Hostile Environments?
- 1:08Tech Debt?
- 2:30Where does it come from?
- 4:55What's the Harm?
- 7:09Case Study
- 12:34How do you even begin to fix this?
- 17:18The Moral of this Story
- 18:48How do we do Better?
- 20:22Time for a New Approach
- 21:20New Name: Sustainability Work
- 21:54Budget VS Planning
- 22:51Helps with Morale
related talks
27mConcept to Code to Runtime - Simplify, Enable, Exploit
33mMaking Strides towards Enterprise-Scale DevOps...w/ Jenkins in Your Tool Chain
01h 12mPitfalls of Continuous Deployment
35mTaming a beast
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
30mA Journey Introducing Jenkins to Enterprise IT
22mCreating a team mindset of continuous improvement
43mTransformative Culture