Balancing New Features While Maintaining Quality
summary
Practical rules for shipping: prioritize by measurable impact and effort using t-shirt sizing, balance urgent revenue features against stability by aiming for everyone to be “equally unhappy” as a decision heuristic, and invest in automation to shorten the dev loop. Instrument systems (QPS, DB IOPS, CPU, memory, network), run capacity tests and redlining to find failure modes, and focus on build delivery and testing systems, plus usage/land‑and‑expand metrics, not long theoretical architectures.
AI-written summary · about
chapters (5)
related talks
18mHow to be quick without being dirty: maintaining quality at high velocity
52mBeyond Features
35mBetter, Faster, Stronger - Delivering High Quality Products
30mDelivering Features VS Delivering Impact
45mThe Goldilocks Problem of Software Delivery
28mAvoid overengineering & big ball of mud- 7 lessons for maintaining the balance
01h 03mHow to defeat feature gluttony
38mBuilding a high quality product