Skip to main content -
Blind judges preferred the rewrite, so we rewrote 751 posts
-
506 open tickets, 429 candidates, and a verifier that would not agree
-
Three Copies of the Firewall Page and Version 18, 27, 31
-
When Yesterday's Design Decision Kills Today's Work
-
Our scoreboard dropped to 44% while the bookkeeping loop went uncounted
-
229 Prompts Before We Built the Session Host
-
Two Posts About 956 Certificates Sat in the Pipeline Together
-
451 Tokens Spent to Learn a Model Call Was Told to Wait
-
Two 900-second agent runs and a git stash pop conflict that never resolved
-
We Wrote Platform-First Goals, Then Drifted
-
125 passing tests and a seat gate nobody had checked at runtime
-
The Window Grid Said Slot 4 Was Empty and Buried a PowerShell Terminal
-
A Cloudflare 530 at 10:59 PM and a tunnel that never restarted
-
30 Clones, 20 Stale Branches, and Commits That Lived on One Disk
-
The Config File That Changed Our 4 AM Cron Without Telling Anyone
-
The 6-by-3 Isolation Matrix Became a Release Grid for Three Repos
-
Why the 201 closes from one sweep went into a log
-
A 1,900-Character Review Where Only One Line Mattered
-
Marking Up a GPT Plan at 10:47 PM Until Dawn
-
Rules Only Stick If They're Lived: The Retroactive Cleanup We Never Started
-
Our First Claude Account's 20x Pool Ran Out Wednesday. We Spun Up a Second Account Mid-Week.
-
Ranking 75 Tickets on Story Points and customfield_10104
-
The 38 Minute Bug Hiding Behind an active_watchers Loop
-
The 26 Minute Test Suite Number That Was Really 497 Seconds
-
Turning One Night of Ticket Sorting Into /queue groom
-
A desk that measured 162 context switches an hour
-
Three labels for 113 technical posts, and what each one decides
-
When Your Agents Need a Coordinator
-
Why Our Release Check Passed Minutes Before the Meeting
-
Our Guard on the Create Command Missed Nine Business Findings
-
190 Units Became 17 Tasks and 6 Epics From Chat History
-
What 270 proposed tasks looked like when we read our chat back
-
What nudge_top1_count Tells You That a Status Field Can't
-
Why Rewriting a Draft Twice Left Us With the Same Forty-Five Lines
-
Two readers, one status field, and a decoding tax
-
Sessions Scoring Under 0.6 Pile Up Forever Without One Rule
-
Why Our Flagged Items Queue Grew Every Single Week
-
What a 12-Turn Throttle Taught Us About Agent Ownership
-
The 5 Minute Silence Our Agent Kept in a Shared Channel
-
The create call that succeeded and left 190 tickets unattributed
-
Nine Minutes to Close a JIRA Ticket That Had No Branch
-
We Stopped Guessing Categories and Read Them Off Our Own Product
-
The Nightly Job That Filed TLS Cert Renewal as Internal Work
-
The Hub Doorway: One Chat to Orchestrate Parallel Sessions
-
Why the 17h 29m Session Made Our Daily Review Card Wrong
-
The Bare Domain Returned a 404 Through the Mail Host
-
The Wrong Address Variant Nobody Had Typed Until Launch Week
-
Why one word of error from a metered assistant meant nothing
-
Why Our Ten Parallel Clones Stopped Accepting New Tickets on July 18
-
Session 005 Turned a Late-Night Judgment Call Into a Slash Command
-
Revision 13 to revision 40 in one evening of group chat
-
A Forced-Command SSH Key Called rc_spawn.sh From a Phone
-
A Worker Stalled for 22 Hours and Nothing Complained
-
Voice, Tone, and Style Stopped Blocking Publishing on June 30
-
12 Unanswered Questions and a Review Tool Nobody Opened
-
Why the Domain Instructions Email Button Felt Slow
-
Why our automated jobs kept opening browsers on top of each other
-
The money logic review that happened in the wrong place
-
What We Learned Clearing 65 Expired Domains From the Backlog
-
172 Messages, 180 Messages, and a Stranger at 8:38
-
A Two-Prompt Session With 91,958 Cached Tokens Showed Up Unannounced
-
Breaking Every Chat Into Trackable Units
-
87 hours, 119 drafts, and one feed that only misbehaved for machines
-
When Unset Quietly Meant Unrestricted on Every Restart
-
Codex Cited a Line in a 1218 Line File and Missed
-
When a Priority Marker Pretended to Be a Status Field
-
Why Our Queue Looked Busy While Most Active Items Were Already Done
-
We Almost Rebuilt Phase 0 Scaffolding That Was Already on Disk
-
One mixed QA ticket can slow down every independent fix
-
The dormant-project tripwire: make the unknown visible
-
Let AI suggest before you save
-
When the dry_run branch sits above the is_ready check
-
Why a stored-procedure reorder collided with thirteen unrelated changes
-
When a Green Dashboard and a Finished Handoff Disagree
-
Why the Activity Log Was the Wrong First Screen
-
One Line in the Rules Ended a Thousand Small Checkpoints
-
Read-Only Views Before Write Access Gets Approved
-
12 Manus Tasks in One Night via File Exchange
-
Why our Haiku credits produced 6,134 files that no screen displayed
-
Filing Systems That Make Everyday Saves Harder
-
Every action endpoint returns HTTP 200 and carries its failure in the body
-
A Seven-Hour Session With 390 Prompts and No Record
-
The Review Record Missing From a Chronological Activity Log
-
The filing spot that did not exist at the other office
-
Where a Git Repository Stops Being Enough for Publishing
-
Why Our Beats Table Never Shipped Without Distributions and Outcomes
-
Stop Making People Rebuild Context Before They Decide
-
What a Handoff Note Needs Before Someone Signs Off
-
git branch -d Refused a Merged Branch and Git Was Right
-
What /add-dir did in the CLI but not in Cursor's Claude Code panel
-
Why Our Deferred and Waiting Items Shared a Single Status
-
Why a Polished AI Note Looked Approved Before Anyone Approved It
-
What a Backlog Triage Session Spent Before Judging Anything
-
What a deferred decision needs besides a threshold
-
The Query Window Said 1 Row Affected and Nothing Else Did
-
Three Layers Keep a Triage Sweep Out of the Approved Queue
-
How to Triage an 880-Ticket Backlog Without Deleting Real Work
-
Five Controls Around One Exceptional Database Change
-
Why a backlog cleanup turned a triage prototype into a field schema
-
Three Objections From a Strong Coder Who Won't Use Claude Code
-
Why One Colleague Keeps Refilling the Same Handoff Detail
-
When a Familiar Screen Makes a Simple Job Harder
-
The Agent Kept Asking Us to Launch Chrome on April 6
-
What Three Stopped Batches Taught Us About Who Owns Chrome
-
187 Commits Across Eleven Repos From Four Routine Customer Tickets
-
A 165 Added, 145 Removed Diff That Barely Changed the Line Count
-
What Four Commits and a Collapsible Details Section Did to Our Task List
-
165 Lines Added, 145 Removed, and the Page Barely Changed