Continuous Delivery (CD) is a software development discipline where you build software in a way that it can be released to production at any time, even if your scrum master is breathing down your neck. CD is like having a perfectly coiffed and styled app that's always ready for its close-up on the production red carpet, while you're stuck in the green room debugging its less glamorous cousin, Continuous Integration.

How to use it in a sentence

• I was going to push that new feature to production, but then I remembered we're doing Continuous Delivery (CD) now, so I guess I'll just keep polishing this turd until it's deployable.

• Oh, you're still doing bi-weekly releases? That's cute. We've achieved Continuous Delivery (CD) nirvana over here, deploying to production every time someone accidentally hits Ctrl+S.

If you actually want to learn more...

• Continuous Delivery by Martin Fowler: Learn about the key indicators of CD, how it differs from Continuous Deployment, and why you should care (even if you'd rather be writing code).

• Continuous Delivery Guide on Martin Fowler's website: Dive deeper into the challenges of implementing CD, from managing source code branches to applying CD principles to machine learning applications.

• Software Delivery Guide on Martin Fowler's website: Explore the broader context of software delivery, including Agile, DevOps, and Infrastructure-as-Code, and how they all tie into Continuous Delivery (CD) (because apparently, everything is connected in this cruel, cruel world of software development).

Note: the Developer Dictionary is in Beta. Please direct feedback to skye@statsig.com.