#go
9 posts tagged go. · All tags
- A PR That Verified Zero Missing Rows Stopped Analysis for Three Hours With One Comment Line The PR for regenerating 260,000 summaries accounted for locks, rolling deploys and every stray row. One format placeholder inside a comment in the last commit broke the SQL, and all four tests still passed
- One Empty Array Turned Hitting the Limit Into an Ordinary Failure For two hours before dawn, jobs failed across every project. The only message left was one line with the cause slot empty. And fixing it meant a number in a disclosure body could trigger a global pause
- I Tightened Parameters One at a Time, Got Breached Twice, and Stopped Tightening I went in to add a shape check to a sibling route and found that was not the point. The cache key was the whole RequestURI, so every way of spelling the same response became its own entry. I gave up hit rate and set a 64MB total ceiling, and then review found three more holes in the ceiling itself
- I Stopped Judging Runaways Per Job I built a per-call cost cap, raised it, turned it into an alert, and finally removed it. After fixing the same safeguard four times in four days, all that's left is the aggregate gate and a timeout. "Didn't I say just alert me?"
- I Opened Up Effort and Effort Was Empty I added per-job model and effort selection to the shared queue. When I had it do a self-review, the agent measured with 9 scratch sessions and found that the thinking I had turned off five days earlier was neutralizing effort. Why I split the requested value and the actual value into two columns, and how after deploy the docs and production disagreed in five places
- I Turned Thinking Off 85.8% of the summary job's output tokens were thinking. One environment variable turned it off: output −85%, 4.5x faster, schema 10/10, and the summaries actually had more numbers. And why the one line that turns it off could have killed auth for three projects at once
- Three Throttles That Keep a 640K-Row Backfill Behind Live Traffic Filling the 2020–2025 disclosure archive means running for months inside the external API's daily quota and the LLM's throughput. I split collection from analysis, put the archive behind new disclosures, and built a throttle that stops every worker on a rate-limit error. The completion estimate changed four times in five days
- Two Silent Traps in the Dev Environment Four times in one day I reread the code because "the fix isn't taking." The culprit wasn't the code but the .next directory shared by dev and build, and a two-layer cache that kept serving old responses after I fixed the local DB. A trap the user never once saw
- If AI Rewrites It, Can I Just Switch Stacks? Three Switches in 12 Days Over 12 days I moved the backend from Spring Boot to Go and switched mobile stacks three times, to check whether the switching cost is really zero