<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Coding Agents on Tech Foundations</title><link>https://valery.tech/ai-engineering/coding-agents/</link><description>Recent content in Coding Agents on Tech Foundations</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2014-2023</copyright><atom:link href="https://valery.tech/ai-engineering/coding-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>Agents Md</title><link>https://valery.tech/ai-engineering/coding-agents/agents-md/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/coding-agents/agents-md/</guid><description>&lt;h1 id="operating-model"&gt;Operating Model&lt;/h1&gt;
&lt;p&gt;A practical mental model is to treat a coding agent as a capable colleague who starts each session with strong general knowledge but limited project-specific context.&lt;/p&gt;</description></item><item><title>Ca Dict</title><link>https://valery.tech/ai-engineering/coding-agents/ca-dict/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/coding-agents/ca-dict/</guid><description>&lt;p&gt;internal harness&lt;/p&gt;</description></item><item><title>Comprehension</title><link>https://valery.tech/ai-engineering/coding-agents/comprehension/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/coding-agents/comprehension/</guid><description>&lt;h2 id="project-understanding"&gt;Project understanding&lt;/h2&gt;
&lt;p&gt;The engineer must maintain a working mental model of the system. Coding agents can generate, modify, and explain code quickly, but they do not remove the need for human comprehension. In fact, they increase the need for it, because implementation velocity can exceed the engineer&amp;rsquo;s ability to evaluate whether a change is coherent.&lt;/p&gt;</description></item><item><title>Harness Engineering 1</title><link>https://valery.tech/ai-engineering/coding-agents/harness-engineering-1/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/coding-agents/harness-engineering-1/</guid><description/></item><item><title>Idiosyncrasy</title><link>https://valery.tech/ai-engineering/coding-agents/idiosyncrasy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/coding-agents/idiosyncrasy/</guid><description>&lt;h1 id="guide-working-with-idiosyncrasy-in-agent-ready-target-systems"&gt;Guide: Working with Idiosyncrasy in Agent-Ready Target Systems&lt;/h1&gt;
&lt;p&gt;A target system intended for coding agents should be evaluated not only by its runtime behavior, but also by its &lt;strong&gt;architectural legibility&lt;/strong&gt;. In this context, architectural legibility means that a competent newcomer &amp;ndash; human or agent &amp;ndash; can form reasonable expectations about where functionality is located, how changes should be made, and how those changes can be validated.&lt;/p&gt;</description></item><item><title>In Effective Context Engineering</title><link>https://valery.tech/ai-engineering/coding-agents/in-effective-context-engineering/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/coding-agents/in-effective-context-engineering/</guid><description>&lt;p&gt;After a few years of prompt engineering being the focus of attention in applied AI, a new term has come to prominence: &lt;strong&gt;context engineering&lt;/strong&gt;. Building with language models is becoming less about finding the right words and phrases for your prompts, and more about answering the broader question of &amp;ldquo;what configuration of context is most likely to generate our model&amp;rsquo;s desired behavior?&amp;rdquo;&lt;/p&gt;</description></item><item><title>In Harnes Building</title><link>https://valery.tech/ai-engineering/coding-agents/in-harnes-building/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/coding-agents/in-harnes-building/</guid><description>&lt;h1 id="harness-building-for-coding-agents"&gt;Harness-Building for Coding Agents&lt;/h1&gt;
&lt;h2 id="executive-summary"&gt;Executive summary&lt;/h2&gt;
&lt;p&gt;Recent writing by Martin Fowler, LangChain, OpenAI, GitHub, Anthropic, and open-source coding-agent projects converges on the same broad intuition: a coding agent is not just a model. It is a model embedded in a system of prompts, tools, files, plans, approvals, execution environments, and feedback loops.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;&lt;sup id="fnref:3"&gt;&lt;a href="#fn:3" class="footnote-ref" role="doc-noteref"&gt;3&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;</description></item><item><title>Part 0</title><link>https://valery.tech/ai-engineering/coding-agents/part-0/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/coding-agents/part-0/</guid><description>&lt;h1 id="part-0-what-i-understand-about-working-with-coding-agents-after-60b-token-events-in-9-months"&gt;Part 0: What I understand about working with coding agents after ~60B token events in 9 months&lt;/h1&gt;
&lt;p&gt;Over the last 9 months, my agentic engineering workflow has consumed roughly:&lt;/p&gt;</description></item><item><title>Perception And Context Management</title><link>https://valery.tech/ai-engineering/coding-agents/perception-and-context-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/coding-agents/perception-and-context-management/</guid><description>&lt;h1 id="perception-and-context-management-in-coding-agents"&gt;Perception and Context Management in Coding Agents&lt;/h1&gt;
&lt;h2 id="executive-summary"&gt;Executive summary&lt;/h2&gt;
&lt;p&gt;In the language of Martin Fowler and recent writing from LangChain, a harness is often treated as &amp;ldquo;everything around the model&amp;rdquo;: state, tool execution, feedback loops, constraints, memory, and orchestration.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt; That is operationally useful, but analytically too coarse for coding agents. Classical AI kept several of these functions separate: sensing and acting in a task environment, maintaining an estimated state under partial observability, controlling what remains in working memory, and closing the loop with monitoring and replanning.&lt;sup id="fnref:3"&gt;&lt;a href="#fn:3" class="footnote-ref" role="doc-noteref"&gt;3&lt;/a&gt;&lt;/sup&gt;&lt;sup id="fnref:4"&gt;&lt;a href="#fn:4" class="footnote-ref" role="doc-noteref"&gt;4&lt;/a&gt;&lt;/sup&gt;&lt;sup id="fnref:5"&gt;&lt;a href="#fn:5" class="footnote-ref" role="doc-noteref"&gt;5&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;</description></item><item><title>Project Ownership</title><link>https://valery.tech/ai-engineering/coding-agents/project-ownership/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/coding-agents/project-ownership/</guid><description>&lt;h1 id="project-understanding"&gt;Project understanding&lt;/h1&gt;
&lt;p&gt;We need to discuss a basic question of project understanding and manageability. This may sound obvious, but it becomes easy to forget when working with LLM-based coding agents.&lt;/p&gt;</description></item></channel></rss>