principleModeratepending
YAGNI -- You Are Not Gonna Need It
Viewed 0 times
YAGNIsimplicityover-engineeringpremature abstractioncomplexity
Problem
Developers build features and abstractions for hypothetical future requirements. This adds complexity that is rarely justified.
Solution
Only build what you need now. Do not add configuration for single values, abstractions for single implementations, or extensibility hooks nobody asked for.
Why
Predicted requirements are almost always wrong. Building for them means maintaining dead code and being constrained by premature decisions.
Revisions (0)
No revisions yet.