Data gone. No error. No warning. No stack trace. Just… gone. Your app writing files using the File System Access API — which, by the way, is genuinely one of the most exciting things that's happened to the browser in years. A user picks a folder. You write to it. Clean, native, no server involved. The dream, right? Except on mobile, the dream has a bad habit of dying quietly. The browser process g
I was building offline-first apps for the Gnoke Suite and ran into the same wall every time. The File System Access API works beautifully — until your phone decides otherwise. A background OS kill. A tab reload at the wrong moment. Ten concurrent writes racing for the same stream. Any of these silently drops your data. No error. No warning. Just gone. The browser fantasy is: pick a folder, write
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
The codebase was old. React 16 with class components everywhere. React Router v3 with routes-as-children. A webpack 4 config that had been edited by a dozen people over five years and contained loaders nobody could explain. The dev server took 45 seconds to come up. Hot reload was 8 seconds on a good day, 20 on a bad one. The production build was 6 minutes. CI deploys took 14 minutes end to end. I
I recently shipped MetaBulkify, a Shopify app for bulk editing metaobjects via CSV. (Part 1 covers the metaobject-specific challenges.) The metaobject stuff was hard, but the Shopify platform stuff was harder. Here are three traps that aren't obvious from the docs. Week 1 of development. Nothing works. metaobjectDefinitions query returns an empty array. No error message. Just... nothing. The probl
Every production dApp built in 2022–2023 has the same problem sitting in its package.json: "wagmi": "^1.4.12", "ethers": "^5.7.2", "@rainbow-me/rainbowkit": "^1.3.5" These three libraries are tightly coupled. wagmi v2 dropped ethers entirely in favor of viem. RainbowKit v2 requires wagmi v2. Migrating one without the others breaks everything. Every team I've seen approach this migration does it t
Vibe coding is upon us, but it works best when the codebase has strong affordances — a concept in design that describes the possible actions an actor (in this case, a coding agent) can take, in relation to an object (in this case, the codebase): Affordance: a use or purpose that a thing can have, that people notice as part of the way they see or experience it. For a coding agent like Claude Code o
You're staring at a JSON API response and you need to paste it into a Kubernetes ConfigMap. Or your colleague sent you a YAML Helm values file and your integration test expects JSON. Either way, manually rewriting the format is tedious, error-prone, and a genuine waste of your afternoon. This is one of those tasks that sounds simple but hides dozens of small traps: indentation levels, quoted strin