Need for speed - Moving fast as a software engineer
summary
A practical set of tactics for shipping faster: scope down to a minimal feature, map each task to the customer value it delivers, and prefer descoping over polishing. Uses real tools and experiments—Pho Ventures: new startup every two months, Wasp for low-code scaffolding, Cursor for context-aware AI coding, Amazon Kira and GitHub spec kit for spec-driven workflows. Argues code is a liability (teams spend ~50% of time debugging), so prefer buy over build, maintainable naming/linting/testing, and iterate in small, aligned increments.
AI-written summary · about
chapters (14)
- 0:00Introduction and context
- 2:17Why speed matters in engineering
- 3:22The art of descoping work
- 5:49DORA metrics and team capabilities
- 7:14Understanding customer needs
- 8:17Alignment and collaboration
- 10:02Code is a liability
- 11:50Less code for faster delivery
- 13:13Maintainable code bases
- 14:17New projects and AI tools
- 16:24Overcoming AI slop
- 19:10Spec-driven development
- 20:33AI-assisted development future
- 21:17Summary and closing
related talks
24mExpediency & Fluency
18mHow to be quick without being dirty: maintaining quality at high velocity
31mThe Effective Developer - Work Smarter, Not Harder
23mMoving Fast with XP
47mAI, Automation & DevEx: Fueling High-Velocity Engineering
50mThe Effective Developer - Work Smarter, Not Harder
58mTechnical Practices that Take Time but Save Time
19mScaling Fast – Engineering Lessons From ~15 Years of Tech Startups