This week's two pieces — one on writing better Git commit messages with AI, and one comparing Claude and ChatGPT for code review — were both born from the same messy sprint where I made a mistake that cost real time.
Here's what happened.
Midway through a feature branch, I switched from the AI tool I'd been using for code review to a different one, mostly out of curiosity. I wanted to test a head-to-head comparison in a live context rather than a synthetic one. The model switch was seamless. The workflow wasn't.
The new tool had a different "grain" — it flagged different things, used different idioms in its suggestions, and didn't carry any of the soft context I'd built up through earlier prompts in the session. I had to re-explain patterns we'd already established. I re-reviewed two files I'd already cleared. Net result: roughly a day's worth of focused review time became a day and a half, and I caught one genuine regression — a missing null check on an edge case — that I'm not confident the original tool would have caught.
So the lesson wasn't "tool X is better than tool Y." It was that consistency in tooling during a sprint has its own compounding value, and switching mid-flow carries a real context-switching cost that doesn't show up in any benchmark.
