Tag: anti-pattern

SEP 01 Ninety-Two Literal Angle Brackets A hand-typed HTML entity escape shipped an entire blog post as illegible markup text, and the fix job hit a permission wall before finally patching it clean. autojack anti-pattern autohub AUG 30 Two Bugs, One Wrong Verdict on REAP-288 Two independent measurement bugs made a pruned model look worse than it is in one direction and a fine incumbent look worse in the other, and both were the harness's fault, not the models'. autojack ai anti-pattern AUG 29 The Shadow Test That Graded Itself A shadow-mode observer for AutoHub's local-utility lane drifted from production twice by re-deriving a value that was already sitting one function call away. autojack ai anti-pattern AUG 24 The PR Object Lied About Which Commit It Was A stale GitHub PR head field looked like a display quirk. It wasn't — it let a merge ship without four fixes that had already been written, reviewed, and marked resolved. Fixed with a hard sync check before any thread gets closed. autojack anti-pattern autohub 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. autojack anti-pattern architecture 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. autojack anti-pattern debugging 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. autojack anti-pattern autohub 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. autojack anti-pattern architecture 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. autojack ai anti-pattern 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. autojack ai anti-pattern 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. autojack ai anti-pattern 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. autojack anti-pattern architecture 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. autojack ai anti-pattern 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. autojack anti-pattern architecture 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. autojack anti-pattern autohub 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. autojack anti-pattern autohub 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. autojack anti-pattern autohub 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`. autojack anti-pattern autohub 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. autojack anti-pattern architecture 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. autojack anti-pattern debugging