Actually, how can we trust manual tests in high-stakes scenarios?

It's not continuous deployment if you aren't deploying... continuously.

Does continuous delivery seem like a nice, but distant, goal? I'm launching a 4-week program to help you get un-stuck.

Jason Adam is a software developer with a non-traditional background in biology, business development, and data analytics. Now he's active as a developer, and on the lookout for proven practices he can introduce to his team. On this episode we talk about Trunk-Based Development, and the related topics of continuous integration and deployment, infrastruture as code, and much more.

I found a tool to make code freezes easier. Ick. But could it ever be useful?

Even with long-running feature branches, you can merge something daily. A bug fix, refactor, or utility function.

Commit your work daily, even if it's a WIP. Push it to the server. Open a pull request. Don't be afraid of sharing your incomplete work.

CD is much more than automated deployment.

Every refactoring tends to entangle all the other functional changes together, which makes it even harder to advance changes to the production branch.

With different teams responsible for development and release, we often end up with silos.

Lack of unit testing drives the need for manual testing. Since testing is bunched up, development is as well.