Why You Should Set up an Automated Pipeline From the Get-Go

Build the foundations before you write any code

Photo by Sebastian Morelli-Peyton on Unsplash

This is the fourth post in the series, “5 Strategies for Serverless Testing”. Check out the first, second, and third post. If you like this content, feel free to share and subscribe!

---

When working on a serverless project you should start by setting up an automated CICD pipeline first.

This is the sort of advice that everyone (at least, every engineer) would want to be true but that we find difficult to justify, at least in our heads.

Some reasons for not doing it (and instead diving deep into writing code) include:

• a desire to start “delivering value” quickly;

• pressure from management or the product owner;

• lack of clarity about what it is that we're actually trying to build;

But here are a few reasons why every software project (especially a serverless one) should start with some basic level of automated infrastructure: