<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Engineering on emaat</title><link>https://emaat.dk/tags/ai-engineering/</link><description>Recent content in Ai-Engineering on emaat</description><generator>Hugo</generator><language>da-DK</language><lastBuildDate>Wed, 04 Nov 2026 20:36:55 +0100</lastBuildDate><atom:link href="https://emaat.dk/tags/ai-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>The Productivity-Experience Paradox</title><link>https://emaat.dk/articles/the-productivity-experience-paradox/</link><pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate><guid>https://emaat.dk/articles/the-productivity-experience-paradox/</guid><description>&lt;p&gt;&lt;strong&gt;Article:&lt;/strong&gt; &lt;a href="https://annievella.com/posts/the-productivity-experience-paradox/"&gt;The Productivity-Experience Paradox&lt;/a&gt; by Annie Vella&lt;/p&gt;&#10;&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;&#10;&lt;p&gt;Vella presents the second set of findings from her Masters research at the University of Auckland on how AI changes software engineering. The study followed engineers from October 2024 to April 2025 and asked two things at two points in time: how AI coding assistants affected their perceived productivity, and how they affected developer experience, measured with the DevEx framework&amp;rsquo;s three dimensions — feedback loops, cognitive load, and flow state.&lt;/p&gt;</description></item><item><title>Harness Design for Long Running Apps</title><link>https://emaat.dk/articles/harness-design-long-running-apps/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>https://emaat.dk/articles/harness-design-long-running-apps/</guid><description>&lt;p&gt;&lt;strong&gt;Article:&lt;/strong&gt; &lt;a href="https://www.anthropic.com/engineering/harness-design-long-running-apps"&gt;Harness design for long-running application development&lt;/a&gt; by Prithvi Rajasekaran&lt;/p&gt;&#10;&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;&#10;&lt;p&gt;Rajasekaran tackles two problems: getting Claude to produce high-quality frontend designs, and getting it to build complete applications without human intervention. Naive long-running setups fail in two ways. Models lose coherence as the context fills — some show &amp;ldquo;context anxiety&amp;rdquo; and wrap up early — and agents asked to judge their own work confidently praise it regardless of quality. Inspired by the generator/discriminator split in GANs, he separates creation from evaluation: a standalone evaluator is still lenient out of the box, but it is far easier to tune an evaluator to be sceptical than to make a generator self-critical.&lt;/p&gt;</description></item><item><title>The Advisor Strategy</title><link>https://emaat.dk/articles/the-advisor-strategy/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>https://emaat.dk/articles/the-advisor-strategy/</guid><description>&lt;p&gt;&lt;strong&gt;Article:&lt;/strong&gt; &lt;a href="https://claude.com/blog/the-advisor-strategy"&gt;The advisor strategy: Give agents an intelligence boost&lt;/a&gt; by Anthropic&lt;/p&gt;&#10;&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;&#10;&lt;p&gt;Anthropic introduces the advisor strategy — a cost-effective pattern for building AI agents that pairs Claude Opus as an advisor with a smaller model like Sonnet or Haiku as the executor. The smaller model runs the task end-to-end and calls on Opus only for the hard decisions, giving near Opus-level intelligence at close to Sonnet-level cost.&lt;/p&gt;&#10;&lt;p&gt;The executor calls tools, reads results, and iterates toward a solution on its own. When it hits a decision it can&amp;rsquo;t reasonably solve, it consults Opus, which reads the shared context and returns a plan, a correction, or a stop signal — but never calls tools or produces user-facing output. This inverts the usual sub-agent pattern, where a large orchestrator decomposes work for smaller workers: here the small model drives and escalates, with no decomposition, worker pool, or orchestration logic.&lt;/p&gt;</description></item></channel></rss>