<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Byron's Development Blog on Byron DG — The Upstream</title><link>https://byrondgdev.com/</link><description>Recent content in Byron's Development Blog on Byron DG — The Upstream</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://byrondgdev.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Intent Engineering, Part 3: Grade the Grader</title><link>https://byrondgdev.com/posts/intent-engineering-grade-the-grader/</link><pubDate>Tue, 09 Jun 2026 09:00:00 +0000</pubDate><guid>https://byrondgdev.com/posts/intent-engineering-grade-the-grader/</guid><description>&lt;p&gt;In the last post I showed that an agent&amp;rsquo;s identity actually sticks when you encode it as structure, a required section in the output, rather than a behavior you hope the model performs. I measured that by having a second model read the agent&amp;rsquo;s transcript and score whether it did the things its identity says it does.&lt;/p&gt;
&lt;p&gt;You may have already spotted the problem. Can you trust a model to grade a model? I didn&amp;rsquo;t think so. Then I built it anyway, because it was the only way to get numbers at any useful scale. And it lied to me. Three times, with total confidence, in three different ways. This post is about why I kept it anyway, and what catching it taught me about measuring anything an agent does.&lt;/p&gt;</description></item><item><title>Intent Engineering, Part 2: Making It Stick</title><link>https://byrondgdev.com/posts/intent-engineering-making-it-stick/</link><pubDate>Sun, 07 Jun 2026 09:00:00 +0000</pubDate><guid>https://byrondgdev.com/posts/intent-engineering-making-it-stick/</guid><description>&lt;p&gt;I ended the last post with a confession. I&amp;rsquo;d written about giving an agent a real identity. Not a system prompt with a list of rules, but a document that says who this agent is, how it thinks, what it values, and what call it would make when nobody is around to ask. I called it intent engineering, and said it was the most leverage you can get out of an agent for the least code. Then, near the bottom, I admitted the thing that had been nagging me the whole time. I had no way to measure whether any of it was working.&lt;/p&gt;</description></item><item><title>Intent Engineering: Giving AI Agents Identity</title><link>https://byrondgdev.com/posts/intent-engineering-giving-agents-identity/</link><pubDate>Mon, 06 Apr 2026 09:00:00 +0000</pubDate><guid>https://byrondgdev.com/posts/intent-engineering-giving-agents-identity/</guid><description>&lt;p&gt;What if your AI agent forgot who it was every morning?&lt;/p&gt;
&lt;p&gt;Not its tools. Not its instructions. Those are easy to reload. I mean its judgment. The priorities it weighs when two valid options exist and the instructions don&amp;rsquo;t cover which one to pick. The instinct to escalate &lt;em&gt;this&lt;/em&gt; decision but handle &lt;em&gt;that&lt;/em&gt; one quietly. The difference between a capable contractor and a trusted colleague.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s the problem I kept running into. I had agents that could do the work. They just didn&amp;rsquo;t know &lt;em&gt;my&lt;/em&gt; work. Every session started from scratch, and every session I was re-explaining things that a human teammate would have absorbed in their first week.&lt;/p&gt;</description></item><item><title>About</title><link>https://byrondgdev.com/pages/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://byrondgdev.com/pages/about/</guid><description>&lt;div style="text-align: center; margin: 2rem 0 3rem;"&gt;
 &lt;img src="https://byrondgdev.com/img/byrondg-wordmark.png" alt="Byron DG" style="max-width: 480px; width: 100%; border-radius: 6px;" /&gt;
&lt;/div&gt;
&lt;p&gt;Hi, I&amp;rsquo;m Byron.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m a software engineer building the systems that build systems — the infrastructure behind AI and autonomous agents.&lt;/p&gt;
&lt;p&gt;This blog focuses on agentic engineering and sharing my learnings as I go.&lt;/p&gt;</description></item><item><title>Privacy Policy</title><link>https://byrondgdev.com/pages/privacy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://byrondgdev.com/pages/privacy/</guid><description>&lt;h1 id="privacy-policy"&gt;Privacy Policy&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Last updated:&lt;/strong&gt; March 2026&lt;/p&gt;
&lt;p&gt;This privacy policy describes how The Upstream (&amp;ldquo;we,&amp;rdquo; &amp;ldquo;us,&amp;rdquo; or &amp;ldquo;our&amp;rdquo;), a personal technical blog operated by Byron Dupuis-George, handles information when you visit our website.&lt;/p&gt;
&lt;h2 id="the-short-version"&gt;The Short Version&lt;/h2&gt;
&lt;p&gt;This is a static blog. We don&amp;rsquo;t use cookies, we don&amp;rsquo;t run tracking scripts, and we don&amp;rsquo;t collect your personal information directly. Our hosting provider (Netlify) collects basic server logs as part of delivering the site to you. Some fonts are loaded from third-party CDNs, which means those providers receive your IP address when pages load.&lt;/p&gt;</description></item><item><title>Terms of Use</title><link>https://byrondgdev.com/pages/terms/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://byrondgdev.com/pages/terms/</guid><description>&lt;h1 id="terms-of-use"&gt;Terms of Use&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Last updated:&lt;/strong&gt; March 2026&lt;/p&gt;
&lt;p&gt;These terms govern your use of The Upstream (this website), a personal technical blog operated by Byron Dupuis-George. By accessing this website, you agree to these terms.&lt;/p&gt;
&lt;h2 id="content-and-accuracy"&gt;Content and Accuracy&lt;/h2&gt;
&lt;p&gt;The content on this website — including articles, code samples, tutorials, and opinions — is provided for informational and educational purposes only. While we strive to be accurate:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Technical content reflects understanding at the time of writing and may become outdated&lt;/li&gt;
&lt;li&gt;Code samples are provided as-is and should be reviewed and tested before use in production&lt;/li&gt;
&lt;li&gt;Opinions expressed are the author&amp;rsquo;s own and do not constitute professional advice&lt;/li&gt;
&lt;li&gt;We make no guarantees about the completeness, reliability, or suitability of any content&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="intellectual-property"&gt;Intellectual Property&lt;/h2&gt;
&lt;h3 id="our-content"&gt;Our Content&lt;/h3&gt;
&lt;p&gt;All original content on this website, including text, graphics, logos, and images, is the property of Byron Dupuis-George unless otherwise stated. This content is protected by United States copyright law.&lt;/p&gt;</description></item></channel></rss>