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

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

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

You write it, you ship it.

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

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

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.

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

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.

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

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