Recently, I've been asked by a group of people to provide arguments that should convince developers and managers to use a CI/CD infrastructure. If you're a developer and you haven't been frozen in an icy lake somewhere in Greenland for the past 8-10 years, you don't need to be convinced. Please, move on. You'll only read what you're used to do daily. And to thank you for stopping by, here's a nice photo of a dog:
![We all don't](https://camo.githubusercontent.com/f67bb85a534b95c8254bafe23e93859b4ec3fbc502582c3efbccdfb7369c6db8/687474703a2f2f7777772e737572656973637574652e636f6d2f696d616765732f3530333630653430316434316338373732363030303133302e6a7067)
So, if you're still here, it means you're in doubt of how CI/CD will play a role in our software development utility belt. Although we all know that automated tests and even a simple CI/CD infrastructure are the foundation of modern software development practices, I wasn't able to answer their questions right on spot. I mean, it's obvious that what we do has benefits, but we still don't know how to quantify them. Often, we see folks banging their heads against the wall trying to figure out _wh