Greenfield

Adjective · Noun · Hacker Culture

Definitions

A project built from scratch with no legacy constraints — a blank slate. The opposite of brownfield. Named after undeveloped land, it's every developer's dream assignment (until they realize they have to make all the decisions themselves).
In plain English: Starting a software project completely from scratch with no old code to work around — exciting but also overwhelming.
Example: "A greenfield project sounds fun until you realize there's no Stack Overflow answer for the choices no one has made yet."
The greenfield paradox: the freedom to make any decision leads to decision paralysis. Without existing constraints, teams can spend months debating technology choices, architecture patterns, and coding conventions before writing a single line of business logic.
Example: 'We got a greenfield project and spent the first month arguing about the tech stack. Turns out constraints are liberating — when you can pick anything, you can't pick anything.'
Source: paradox of choice

1960s: Urban planning coins 'greenfield' for undeveloped land — literally a green field with no existing structures
1990s: Software developers adopt the term for projects built from scratch with no legacy constraints
2010s: Greenfield projects become a developer fantasy — no technical debt, no backward compatibility, just pure possibility