Myth-Driven Design
summary
The talk examines common myths in software architecture and development that circulate from tutorials and GitHub, and refutes claims like “no tests is faster,” “we don’t do D/B/TDD because it’s complicated,” “CQRS requires two databases,” and “no upfront design because we’re agile.” It uses concrete examples from architecture and development practices to debunk these misconceptions and promote evidence-based approaches that improve systems for stakeholders.
AI-written summary · about
chapters (10)
- 0:00Introduction to IT myths
- 7:37Myth: Tests slow development
- 13:18Myth: TDD only for calculators
- 18:56Myth: DDD is complex theory
- 24:04Myth: CQRS is just two databases
- 31:08Myth: Efficient domain events
- 34:15Myth: Event sourcing is event streaming
- 36:24Myth: ORM is necessary evil
- 39:14Myth: Design is unnecessary
- 43:34Summary and sources
related talks
01h 01mSoftware Design: Myths and Legends
08mLightning talks – 101 Things Software Never Learnt
41mThe lost art of software design
55mHigh-speed DDD
45mFive things every developer should know about software architecture
44mCognitive Biases Driven Architecture?
48mObject modeling: Theory vs Practice. Round 1
45mFive things every developer should know about software architecture