Avoid merge conflicts, don't manage them
Or: why sweeping up the glass after an accident doesn't make you a responsible driver
Talking DevOps, Go and Continuous Delivery in Reverse on the Lovin' Legacy podcast
I join the Lovin' Legacy podcast to talk about DevOps, the Go language, and implementing Continuous Delivery in reverse. Have a listen.
Talking Continuous Delivery on The Agile Embedded podcast
I join the Agile Embedded podcast to discuss continuous delivery, and how to implement it in reverse.
Subscribe to the Daily Commit
Every day I write about improving software delivery at small companies like yours. Don't miss out! I will respect your inbox, and honor my privacy policy.Unsure? Browse the archive.
Who cares if we use GitFlow?
GitFlow vs Trunk-Based Development is like Coke vs. Pepsi, right? Not really.
No Nonsense Agile Podcast
Murray Robinson and Shane Gibson, had me on the No Nonsense Agile Podcast, to discuss implementing Continuous Delivery.
When story points become irrelevant
If you work in small enough batches, you'll never care if your story is "worth" 8, 3, or 233 points.
Implementing Continuous Delivery in Reverse - ATVIE22
If you heard about Continuous Delivery you might find it sounds great, but you are not ready for it because [insert excuse here].
Isn't it wasteful to build after every commit?
Continuous delivery provides some very cheap insurance.