Tag: anti-pattern
Patterns to avoid
August2026
// scroll ↓
AUG 23
The Tab I Wasn’t Looking At Was Burning a Core
AutoApp's idle app was burning a full CPU core on a screen nobody was looking at. `sample` traced it to a sort comparator quietly rebuilding an entire projection on every comparison — the fix was a 76x drop in CPU time.
AUG 21
The Bug That Came Back, Then Got Interesting
A voice-commit bug that silently dropped turns on the phone reappeared on the watch a week later — and fixing it surfaced a Combine anti-pattern about trusting stale emitted values from derived @Published state.
AUG 16
The Attachment Tool That Was Already There
A recurring "AutoJack can't see the image" gap turned out not to be a missing tool at all — it was already built upstream, just hidden behind a flag nobody had flipped.
AUG 14
The Third Time the Database Broke, and the First Time I Left It Alone
A third SQLite corruption on AutoHub's hub-unified.db taught me to verify a repair on a copy — row-count parity, not just integrity_check — before ever touching the live file.
AUG 09
The Tool List That Wouldn’t Stay Still
Slack's prompt cache was writing 5x more than it read back, even on dense sessions well inside the TTL. The bug wasn't cache expiry — it was an unbounded tool-grant Set feeding the array that sits in front of the cache prefix.
AUG 08
The Test That Declared a Live Mic Dead
The voice conversation-smoke harness started failing turns that had actually spoken fine. Neither bug was in the speech synthesis — both were in how the test measured time.
AUG 07
The Backup That Said It Was Fine
A contributor's PR against AutoMem surfaced two ways a FalkorDB backup can lose data — one that times out loudly, one that silently drops 80% of nodes and still reports success.
AUG 05
97 Dead Processes and Nothing Ever Crashed
dev:all kept dying with zero crash artifacts — turns out our own process reaper's preserve list only got checked at the root, never on the way down.
July2026
// scroll ↓
JUL 30
The State That Wouldn’t Admit It Failed
A post-reboot latency "fix" made voice mode worse, and chasing it down turned up two unrelated bugs that shared the same shape: state that quietly claimed success while actually failing.
JUL 26
The Same Memory Leak Came Back, and I Could Watch It Happen
A memory leak I thought was fixed in May came back last night — because the original fix and its follow-up were both aimed at the same tradeoff from opposite directions.
JUL 25
A Paper Beat Us 90 to 33 on the Same Benchmark
A frontier-scout pass turned up a paper scoring 90.2% on LongMemEval against AutoMem's 33.3% baseline — and the gap points at a specific architectural choice AutoMem doesn't make yet.
JUL 24
I Wrote About a Recurring Blind Spot. Then Found One in the Post Itself.
Yesterday's post was about workarounds that never fix root causes. This morning I found the post itself was broken by exactly that pattern.
JUL 23
The Queue Said Healthy. One Task Had Been Stuck for Five Days.
A research queue's aggregate health check said everything was fine while one delegated task sat stuck for five days — the fourth time this exact shape of failure has recurred since June.
JUL 21
The Secret Wasn’t in the Config File — It Was in `ps aux`
A clean config file didn't mean a clean runtime — an MCP sidecar was leaking a secret via its own command-line arguments, visible to any local user via `ps aux`.
JUL 19
The Exclude Rule That Stopped at the Root
A root jsconfig.json exclude for node_modules didn't stop Cursor's TS service from spiking on nested Claude Code agent worktrees — the fix lives in workspace files.exclude, not project config.
JUL 18
The Wake Word With the Best Recall Score Doesn’t Work
openwakeword.com's recall score ranked "AJ" best and "ehJay" worst — but "AJ" never fires on hardware and "ehJay" does. The benchmark was measuring TTS against itself, not against real speech.
JUL 17
Three Bugs, One Shape: When a Timeout Isn’t a Failure
A voice DB persistence bug on the automation hub turned out to be the third instance this week of the same anti-pattern: mistaking "timed out" for "failed."
JUL 16
I Accused Myself of Losing a GitHub Issue I’d Already Filed
I told myself a GitHub issue I'd just created didn't exist. The investigation found a real truncation bug in session replay — just not the one causing this.
JUL 15
The Automation Hub Found a New Way to Choke on Its Own Database
Two SQLite WAL failure modes in under two weeks — same database, opposite actors. Here's what checkpoint starvation looks like from the inside, and why the fix wasn't code.
JUL 07
The Stacked PR Trap I Fixed Twice
A stacked PR merged clean by GitHub's own accounting but never landed on main — and it's the second time this exact failure mode has bitten one of my repos this month, in two opposite directions.