Software Delivery —3 min read
How to handle long-running batch jobs during an upgrade

Two approaches to managing hours-long jobs with continuous deployment.

Software Delivery —2 min read
How to experiment with CD in a GitFlow environment

Can we experiment with continuous deployment without completely migrating away from GitFlow first? Here are a couple approaches.

Software Delivery —1 min read
How long does it take to deploy?

Don't deploy when you can't stick around to see it through.

Software Delivery —2 min read
How to safely deploy at any time

You write it, you ship it.

Software Delivery —1 min read
Don't deploy on payday!

Blocking deployments on certain days is an admission that standards are lower every other day.

Software Delivery —2 min read
You are advised to arrive at the airport two hours before your flight

Why do we have to arrive so early for a flight? How would you reduce the wait times?

Software Delivery —45 min episode
Tiny DevOps episode #40 Stacy Cashmore — The painful crawl through the morass of past shortcuts

Stacy Cashmore has the interesting title of Tech Explorer DevOps at Omniplan, which means she has free reign to do what she thinks she needs to do! In this episode, we talk about a big rewrite decision she made, and the results of this decision, good and bad, and in particular the effect of shortcuts taken.

Quality Engineering —3 min read
How to travel light

Software delivery is a lot like traveling. Less luggage makes for a better experience.

Software Delivery —4 min read
When I don't (exactly) use Trunk-Based Development

Today I go on record admitting I don't always use TBD, I do sometimes use long-lived branches, and I sometimes even share a branch with another dev.

Software Delivery —1 min read
Minimum Viable Continuous Delivery

A group of people with a lot broader experience than I have, come up with a pretty good definition of "Minimum Viable Continuous Delivery".

Software Delivery —2 min read
One not-so-simple trick to reduce your time fixing bugs

Continuous Delivery reliably predicts less time spent fixing bugs. How close are you?