Practical (a.k.a. Actually Useful) Architecture
summary
Gives 10 pragmatic recommendations: consciously pick domain/macro/micro perspectives, design team boundaries to match boxes, make a few strategic decisions centrally, and enforce the least viable number of rules, rigidly. Advocates ADRs, optimize for delivery flow as much as runtime quality, resist copying Netflix-scale designs, and favors boring tech — be boring: prefer Postgres over blockchain hype. Notes 80% of work comes from delivering software so architecture must survive implementation and change.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:2410 recommendations for pragmatic architecture work
- 1:511. Choose your perspective(s) consciously
- 7:452. Explicitly architect your team setup
- 13:223. Match your organizational setup to project size, etc.
- 17:394. Don't be afraid to decide things centrally
- 21:055. Pick your battles wisely
- 23:376. Enforce the least viable amount of rules, rigidly
- 29:527. Balance prescriptive vs. descriptive architecture
- 35:158. Don't aim for perfection - iterate
- 36:519. Architect for delivery flow as much as for runtime quality
- 39:2010. Be boring & do more with less
- 44:51Conclusion
- 46:08Outro
