<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Patrick Elmore</title><description>Notes on AI-assisted software development. Tooling, workflow, and team practices for building with AI agents.</description><link>https://patrickelmore.com/</link><language>en-us</language><item><title>When letting it rip goes wrong: how I let Claude delete my database</title><link>https://patrickelmore.com/posts/when-letting-it-rip-goes-wrong/</link><guid isPermaLink="true">https://patrickelmore.com/posts/when-letting-it-rip-goes-wrong/</guid><description>A year of disciplined Claude Code use, sophisticated guardrails, more than a thousand hours of practice. The agent destroyed my database anyway.</description><pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate><category>claude-code</category><category>field-notes</category><category>incident-report</category><category>ai-development</category></item><item><title>Generation Is Not Retrieval: What &apos;Hallucination&apos; Actually Is</title><link>https://patrickelmore.com/posts/generation-is-not-retrieval/</link><guid isPermaLink="true">https://patrickelmore.com/posts/generation-is-not-retrieval/</guid><description>Developers treat hallucination as a lookup that went wrong. The mechanism is that the model generates plausible continuations and there is no lookup. Verification isn&apos;t a bug to fix on the model side. It&apos;s a structural job on the user side.</description><pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate><category>mental-models</category><category>llm</category><category>hallucination</category><category>prompt-engineering</category><category>ai-development</category></item><item><title>Attention Is Not Memory: Why Models Re-Read Everything Every Turn</title><link>https://patrickelmore.com/posts/attention-is-not-memory/</link><guid isPermaLink="true">https://patrickelmore.com/posts/attention-is-not-memory/</guid><description>The model doesn&apos;t remember earlier turns. It re-reads the full transcript from scratch every turn. What feels like memory is re-reading, and the failure modes follow directly from that.</description><pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate><category>mental-models</category><category>llm</category><category>context-window</category><category>prompt-engineering</category><category>ai-development</category></item><item><title>The Context Window Is the Workspace, Not a Buffer</title><link>https://patrickelmore.com/posts/context-window-is-the-workspace/</link><guid isPermaLink="true">https://patrickelmore.com/posts/context-window-is-the-workspace/</guid><description>The folk model treats the context window as storage you load before the model knows things. The mechanism is the opposite: the window is the workspace itself, and every token in it shapes every answer the model gives.</description><pubDate>Sat, 09 May 2026 00:00:00 GMT</pubDate><category>mental-models</category><category>llm</category><category>context-window</category><category>prompt-engineering</category><category>ai-development</category></item><item><title>Working With LLMs Effectively: Mental Models That Actually Match the Mechanism</title><link>https://patrickelmore.com/posts/working-with-llms-effectively/</link><guid isPermaLink="true">https://patrickelmore.com/posts/working-with-llms-effectively/</guid><description>Effective collaboration with a capable LLM is mutual deference based on honest capability assessment. Most prompt engineering is the human refusing to do the partition.</description><pubDate>Thu, 07 May 2026 00:00:00 GMT</pubDate><category>mental-models</category><category>llm</category><category>prompt-engineering</category><category>ai-development</category><category>agent-workflow</category></item><item><title>Feedback Loops That Compound</title><link>https://patrickelmore.com/posts/feedback-loops-ai-agents/</link><guid isPermaLink="true">https://patrickelmore.com/posts/feedback-loops-ai-agents/</guid><description>Capture is cheap and aggressive. Promotion to rules is expensive and conservative. The discipline that separates compounding feedback from rule-set pollution is the gate between them.</description><pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate><category>engineering-with-agents</category><category>feedback-loops</category><category>agent-workflow</category><category>ai-development</category><category>software-process</category></item><item><title>Orchestration Patterns for Multi-Agent Work</title><link>https://patrickelmore.com/posts/multi-agent-orchestration-patterns/</link><guid isPermaLink="true">https://patrickelmore.com/posts/multi-agent-orchestration-patterns/</guid><description>Once more than one agent is in a pipeline, the load-bearing engineering act is the discipline at the boundaries between them.</description><pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate><category>engineering-with-agents</category><category>multi-agent-orchestration</category><category>agent-workflow</category><category>ai-development</category><category>software-process</category></item><item><title>Composing the Context</title><link>https://patrickelmore.com/posts/composing-the-context-agent-failures/</link><guid isPermaLink="true">https://patrickelmore.com/posts/composing-the-context-agent-failures/</guid><description>Most failures attributed to bad model output are composition failures: the wrong material, in the wrong order, with no rule for which source wins.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>engineering-with-agents</category><category>context-engineering</category><category>agent-workflow</category><category>ai-development</category><category>software-process</category></item><item><title>Context Pollution</title><link>https://patrickelmore.com/posts/context-pollution-debris-not-capacity/</link><guid isPermaLink="true">https://patrickelmore.com/posts/context-pollution-debris-not-capacity/</guid><description>Output quality degrades because the room is full of debris, not because the room is full. The fix is structural, not a bigger window.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>engineering-with-agents</category><category>context-engineering</category><category>agent-workflow</category><category>ai-development</category><category>software-process</category></item><item><title>Tiered Planning as Engineering Discipline</title><link>https://patrickelmore.com/posts/tiered-planning-engineering-discipline/</link><guid isPermaLink="true">https://patrickelmore.com/posts/tiered-planning-engineering-discipline/</guid><description>Iterative development applied to the planning function itself. The checkpoints between tiers are the entire mechanism.</description><pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate><category>engineering-with-agents</category><category>planning</category><category>agent-workflow</category><category>ai-development</category><category>software-process</category></item></channel></rss>