More software engineering teams should understand YAGNI.
"You Aren't Gonna Need It" - Don't build features until you actually need them.
YAGNI violations show up everywhere:
- Configuration systems for settings that never change
- Abstract base classes with only one implementation
- Database schemas designed for use cases that don't exist yet
- APIs with endpoints that no one calls
Build for today. Refactor for tomorrow.