{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiakzuopowrpm2nv6wpzfo6xos5mj7yb5bznlkkw3m7a2qjdfjhn74",
    "uri": "at://did:plc:25rdn5elo5izoxrmtis34zuk/app.bsky.feed.post/3mpomej57ia72"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreigdeshcr7pbpg53dr4gp4lyakvprajyi3dydigiu3auf7mpadoum4"
    },
    "mimeType": "image/webp",
    "size": 65552
  },
  "path": "/jcamarate/compound-engineering-is-the-only-ai-coding-idea-that-actually-compounds-n66",
  "publishedAt": "2026-07-02T17:29:00.000Z",
  "site": "https://dev.to",
  "tags": [
    "ai",
    "claudecode",
    "programming",
    "productivity",
    "separately"
  ],
  "textContent": "I've been building software with AI agents every day for months. The biggest thing I've learned has nothing to do with which model or which tool is hot this week. Its this: most people's AI output is flat. Every task starts from zero. The agent is just as sharp and just as forgetful as it was last week.\n\nKieran Klaassen and Dan Shipper at Every gave this problem a name - compound engineering. The idea is almost stupidly simple: each piece of work should make the next one easier, not harder. They run several products with basically single-person eng teams on the back of it. Once you feel the difference its really hard to go back.\n\nIt's usually drawn as a four step loop. Plan, work, assess, compound.\n\nPlan - before a line of code, the agents go read the codebase, the conventions, the framework versions, and hand you a plan you correct.\nWork - the plan drives the build. The agent writes the feature and the tests.\nAssess - review agents check it. Correctness, security, architecture.\nCompound - whatever you learned this time gets captured into durable rules and docs the system actually reads next time.\n\nEveryone does the first three. Almost nobody does the fourth.\n\nAnd the fourth is the whole point. Its the only step that actually compounds. Skip it and you dont have compound engineering - you have a very fast autocomplete with extra steps.\n\nEvery ships this as an open source claude code plugin, a set of /ce: commands that scaffold the plan, run the work, run the review. Genuinely good on-ramp. If you live in the terminal go grab it.\n\nBut the plugin isnt the loop. The loop is a discipline. The hard part was never typing /ce:plan - its doing the compound step honestly, every single time, when youre tired and the feature already works and you just want to merge and go to bed. Thats exactly where it dies.\n\nI ran this by hand for a while and the same leaks show up every time.\n\nThe compound step is optional, so it doesnt happen. Writing down what you learned is boring and nothing breaks when you skip it. So you skip it. And the system quietly stops compounding.\n\nYour memory is scattered. Lessons end up as random edits to a CLAUDE.md that slowly turns into a swamp, or worse, they live in your head. No record of why a decision got made, or that you corrected the agent on this exact thing last week.\n\nNothing is gated. The loop is a convention, not a wall. The second youre moving fast, work jumps from plan straight to merge and assess + compound fall off the back of the truck.\n\nThe deeper version of this - how decisions and context drift across a pile of parallel agents - is its own rabbit hole. I went into that one separately.\n\nSo heres the only question I actually care about now, every time I wire up an agent loop: a month from now, will this system be better at building my product than it is today? Or just as fluent, and just as forgetful?\n\nIf theres no compound step, you already know the answer.\n\nBuild the fourth step. Thats the whole game 🙌",
  "title": "compound engineering is the only AI coding idea that actually compounds"
}