Coding Agents Underestimate the Cost of Code They Own
Your coding agent just rebuilt a library you could have installed. Now every future change has to pay for that decision.
Your coding agent just rebuilt a library you could have installed. Now every future change has to pay for that decision.
Your CLI already knows its commands and flags, yet its docs—and the agents using it—often have to reconstruct them. I built CliDoc to turn those same definitions into reference pages and a complete machine-readable description.
git-dedup is a drop-in replacement for git that shares one copy of Git history across all your clones, worktrees, and submodules. It made my agents start dramatically faster and cut my Git storage by 70%.
Every time an AI agent has to reverse-engineer your library, you pay for the lesson in tokens. A clear, versioned README lets you write that knowledge once—especially for code the model has never seen.
A coding agent can fit in around 200 lines of TypeScript: ask Claude for shell commands, execute them, and feed back the results. What does that tiny loop accomplish, and where does it fall short?
I gave an LLM a shell and a few file tools, and it started writing and debugging its own code. Making that prototype useful meant solving less glamorous problems: blocked commands, oversized files, and a context window that kept filling up.
If rebuilding becomes cheaper than maintaining, the code may stop being the asset worth preserving. Requirements and behavioral tests could become the durable core, letting us choose tools for today and replace the implementation later.
Before taking my daughter to daycare, I turned two GitHub issues into feature PRs from my phone, without writing code. A few issue comments were enough for MyCoder to plan and implement the changes through GitHub Actions.
Giving MyCoder GitHub issues, pull requests, and CI logs changed what I needed to supervise. The surprising part was GitHub’s role as persistent memory: I could leave the agent working for 30 minutes and review its PRs asynchronously.
Adapting your codebase to match AI coder assumptions doesn't just help AI -- it uncovers hidden complexity, ultimately benefiting human developers.
My coding agent kept getting lost in a codebase I thought was well organized. Simplifying packages, imports, and type contracts made it more reliable—and exposed the same obstacles a new teammate would face.