Why continuous deployment matters more than it looks

This is one of those topics that looks small until it costs you something. Continuous deployment is easy to treat as a detail, and that is exactly why it is worth a few minutes of attention.

The question is rarely whether something can be built, but what it costs to keep running afterwards. If two people in the business would answer this differently, that gap is the actual problem.

What is actually at stake

Deploying should be boring enough to do on a Friday. This is the sort of thing that compounds, quietly, in both directions. It is the sort of thing that looks like polish right up until it costs you an enquiry.

Automate the checks you would otherwise forget. Getting it slightly wrong is survivable. Ignoring it entirely is not. Check it against what you would want a competitor's site to get wrong.

The mistakes we see most

Small frequent releases are safer than big rare ones. The reasoning matters more than the rule, because the rule has exceptions. Assume whoever inherits this will have half your context and none of your patience.

In practice

Most development decisions are really maintenance decisions wearing a different hat. Three things worth confirming about continuous deployment before you move on:

• Someone can say what the current setup is without going to look
• Automate the checks you would otherwise forget — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Most of the value here comes from doing the first two things, not all of them.