Version control (also called source control or revision control) is fundamental to modern software development, enabling teams to work together without overwriting each other's changes.
Why it matters
- Enables parallel development through branching and merging.
- Provides complete history of who changed what, when, and why.
- Allows safe experimentation—you can always revert to a working state.
- Essential for code review, CI/CD pipelines, and audit trails.
- Required for compliance in regulated industries (SOX, FDA 21 CFR Part 11).
Types of version control
- Centralized (CVCS): Single server holds the repository (SVN, Perforce).
- Distributed (DVCS): Every developer has full repository copy (Git, Mercurial).
Git fundamentals
- Repository: The database containing all versions and history.
- Commit: A snapshot of changes with a unique identifier (SHA hash).
- Branch: An independent line of development.
- Merge: Combining changes from different branches.
- Pull request: Proposed changes for review before merging.
- Tag: A named reference to a specific commit (usually for releases).
Best practices
- Write clear, descriptive commit messages explaining why changes were made.
- Commit often with small, focused changes.
- Use branches for features, fixes, and experiments.
- Review code before merging to main branch.
- Never commit secrets, credentials, or sensitive data.
- Use .gitignore to exclude build artifacts and dependencies.
Related Articles
View all articlesLocal LLM Benchmarks: 12 Findings From Consumer Hardware
NVIDIA publishes its inference wins on 8× DGX B300s. Almost nobody has those. So we ran the same ideas on a single consumer RTX 5060 Ti, a 2017 GTX 1080 Ti, and a CPU — and measured what actually happens. Here are all 12 experiments.
Read article →Ollama vs llama.cpp vs LM Studio: The Speed Tax, Measured
LM Studio, Ollama, and raw llama.cpp all run the same engine on the same GPU. We measured what the convenience layer costs: LM Studio adds 0.3%, Ollama adds 10%.
Read article →How Low Can You Quantize a GGUF Model Before Quality Breaks?
We swept Qwen2.5-Coder-7B from Q2 to Q8 on an RTX 5060 Ti. Output fidelity goes 21% at Q2, 57% at Q4, 80% at Q6 — the cliff is below Q4, and the sweet spot is Q4–Q5.
Read article →KV-Cache Quantization: The q4_0 Cliff Your Logs Won't Warn You About
We benchmarked f16 vs q8_0 vs q4_0 KV caches on the same model. q8_0 KV is nearly lossless (81.6% similar). q4_0 KV wrecks output quality (8.3%) while saving VRAM — and your throughput dashboard stays green the whole time.
Read article →Explore More Development
View all termsAPI (Application Programming Interface)
A set of rules and protocols that allows different software applications to communicate and exchange data.
Read more →Cron Expression
A time-based job scheduling syntax using five or six fields to specify when tasks should run.
Read more →DevOps
A set of practices combining software development (Dev) and IT operations (Ops) to shorten development cycles and deliver high-quality software continuously.
Read more →Diff Algorithm
A computational method for comparing two sets of data and identifying differences between them.
Read more →GitOps
An operational framework that uses Git repositories as the single source of truth for declarative infrastructure and application configurations.
Read more →JSON (JavaScript Object Notation)
A lightweight data interchange format using human-readable text to represent structured data.
Read more →