Design Patterns · Junior · Question 33 of 75
What does the YAGNI principle mean?
- ✓Correct answer: Don't implement functionality until it's actually needed
- 2Always build in extra capabilities for future requirements
- 3Don't use third-party libraries; write everything yourself
Explanation
You Aren't Gonna Need It: premature generality ("what if we need five languages") costs time and complicates code, and the assumptions often don't come true. It's not a ban on thoughtful architecture but a stance against "just in case" code.