Code Habits
-

•
Reading Code for Things That Happen at Once
I once spent three days chasing a ghost in a logistics system that only appeared when the server load hit a very specific, unlucky peak.…
-

•
The Reviewer Is Right and You Are Annoyed
I remember sitting in a dimly lit office at 3:15 AM, staring at a screen while the cooling fans of a server rack hummed a…
-

•
When the Reviewer Did Not Read the Context
I was staring at a pull request at 11:45 PM, nursing a lukewarm coffee, when I saw it: a comment that had absolutely nothing to…
-

•
How to Say No in a Comment Thread
I spent three hours last Tuesday arguing with a senior dev about whether we should use a ternary operator or a full if-else block. We…
-

•
Review the Code, Not the Person
I once spent an entire afternoon arguing with a junior dev about whether to use a ternary operator or an if-else block, feeling incredibly superior…
-

•
Pinned Is Not the Same as Abandoned
I remember sitting in a dimly lit office during my time at that logistics startup, staring at a build pipeline that had been dead for…
-

•
Upgrade One Thing at a Time
I remember sitting in my kitchen at 3:15 AM, staring at a terminal window while the blue light of my laptop felt like it was…
-

•
Every Dependency Is Code You Did Not Review
I remember sitting in my kitchen at 3:14 AM, staring at a terminal window while my coffee went cold, trying to figure out why a…
-

•
A Changelog for Humans, Not Commits
I once spent a full Tuesday afternoon at a logistics startup trying to figure out why our shipping service was intermittently dropping payloads, only to…
-

•
Write Down Why, Not Just What
I once spent three days rebuilding a distributed locking mechanism from scratch, only to realize halfway through that I had already solved it perfectly for…