There's almost always more than one way to do something. What workflow does your team use for CI/CD?

CD leaves room for manual approvals, but once approved, all changes should be applied automatically.

With a platform-team, there's no confusion over the question of specialization, as it's clear who does dev work and who does ops work.

Jonathan Hall joins the Adventure this week to discuss the advice he gives to clients to start continuous deployment before they have automated tests around their code.

There's no one-size-fits-all solution to all testing needs. Ephemeral review environments are great, but they don't solve all problems. Most teams will also want a long-lived staging environment, too.

Simply adding a linter to your build pipeline is usually the simplest, cheapest single step you can do to improve code quality.

We automatically created a test environment for every pull request, and it had a revolutionary impact on the development process.

As usual, the biggest obstacle to Continuous Deployment was the fear of losing control.

An overlooked benefit of Continuous Deployment is the psychological change that developers feel when they know that "Merge" means "Go live".

What's the smallest step you can take today toward improving your software delivery?

In 2009, many thought 10+ deploys per day was inconcievable. Today it's boring. I call that progress!