Code Habits
-

•
Crash Early Rather Than Corrupt Quietly
I still remember the silence of a Tuesday morning three years ago at the insurance firm. There were no alerts, no PagerDuty calls, and no…
-

•
Read Both Sides Before You Pick One
I once spent a Tuesday evening staring at a terminal screen, watching a deployment fail because I thought I knew better than the git markers.…
-

•
Rebase With a Backup Branch
I still remember the exact feeling of my stomach dropping in a dimly lit office back at the logistics startup—that cold, hollow sensation when you…
-

•
A Branch Older Than a Week Is a Problem
I’ve sat through enough “agile transformation” workshops to know that most people treat git workflows like a religious ritual rather than a tool. They’ll spend…
-

•
Changing the Table While People Use It
I still remember the specific, hollow sound of a Slack notification at 2:14 AM during my time at that logistics startup. It wasn’t a loud…
-

•
Write the Down Migration First
I still remember the specific, hollow feeling of staring at a terminal at 3:14 AM, watching a deployment hang while the production database CPU spiked…
-

•
Give Every Flag an Expiry Date
I remember sitting in a dark apartment three years ago, staring at a trace of a production outage that felt like a ghost in the…
-

•
Your Logs Are a Database of Passwords
I still remember the cold sweat I felt back at the logistics startup, staring at a terminal screen at 3:15 AM because our centralized logging…
-

•
Stop Fixing the Symptoms and Start Knowing Your Own Defaults Before You Try to Change Them.
I remember sitting in a darkened home office at 3:14 AM, staring at a dashboard of red metrics while a service I thought was “robust”…
-

•
Log What You Would Want at Three in the Morning
I spent three hours last Tuesday digging through a mountain of “INFO” level noise just to find the one trace that explained why a specific…