Delivering imperfect software

on YouTube ↗11m

" summary

Claim: shipping good‑enough software is deliberate and measurable not sloppy. Example: a same‑day care platform at Providence St. Joseph Health trades an initial AWS SQS design for a simpler database table to meet deadlines, surfaces a race condition via automated intent tests, and stays shipped while a cleaner SQS / DB redesign is deferred. Team rituals include LGTM PR committee approvals, blameless weekly operational excellence RCAs and pager reviews so releases iterate without losing trust.

AI-written summary · about

" chapters (13)

1. 0:00Intro
2. 0:53Shakespeare
3. 1:06Release imperfect software
4. 1:58Stop and think
5. 2:56Tradeoffs
6. 4:25LGT PR
7. 4:48Merging
8. 5:40Tech debt
9. 6:24Story time
10. 8:24Good enough is good enough
11. 9:01Rootcause analysis
12. 9:53Elephant in the room
13. 10:18Outro

" related talks

• 38mBuilding a high quality productFinn Lorbeer · DevOne Detroit 2018
• 35mBetter, Faster, Stronger - Delivering High Quality ProductsFinn Lorbeer · TestCon Vilnius 2018
• 26mSoftware Delivery from First PrinciplesJosh Reed · DevOpsDays Montréal 2024
• 45mThe Goldilocks Problem of Software DeliveryAnders Wallgren · All Things Open 2020
• 38mJust Ship It!Nikolaj Tolkaciov · TestCon Europe 2021
• 52mBeyond FeaturesDaniel Terhorst-North · Jfokus 2016
• 21mScaled Agile DevOpsBryan Finster, Dana Finster · DevOpsDays Eindhoven 2022
• 41mContinuous delivery in 10 easy mistakesKim van Wilgen · Codemotion Amsterdam 2018