How to Write Good Apps. Fast.
summary
Treat time as the primary budget and deliver small, testable increments using the Deming cycle (plan–do–check–act) to validate assumptions quickly. Plan and design before coding, use automated tests (TDD-style) as a design litmus, apply SOLID and Clean Architecture to keep code readable, avoid premature optimization and feature creep, refactor only when maintenance cost warrants it, and use lightweight requirement practices to cut rework and speed delivery.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:55Code quality myths
- 8:58Client requirements traps
- 13:14New technologies when
- 16:28Agile pitfalls
- 18:37Analytical thinking
- 21:06Early optimization avoid
- 23:13Requirements gathering
- 25:38Implementation design
- 27:06Test Driven Development
- 30:47Clean code SOLID
- 33:39Business value vs tech
- 35:23Optimization when how
- 36:52Refactoring process
- 39:41Software architecture simplicity
- 42:27Summary
related talks
58mTechnical Practices that Take Time but Save Time
47mHow To Build Future Proofed Applications
36mIterative Mobile Development
27mStop wasting time: 3 ways to build web applications faster and better
47mEverything I know about writing quality software
42mWriting Code for Humans, Not Computers
21mNeed for speed - Moving fast as a software engineer
40mBuild Better Software