Benjamin Cronce
Jul 10, 2017 · 1 min read

The only problem more difficult than concurrency, naming.

It is a bit sensational to say that a user’s experience was “wrecked”. Personally, I found git intuitive to use. I like to commit often, then clean up my history before doing a pull request. Of course I keep important commit that infer important decisions made, but most commits are noise of playing around. Just pretend the in-between never happened.

I used SVN for years and never understood branching and merging, but after less than a day with git, I was branching, rebasing, cleaning history, and handling conflicts.

Not only does git give me the power to make the history read like a book, it has taught me to think of how I would like the history to look, to help facilitate whomever may be stuck supporting my code.

SVN never allowed for such a thing. I just committed random blobs of code changes, always afraid my computer could die at any moment. Blame working as IT for a few years. If your data is not stored somewhere off of your computer, it may as well not exist. Commit often.