top of page
  • Writer's pictureMatt Burrell

When Greenfield Doesn't Mean Greenfield

Updated: Feb 16, 2023

If you want to make a software developer happy give them a new project to work on and tell them they’re free to use whatever technologies they see fit.

Aside from giving them a pay rise, there’s no better way to motivate them. Developers love autonomy. (Who doesn’t?)

Knowing this, companies often advertise jobs as greenfield. Sadly, however, calling a project greenfield is usually misleading.

To see why, consider the Wikipedia definition:

“A greenfield project is one that lacks constraints imposed by prior work.”

To a software developer, a greenfield project means developing an application from scratch. But when it comes to job adverts there’s a catch.

If a single line of code has already been written the project is not greenfield.

The project has been constrained by prior work. You could even argue that it is constrained by legacy code.

Previous developers have already chosen a programming language, tech stack and mapped out a basic architecture. It doesn't matter if it's just a proof of concept because these tend to end up in production anyway.

So the only time a project can be called greenfield is if no code has been written. Maybe we should start using Tabula Rasa instead to describe true greenfield projects.

Recent Posts

See All

Why You Should Hire Product-Focussed Developers

You may be used to thinking of developers primarily in terms of their technical skills. But not all developers are solely focused on the technical aspects of their work. Many developers got into progr

Debunking Monorepo Myths

A monorepo is a version control strategy where multiple projects are stored in a single repository. I've noticed that some developers have a negative perception of monorepos due to past struggles with


bottom of page