YAGNIYou Aren't Gonna Need It
Extreme Programming · Kent Beck and Ron Jeffries
Don't build it until somebody needs it.
Every feature you build "for later" costs you now. It's more code to read, more to break, and more for the AI to trip over next time. And later usually never comes, or it shows up looking nothing like you guessed. Build for the users you have this week, not the ones you hope to have next year.
You ask for a simple invoicing tool. Claude decides you need microservices, user roles and a job queue to support your future 10 million customers. Brother, you don't have one customer yet.
You're Breaking It If
- You have an admin panel, team accounts and an API. And no users.
- There's a settings page full of settings nobody has ever changed.
- You've said "we'll need this when we scale."
Do This Instead
Ask for the smallest version that works, and make the AI write down its "you'll probably want" ideas instead of building them. Build one when a real user asks for it twice.
Build only what I asked for. Don't add features, settings, user roles, abstractions or infrastructure for future needs. If you think I'll need something later, don't build it. List it at the end under "Not built (yet)" with one line on why, and I'll decide.