Skip to main content -
The Pre-Release Scan Was Checking Only One Direction
-
The Second Hotfix Was the Honest One
-
My pinned app kept vanishing after every reboot, and it wasn't Windows being flaky
-
The Self-Updating Deploy Script That Has to Fail Once to Fix Itself
-
One mixed QA ticket can slow down every independent fix
-
My red CI was a lie: a deleted workflow haunted every push while nothing real ran
-
The release said LIVE. The code was not.
-
One Private Dependency, Five Different Failures
-
I split my personal cockpit out of the product and everything got cleaner
-
The Hotfix That Lied: STAGING/LIVE in JIRA, Never Merged to Master
-
Closing a Ticket From a Machine That Never Cloned the Repo
-
Before You Merge a Long-Idle Branch, Audit Its Temporary Scaffolding
-
A var EDIT_DATABASE = false Sat in a Branch for 2.5 Years. Then We Shipped It.
-
"Bamboo is broken" was wrong: a deploy that races the filesystem under CPU pressure
-
Hotfix branches need different rules than develop
-
The bug was wearing a trench coat
-
My hotfix skill learned that tags are a lie
-
Don't Trust the Green Deploy: Grep the Live File for Your Ticket Marker
-
A `?prototype=1` Flag and 23 Commits: Prototyping a Redesign in Production Code
-
Your AI Skill File Is Part of Production Now
-
187 Commits to Fix Four Bugs
-
The Real Release Started After the Tag
-
Env drift was the real bug
-
Six Production Releases in One Day: Anatomy of a Hotfix Train
-
Route a Change by Its Blast Radius, Not Its Size or Your Schedule