Code Habits
-

•
Tell Them What to Do, Not What Broke
I once spent three hours on a Tuesday morning debugging a failed payment integration, only to realize the system was throwing a generic “Internal Server…
-

•
A Slow Suite Is a Suite Nobody Runs
I remember sitting in my kitchen at 3:15 AM, staring at a spinning progress bar in Jenkins while my coffee went cold. I had pushed…
-

•
Not Everything Deserves a Test
I remember sitting in a cold server room during a deployment at my old insurance firm, watching a CI pipeline crawl through three thousand green…
-

•
Prove the Bug Exists First
It was 2:14 AM, the kind of hour where the blue light of your monitor starts to feel like a physical weight, and I was…
-

•
Six Hundred Lines and No Tests
I remember sitting in a dimly lit office at that logistics startup—the one that eventually vanished—staring at a single, 1,200-line method that seemed to be…
-

•
Clever Code Is a Debt With Interest
I remember sitting in a dim office at a logistics startup around 3:00 AM, staring at a single line of nested ternary operators that someone…
-

•
Write for the Person Who Edits It Angry
I once spent three days trying to untangle a “clever” abstraction in a logistics codebase, only to realize the guy who wrote it had moved…
-

•
Find the Entry Point, Then Follow the Data
I remember sitting in a dark apartment three years ago, staring at a service that was hemorrhaging memory, trying to figure out how to read…
-

•
Fix One Small Thing on the Way Past
I remember sitting in a darkened apartment three years ago, staring at a terminal window while a production database choked on a query I didn’t…
-

•
The Code Is in Git, Delete It
I once spent three days tracing a memory leak in a legacy logistics service, only to realize the culprit was a “safety net” function written…