I've noticed a trend of defending what is mistakenly believed to be GitFlow.

Technology comes and goes. Why do we still use GitFlow, but not Windows Mobile? Why did we stop using 5.25" floppies, but never fully adopted static analysis?

GitFlow vs Trunk-Based Development is like Coke vs. Pepsi, right? Not really.

If you heard about Continuous Delivery you might find it sounds great, but you are not ready for it because [insert excuse here].

Coach Denis interviews me about my mission to bring enterprise-class software delivery to small teams with small budgets.

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

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.

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

Multi-stage software delivery means no hotfixes, or lots of extra work.

Lines of communication go up as team size increases, but that's not all. Consider merge conflicts.

Push to your staging branch as needed, but don't make it a mandatory step toward production.