Product Between Quality and Over-Engineering
summary
Examines over-engineering in software: building overly complex solutions (applying SOLID, DRY, OOP, design patterns prematurely) that prioritize perceived quality over delivery speed. Explains costs—higher development time, increased complexity, and expenses—and offers concrete examples and practical tips to avoid this trap in real-world mobile/embedded development.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:33Over-engineering in auto industry
- 8:56Software quality definition
- 14:12Agile vs quality-cost-time
- 20:55Over-engineering in code
- 26:08Non-technical reasons
- 30:23Consequences and product fit
- 32:56Avoiding over-engineering
related talks
37mProduct Between Quality and Over‑Engineering
25mOverengineering 101: what is it and how to avoid it?
37mEngineering for Software
01h 01mEngineering for Software - How to Amplify Creativity
27m'The Art of Software Development'
41mA Defence of Technical Excellence
30mWhy should I write software well?
26mFacing the "Quality" Problem in Long-Lived Codebases