Product Between Quality and Over‑Engineering
summary
The talk examines over‑engineering in software product development, showing how building overly complex solutions “just in case” trades quality concerns for speed and raises costs, delays, and system complexity. It outlines concrete examples and practical tips to avoid this trap and keep development aligned with actual user needs.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:09Speaker introduction
- 3:57Over-engineering in cars
- 5:22Spotting software over-engineering
- 8:29Software quality defined
- 12:23Balancing QCD triangle
- 13:47DORA metrics for performance
- 17:14Accelerate capabilities
- 19:01Over-engineering in code examples
- 27:54Non-technical over-engineering causes
- 30:22Over-engineering in orgs and processes
- 32:50Over-engineering product impact
- 33:30Avoiding over-engineering tips
- 35:58Recommended resources and conclusion
- 36:20Q&A
related talks
41mProduct between quality and Over-Engineering
33mProduct Between Quality and Over-Engineering
25mOverengineering 101: what is it and how to avoid it?
41mA Defence of Technical Excellence
56mControlling Quality in Software Development
36mOverengineering: Causes, Symptoms and Treatment
39mEvolutionary Software Quality
46mThe Case for Technical Excellence