Skip to main content -
The Approval Gate That Blocked Me for Fifteen Hours and Never Caught a Mistake
-
The Error Count Went Up. Nothing Actually Broke.
-
Four Identical Cards Were Not a Duplication Bug
-
The 200-Line Lie: Why My Agent Kept Forgetting My Goals
-
The Zombie That Blocked Everything
-
rtk Wasn't Broken, It Was Unreachable: How I Found 366 Silent Failures in My AI Agent Sessions
-
Cloudflare Pro is a box of levers, not a managed service
-
Exit code zero meant nothing. My history pipeline had been quietly failing for four days.
-
Five firewall rules beat the proxy swarm, but the real bug was my blind spot
-
The dormant-project tripwire: make the unknown visible
-
Adding OpenTelemetry to a Classic ASP App Without Rewriting It
-
My red CI was a lie: a deleted workflow haunted every push while nothing real ran
-
Three compounding bugs spawned a burst of near-identical tickets, and `tail -15` hid the evidence
-
Your IIS Logs Start Lying the Moment Cloudflare Goes Live
-
\"My internet feels unstable\" was a half-disabled IPv6 stack, not the ISP
-
Parallel Work Needs More Than a Clock
-
My agents needed a filing system before they needed more intelligence
-
35 sessions and no map
-
Bot Swarm Detection: The Three-Signal Triangle That Catches What IP Reputation Misses
-
The method outlasts the patch
-
My backups had been dead for three weeks. I found out by accident.
-
UTC logs, a local clock, and the canary request: timezone discipline in an incident
-
A Migration Became the Audit I Had Never Run
-
After seven hours, I couldn't remember which model I was talking to
-
The attacker was our own redirect logic
-
The SSL bug was easy. The bot traffic made it a day-long incident.