Skip to main content -
Two Customers Blamed for a Setup Error That Was an Expired Certificate
-
The Signup Spike Wasn't the Fix, It Was the Season
-
Four Identical Cards Were Not a Duplication Bug
-
The Silence in the Log Was the Bug
-
My Sessions Kept Dying and I Blamed the Wrong Thing
-
The 200-Line Lie: Why My Agent Kept Forgetting My Goals
-
Before you repair data, build the diagnostic
-
The CAPTCHA lockout you trigger yourself: when a wrong API endpoint hammers you to a 403
-
The Whole Feature Was Built and Verified in Sandbox, Then Prod Said E00044: CIM Not Enabled
-
My pinned app kept vanishing after every reboot, and it wasn't Windows being flaky
-
It Looked Exactly Like a Bot Swarm. It Was SQL Server Parameter Sniffing.
-
The stale credential that failed two different code paths at once
-
The Ambient-Global Bug: When "Current Account" Is a Mutable Global Your Whole App Reads
-
rtk Wasn't Broken, It Was Unreachable: How I Found 366 Silent Failures in My AI Agent Sessions
-
The \"queue worker drains it\" story was vapor: the create command said NOT YET IMPLEMENTED
-
The runbook said the domain was in account A. It was in account B. Verify ownership before touching live DNS.
-
The customer's own scraper IS the bot swarm you've been fighting
-
The console window that flashed every 30 minutes: Interactive vs S4U scheduled tasks
-
The Self-Updating Deploy Script That Has to Fail Once to Fix Itself
-
tRPC 401 vs REST: when a reviewer's suggestion is right in substance, wrong in transport
-
The False 200: When Removing a Binding Reveals Your Verification Was Lying
-
The Cloudflare-for-SaaS + IIS Gotcha Nobody Documents: SNI vs Host Header
-
The Prod Box Was DDoSing Itself: An iCal Calendar Feature Looping Through the Public Edge
-
The legacy server-variable bug that printed `undefined` instead of a value
-
A dry run is only useful when it checks the same things as apply
-
Operator, not IP: fingerprinting a 40,000-IP proxy swarm by its RIPE maintainer
-
The bot swarm that turned out to be one bad query plan
-
My agents quietly hoarded 48 GB of Chrome profiles until the machine froze
-
314 broken stats pages and one bad cursor
-
It wasn't one tournament bug
-
You can't repoint a junction under live file handles (why I had to stage the .claude move)
-
Clearing %TEMP% on a machine running parallel Claude sessions is friendly fire
-
Edit a label, get " back: the HTML-entity round-trip bug
-
Cloudflare Tunnel as a Windows scheduled task (and the visible-console bug I shipped)
-
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
-
The Index Seek That Was Actually a Half-Table Scan (5000x, on a 4M-Row geoIP Table)
-
7 games became 14: making a bulk insert idempotent with an origin key
-
Measure the Bottleneck Before Blaming the Visible Workload
-
My Agent's Chrome Was Running but Invisible: A Windows Session 0 Isolation Ghost Story
-
One Private Dependency, Five Different Failures
-
The Button Clicked and Nothing Happened: IIS Ate My JSON Error and Handed Back HTML
-
An Index Seek Can Still Read Far More Than You Expect
-
\"My internet feels unstable\" was a half-disabled IPv6 stack, not the ISP
-
One-Flag Fix: --isolated Stops Parallel Playwright Clones From Deadlocking
-
claude --resume worked in my terminal and failed in my web app: the LocalSystem homedir trap
-
The IPv6 fix bit back: how localhost resolving to ::1 quietly broke a three-hop proxy chain
-
Avoid Unnecessary Date String Round Trips
-
RTK Ate My JSON and Hid My Merge Commit: When a Token-Saving Filter Lies to Your Agent
-
Same Root Cause Is Not Same Fix: Verify the Data Shape, Not Just the Symptom
-
Your JIRA Session Won't Cross Into an Iframe. Here's the Reused-Popup Workaround.
-
Before You Merge a Long-Idle Branch, Audit Its Temporary Scaffolding
-
The workflow broke in the glue code, not the AI
-
"Bamboo is broken" was wrong: a deploy that races the filesystem under CPU pressure
-
UTC logs, a local clock, and the canary request: timezone discipline in an incident
-
The fix that ran on every request
-
A 25-Second Admin Screen Meant We Trusted the Wrong Query
-
The bug wasn't the upload, it was the URL contract
-
The bug wasn't the upload, it was the URL contract
-
The Bug Was Not in the Mobile UI
-
The Fastest Legacy Hotfix Is Often a Diagnostic
-
The call was coming from inside the house
-
Classic ASP Doesn't Care That It's a Comment: The Script-Delimiter Collision
-
Why schedules broke around March 4, 1973: a getTime() digit-count sort bug
-
The Banner Wasn't a Safari Bug, It Was an Empty Frame
-
The Page Was Performing a Ceremony, Not a Job
-
The CSS Bug That Was Actually a Delete Bug
-
The feature was fine. First-time state was the real bug.
-
The ambient-global bug: when \"current account\" is a mutable global 100 call sites read
-
The ambient-global bug: when current account is a mutable global your whole app reads
-
Hand-rolled hydration: passing server state to the browser with no framework
-
A New Feature Is the Best Fuzz-Tester for Your Existing Data Model
-
Carry Your State in the URL, Then Actually Carry It: The Dropped Query Param
-
A Client Tree-Walk That Was Really a Server Business Rule
-
The Duplicated-Derivation Bug: One Fragile Expression in Four Queries
-
Moving Claude Code Off Your C: Drive: The 12.4 GB VM Bundle and the UWP Permission Wall
-
Same SHAs in Two Repos: Why Commit-Count Metrics Lie in a Clone Workflow
-
PayPal Pay-Later Messages Won't Re-Render, So Destroy the Node and Recreate It
-
A Tiptap Editor That's Invisible Until You Add ProseMirror's Base CSS
-
Tiptap v3 Fires onFocus During Init, So Subscribe to the DOM Instead
-
clipboard.js Named Its Global 'Clipboard'. So Did the Browser. Boom.
-
Response.Redirect Blew Up the Error Page. Server.Transfer Didn't.
-
Stripe Needs a Post-Back, Authorize.Net Doesn't: One Page, Two Flow Shapes
-
Shipping a Throwaway Relay Page to Debug a Payment Integration in Prod
-
x_trans_id Is Not Your Invoice Number: An Authorize.Net Direct-Post Bug
-
1900-01-01 Is Not a Date: The Zero-Datetime That Corrupts Every Migration
-
N Drifting Copies Share One Bug: The Legacy Consolidation Thesis