Why don't people use git properly?
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Many developers use git poorly or not at all, and this essay explores why. The core issues are: git is primarily a CLI tool and many developers lack command-line fluency; most people never experience situations where version control's value becomes viscerally obvious (rolling back a broken production deploy, for example); and without that felt need, learning the tool feels risky rather than safe. The author uses an analogy of armoured vs. unarmoured soldiers — git gives developers the confidence to take risks and experiment, but only once they've internalized that safety net. Solutions proposed include introducing git from the very first coding lesson, requiring repository submissions for assessments, rotating new hires through DevOps, and encouraging small independent tool projects that create real deployment and rollback scenarios.
