<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>CodeHerder Insights</title><description>Notes on shipping with AI coding agents: coordination, cost, and what the herd can actually do.</description><link>https://codeherder.com/</link><item><title>Shipping without code: a non-technical builder&apos;s playbook for AI coding agents</title><link>https://codeherder.com/blog/non-technical-builders-playbook/</link><guid isPermaLink="true">https://codeherder.com/blog/non-technical-builders-playbook/</guid><description>You don&apos;t need to write code to ship real software with AI agents — you need to brief clearly, review the right things, and let the gates do the work. A practical playbook for founders and product people.</description><pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate><category>product</category><category>workflow</category><category>guide</category><author>The CodeHerder team</author></item><item><title>Can you trust AI-generated code? A practical guide to reviewing agent work at scale</title><link>https://codeherder.com/blog/trusting-ai-generated-code/</link><guid isPermaLink="true">https://codeherder.com/blog/trusting-ai-generated-code/</guid><description>The real objection to AI coding agents isn&apos;t whether they can write code — it&apos;s whether you can trust code you didn&apos;t watch get written. Here&apos;s how gates, not faith, make that answer yes.</description><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><category>review</category><category>quality</category><category>trust</category><category>agents</category><author>The CodeHerder team</author></item><item><title>How to run a team of AI coding agents: a practical guide to orchestration</title><link>https://codeherder.com/blog/how-to-orchestrate-ai-coding-agents/</link><guid isPermaLink="true">https://codeherder.com/blog/how-to-orchestrate-ai-coding-agents/</guid><description>Going from one AI coding agent to a coordinated fleet that ships reviewed, cost-bounded work — the problems that show up and the operating model that fixes them.</description><pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate><category>orchestration</category><category>agents</category><category>workflow</category><category>guide</category><author>The CodeHerder team</author></item><item><title>Cost-aware AI engineering: keeping agent spend visible and bounded</title><link>https://codeherder.com/blog/cost-aware-ai-engineering/</link><guid isPermaLink="true">https://codeherder.com/blog/cost-aware-ai-engineering/</guid><description>Token spend is easy to lose track of once more than one agent is running. Here&apos;s how to keep it visible per task, per agent, and per model — without ever routing it through a black box.</description><pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate><category>cost</category><category>observability</category><category>engineering</category><author>The CodeHerder team</author></item><item><title>One agent is a tool; a herd needs a shepherd</title><link>https://codeherder.com/blog/one-agent-is-a-tool-a-herd-needs-a-shepherd/</link><guid isPermaLink="true">https://codeherder.com/blog/one-agent-is-a-tool-a-herd-needs-a-shepherd/</guid><description>A single coding agent is easy to supervise. Ten of them, across machines and tasks, is a coordination problem — and coordination is the part nobody&apos;s tool was built to solve.</description><pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate><category>coordination</category><category>agents</category><category>orchestration</category><author>The CodeHerder team</author></item><item><title>Ship a product idea without an engineer</title><link>https://codeherder.com/blog/one-idea-no-engineer/</link><guid isPermaLink="true">https://codeherder.com/blog/one-idea-no-engineer/</guid><description>You know exactly what &apos;done&apos; looks like. Here&apos;s how to go from a plain-language brief to a shipped, reviewed change — without writing a line of code yourself.</description><pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate><category>product</category><category>workflow</category><category>no-code adjacent</category><author>The CodeHerder team</author></item></channel></rss>