Real Loss or Stale Read? The Night the Records Vanished, and the Dashboard That Lied Both Ways
The system said the records were gone. They really were gone. But the same system routinely reports counts that are wrong by a factor of eight — so how do you know which kind of "gone" you are looking at, before you act on it?
Reconcile Before You Recreate: Making a Bulk Job Safe to Run Twice
Every bulk job gets re-run — after a crash, a false failure, or a nervous operator. Whether that re-run heals the data or doubles it comes down to one question you answer before it starts.
A “Success” Toast Is Not Confirmation: When the UI Lies Both Ways
The message said the record was created. It was not. A different message said the save had failed. That one was already in the database. The interface was wrong in both directions on the same afternoon.
Killing the Process Didn’t Stop the Job: A Runaway Batch and the Orphan That Ran It
I killed the worker, watched it die, and moved on. Twenty-five minutes later a batch I thought I had stopped had quietly finished on its own.
Regex Inline Flags Killed the Field: A Pattern That Compiles Everywhere Else
The question was not broken, not hidden, and not misconfigured. It was disabled — by a two-character prefix that every other language I use accepts without complaint.