Version Control

Version control is the discipline from which all modern software quality flows: every change to the codebase is recorded — who, what, when, why — in a shared history that nothing overwrites. It is the reason a team of fifty engineers can change one product simultaneously, and the reason 'what changed?' is always an answerable question.

What It Is

Version control (source control) records every modification to files — code, configuration, documentation — as a commit: an atomic change with author, timestamp and message, building an append-only history from which any past state can be reconstructed. Modern practice is distributed (Git being universal): every engineer holds the full history, changes converge through pushing and pulling to shared repositories. The discipline's power structures everything else: branches isolate in-progress work, merges integrate it, pull requests gate it through review, and tags mark released versions. The equivalent for infrastructure — infrastructure-as-code under version control — extends the same record to the environment itself.

Why It Matters to You

Version control is non-negotiable engineering hygiene, which makes it a useful floor-level due-diligence probe: a software vendor not using it is disqualifying, full stop — there is no credible engineering practice without it. Beyond the floor, the history is an evidentiary asset: when a defect appears, the exact change that introduced it can be identified (and its author, reviewer and date); when a dispute arises about what was delivered when, the commit log is the record. In acquisition due diligence, a clean version history is part of proving the provenance and ownership of the code itself.

When You'll Meet It

In engineering assessments and vendor due diligence. The single diagnostic question: 'show me the commit history' — its cadence, messages and authorship pattern tell you more about a team than any capability deck.