Just published a new article about "The CI/CD Flywheel". Why it's such a superpower for teams that embrace it, and how it maps to CI/CD pipelines.

I dive into the different steps of the CI/CD flywheel, including local code authoring, running CI jobs on pull-requests, deploying and verifying on staging (preproduction) environments, and finally deploying and verifying in production.

Then, I try to showcase the business and technical benefits of a proper CI/CD pipeline.

Busines benefits: - Ship value to customers more often - Earn and retain customer trust - Fast experimentation feedback loop - Attract the right talent - Cost reduction

Technical benefits: - Code quality - Comprehensive tests - Automate repetitive tasks for reproducibility - Build once, use everywhere - Controlled rollouts and faster Mean Time To Resolution (MTTR)