No, I don't think so. However, not all monoliths are created equal!

Trunk-Based Development is the standard everyone commercial software project should aim for.

Pull requests are like bread. They go stale quickly.

I join the Lovin' Legacy podcast to talk about DevOps, the Go language, and implementing Continuous Delivery in reverse. Have a listen.

I join the Agile Embedded podcast to discuss continuous delivery, and how to implement it in reverse.

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

If you work in small enough batches, you'll never care if your story is "worth" 8, 3, or 233 points.

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.

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.

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