What code review taught me about writing prose
Same skills, different medium: clarity, structure, knowing your reader, and killing your favourite sentence.
By Nzubechukwu Cyprian · Pharmacy student at UNN, full-stack developer
Reviewing code made me a better writer, which surprised me until I saw that they're the same skill wearing different syntax.
The transfers
Structure before polish. A review checks shape first — is this in the right place, does the flow make sense — before nitpicking style. Documents work the same way. Fix the outline; the commas can wait.
Small diffs get better feedback. A thousand-line pull request gets a shrug; a focused one gets a real review. A ten-page document gets skimmed; a two-page memo gets read. Size is a communication decision, not just a work decision.
Explain the why. Good review comments question intent: "why this approach?" Good writing does the same — it anticipates the reader's "why" and answers it before they ask.
Kill the clever line. My cleverest code was always my least maintainable. Same for prose. The sentence I loved was usually the one that served me, not the reader.
The compounding effect
Both skills reward the same habit: rereading as a stranger. I now review my writing with the same checklist I use on code — and the honest, boring truth is that everything gets shorter and clearer.
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.