When version control is worth the effort

It comes up on almost every project, usually later than it should. Version control is not free, and pretending otherwise leads to bad decisions.

Most development decisions are really maintenance decisions wearing a different hat. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.

When it is worth it

Small commits with clear messages are a gift to future you. The cost of getting this wrong is rarely visible on the day it happens. Budget a little time for it every quarter and it never becomes a project of its own.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. The teams that handle this well are rarely the ones with the biggest budgets.

How to decide

If it is not in version control, it does not exist. It is worth being explicit about, because assumptions differ quietly. It is the sort of thing that looks like polish right up until it costs you an enquiry.

In practice

The question is rarely whether something can be built, but what it costs to keep running afterwards. Three things worth confirming about version control before you move on:

• Someone can say what the current setup is without going to look
• Branch naming conventions cost nothing and prevent confusion — 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.