Latest News

Your agent's memory stopped writing and nobody told you

The worst persistence failure is not the error: it is the write that never happens and returns success. The agent keeps believing it has memory, and…

Deduplicated Fallback Query Uses Wrong Relevance Threshold

Deduplicated fallback search queries can accidentally trigger the wrong relevance threshold and reject valid results when the requested query matche…

A guard that never fires is the same as a guard that does not work

Every guard has two states: working and green by accident. Both print “OK”. The difference only shows when you force the condition it was supposed t…

48-Hour Field Notes: Exit Code 137 at Hour 31 Was Not a Bug in My Code

I run long jobs on purpose, because short jobs lie to me in pleasant ways. A loop that finishes in ninety seconds never teaches you what happens whe…

The Uniface test that "hung" had died - finding a silent crash with SQLite

This is a side story from the series Building a customer app in Uniface 10 . It stands on its own: you only need to know that the app is a Uniface 1…

Go Typing Indicator Debugging: 5 Checks for Missing Stop Event Expiry

Short answer: Treat every typing-start signal as a renewable client-side lease, expire it locally, and use the stop event only to hide the indicator…

Kill the bug class, not just the bug

The dry run said the reminder text would go out to a customer with the window "12PM–2PM." The actual appointment was 8AM–10AM. Four hours off, on a…

The optimization that doesn't survive the process boundary

The optimization that doesn't survive the process boundary I found a slow lookup in our inbound-message handler — every incoming SMS triggered an O(…

The Agent Passed the Test It Rewrote

An agent that can edit tests can make any bug disappear. That is the whole article in one line. Agent-written patches are everywhere right now. The…

Debugging nighttime PoE camera restarts: power, cable and recording checks

A PoE camera can work during the day and restart when its lighting activates. Power is one possible cause; a frozen live view alone does not prove a…

We published that Google never recorded our only sale. Google had recorded it — we read the window too early.

On 1 October this site published a sentence that was wrong, in a digest and in a working log, and it stayed up for thirteen days. This is the correc…

Don't make the failure path stricter than the success path

Two incidents in one week, same anti-pattern. In both cases, the system didn't fail because of the failure — it failed because of how we handled the…

The sync that deleted our leads every 60 seconds

The sync that deleted our leads every 60 seconds Leads were vanishing. Not bouncing, not erroring — just gone. New leads would appear in our registr…

Profiling a Slow Application: Stop Guessing, Start Measuring

Your application is slow. Users are complaining. API requests are taking too long, and pages are struggling to load. Your first instinct might be to…

[Boost]

A Go Build Failed. I Wanted to Replay It Without the Original Project. Alimkhan Slambek Alimkhan Slambek Alimkhan Slambek Follow Oct 13 A Go Build F…

I moved my webhook work into waitUntil() to fix a timeout. The failures didn't go away, they just stopped being visible.

My GitHub App takes a pull request, asks an LLM to review it, and posts the comments back. The first time I ran it end to end against a real reposit…

Audio works, video is black: debugging a layered WebRTC SFU in Go

Audio connects instantly, the viewer hears everything, and the video tile stays black. The publisher side looks fine. ReplaceTrack returns nil , whi…

The Log You Need Is the One the Platform Decided Not to Keep

The support ticket had been open for nine days when the operations manager finally said the sentence out loud: "It works every time I try it. It onl…

Your Agent Added a Retry Loop. It Hid the Bug Instead of Fixing It.

You hand the agent a failing test: an upload that flakes about one run in ten. It comes back green. You open the diff and find a for (let i = 0; i &…

Watermark Removal Artifacts: The "Processed Look" Came From Our Own Blend, Not the AI Model

This is part 8 of the ClearPix engineering series, and it is the story of a bug that lived in the last 40 lines of the pipeline: the step that paste…

My NestJS app "hung" on startup and printed nothing - it was dead all along

Few months ago I started one of my Nest services in watch mode and got... nothing. No error, no "Nest application successfully started", no stack. T…

Your Scraper's "Success" Metric Is Lying When the Site Sends You an Empty 200

Most collection pipelines count a fetch as a success when the HTTP status starts with 2. That works right up until the day a site hands you a polite…

How I Tracked Down a Race Condition in Async Python With Claude Code

TL;DR A background worker in one of my Python services was sending duplicate webhooks about once every 3,000 jobs. It never happened locally, never…

The UTF-8 / Code Page Surprise That Corrupted My Log Parser

The UTF-8 / Code Page Surprise That Corrupted My Log Parser The parser wasn’t wrong. The bytes were fine. My shell lied about what “text” meant—and…

What’s your routine for getting unstuck when you've stared at the same bug for 3+ hours?

Conflicting Android beta reports: separating observations from verified bugs

Two reports from a small Android beta described different behaviour for the same breathing timer: one tester said it restarted after switching apps,…

Mars Pathfinder Priority Inversion Bug: What Really Happened

6 debugging checks for JSON, JWT, SQL, regex, timestamps and URLs

An API failure is often easier to investigate when you separate six questions: what did the response contain, what does the token prove, which date…

How I Hunted Down a Node.js Memory Leak With Claude Code: 5 Lessons

TL;DR One of our Node.js 22 API services was slowly eating memory until Kubernetes OOM-killed it roughly every 30 hours. I paired with Claude Code (…

The Flush Printed a View After the Owner Died

A green debug run does not prove a view owns its bytes. Release can reuse that stack slot before the flush reads it. I start every split-brain crash…