Version control is a time machine, not a filing cabinet
Commits that tell a story, branches that hold experiments, and the confidence to delete things. Git rewards the curious.
By Nzubechukwu Cyprian · Pharmacy student at UNN, full-stack developer
For my first year with git, I used about 4% of it: add, commit, push, pray. It was a filing cabinet with anxiety. The shift to treating it as a time machine changed how I build.
The mindset shifts
Commits are save points in a game, not deliveries. Small, frequent, honest. "wip" commits are fine on a branch — they're breadcrumbs back to working states.
Branches are parallel universes. Want to try the risky refactor? Branch, break everything freely, and git checkout home. When breaking things costs nothing, you experiment more, and experimenting more is how you find the good design.
History is documentation. git log and git blame answered more "why is it like this" questions for me than any architecture doc ever written — but only because I learned to write commit messages that explain the why.
The practices worth stealing
- commit before you refactor, so there's always a door back
- write the message for the person debugging this in a year — usually you
git revertovergit fix-forward-and-praywhen something's wrong in production- stashes are not storage; they're pockets
Deleting things fearlessly is the real payoff. When you trust the time machine, you stop hoarding code out of fear.
One email when a post lands
No schedule, no spam. Just the posts worth reading — new writing on software, AI, products, and the Pharmacy × Tech life.
Prefer a feed reader? Grab the RSS feed.
Keep reading
Software engineeringNaming things is the whole job, sometimes
Most codebases don't have a naming problem — they have a thinking problem that shows up in their identifiers.
Software engineeringYour README is your first interview
Before anyone judges your code, they judge your README. What a good one actually contains, from someone who reads a lot of them.
Software engineeringThe bug that taught me to read error messages properly
A three-line error sat in my logs for a week. It told me exactly what was wrong. I just never read past the first line.