The real cost of ignoring version control
The gap between knowing this and actually doing it is where most teams lose ground. Nobody bills you for neglecting version control. The cost shows up somewhere else.
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.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- Small commits with clear messages are a gift to future you
- Rework, once the problem is finally visible
Branch naming conventions cost nothing and prevent confusion. The teams that handle this well are rarely the ones with the biggest budgets. Check it against what you would want a competitor's site to get wrong.
Making it stick
If it is not in version control, it does not exist. None of that requires a large budget, only a decision and someone to own it. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.
What this looks like day to day
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
If you are not sure where your systems currently stand on this, it takes us about an hour to find out.