YAGNI (You Ain't Gonna Need It)

Overview

Don't implement something until you actually need it.

Every feature has a cost: code to write, tests to maintain, complexity to manage. Speculative features often go unused while creating real burden.

When to Use

• Adding features "users might want later"
• Building "production-ready" infrastructure upfront
• Adding flexibility "in case requirements change"
• Implementing patterns "because best practices"
• Creating abstractions for hypothetical use cases

The Iron Rule