DEV Community

Jonathan Hall
Jonathan Hall

Posted on • Originally published at jhall.io on

“Greenfield” doesn't exist in agile projects

Many engineers love the idea of working on greenfield projects. That is, new projects, where design mistakes and technical debt have not yet been acrued.

I’ve worked on a number of such projects over the years, but there’s a problem that’s practically always overlooked with these types of projects.

A greenfield project is only greenfield for about a week.

Very quickly, you’ll start bumping into decisions you made, which don’t fit the current circumstance perfectly, and you’ll begin refactoring. You’ll begin to see that you’re working on a brownfield project.

What can you do?

Stop dreaming of your next greenfield project, and just learn to deal with technical debt, legacy code, refactoring, and all the other things that come with the territory.


If you enjoyed this message, subscribe to The Daily Commit to get future messages to your inbox.

Heroku

Build apps, not infrastructure.

Dealing with servers, hardware, and infrastructure can take up your valuable time. Discover the benefits of Heroku, the PaaS of choice for developers since 2007.

Visit Site

Top comments (0)

AWS Security LIVE!

Join us for AWS Security LIVE!

Discover the future of cloud security. Tune in live for trends, tips, and solutions from AWS and AWS Partners.

Learn More

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay