There is a sweet spot in optimizing for quality. The further you try to maximize something, the less benefit you get. At some point, the quality becomes useless and only serves as an art piece. This applies to many things, such as writing, architecting software systems, coding, etc. We need to carefully analyze the relation between the cost and the quality and try to keep it balanced.
- Related Note(s):
- 19d: Why can’t this be done sooner?;
- 2: How to Improve Writing;
- 17: Public Speaking and Improving Skills;
- 21: Efficient Code Review Process (The changes I wanted to do in one of my teams);
- 48: System Design Index;
- 50: Service Level Agreements/Indicators/Objectives - Percentiles;
- 56: Structuring Teams in Organizations;
- Source(s): The Cost-Quality Curve – commadot com
