Skip to main content -
Restoring From R2 Required R2 Credentials Stored Inside R2
-
Expired Domains Vanished From Every Account Page Until June 23
-
Null oldGameID Columns Pointed Straight at the Duplicate Game Inserts
-
Wrong Group on Login Twice in One Week and the Repairs Pointed Opposite Ways
-
The Console UPDATE Is the Most Dangerous Line in Production
-
The Query Window Said 1 Row Affected and Nothing Else Did
-
When a Payment Confirmation Event Overwrote Decisions Made by Hand
-
Three Bugs Merged the Same Day Into develop From Two Hotfix Branches
-
Three Fixes on April 21 and Each One Was Called Done Too Early
-
Restoring 327 Units From One Backup Without Writing a Row
-
A restored organization of 327 units and the script we almost left armed
-
1,477 Lines of Recovery Code Replaced Three Scripts That Disagreed
-
A code-first schema audit: keeping a 1,477-line recovery file in sync with a 14,536-column DB
-
We Wrote a 1,477-Line Site-Recovery Engine: Copy First, Remap IDs Second
-
A 418-line tool now reads our recovery file as plain text
-
3.5 Million Database Messages Against a Thirty Minute Recovery Window
-
1900-01-01 Is Not a Date: The Zero-Datetime That Corrupts Every Migration
-
A 683-Line Plan File Written Before Touching the Live System
-
From 3.5 million round-trips to hundreds: batching a remap with temp tables
-
The Recovery Script That Stayed Armed After 327 Units Came Back