- Type 1 error: premature optimization/generalization/etc. You spend time scaling something that doesn’t sell, or designing a generic platform that only gets used once.
- Type 2 error: technical debt. By the time you realize you have a scaling problem it’s too late, and your users end up unhappy. Or, your lack of CI processes and tests slows down future releases.
Ref :
- https://twitter.com/ThePracticalDev/status/821089706284904449
- https://dev.to/wrschneider/balancing-early-and-later-project-risks
A smaller, faster, better way to build software