Slow but Faithful vs Fast but Crooked: The Modern Development Dilemma
summary
A CTO from Uspacy discusses balancing rapid feature delivery against technical quality and managing technical debt, using their startup’s development as a concrete case study. The talk describes specific mistakes they made while prioritizing speed, the consequences that followed, how they resolved accumulated problems, and lessons learned about decisions that could have been different to better balance speed and correctness.
AI-written summary · about
chapters (9)
- 0:00Speed vs quality
- 3:18Microservices and fast releases
- 11:49Automation and monitoring
- 17:14Growth issues from speed
- 20:38Critical errors: UX and bugs
- 24:17Frontend re-renders and tech debt
- 28:16Refactoring costs
- 30:25Key takeaways
- 36:20Q&A
related talks
23mThe Cost of Speed: Rethinking "Move Fast" in DevOps
40mDeveloping at Cruise Speed
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
41mA Defence of Technical Excellence
29mEconomies of Speed
22mOptimizing Product Development: Balancing Speed, Quality, and Process
39mStop Focusing on Tech Debt
42mBuilding Fast and Slow: Contextual Product Management