<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on Iuri Madeira</title><link>https://iurimadeira.com/</link><description>Recent content in Home on Iuri Madeira</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 02 Sep 2026 09:00:00 -0300</lastBuildDate><atom:link href="https://iurimadeira.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Agents Blaze Trails. Scale Needs Roads.</title><link>https://iurimadeira.com/posts/ai-agents-can-blaze-trails/</link><pubDate>Wed, 02 Sep 2026 09:00:00 -0300</pubDate><guid>https://iurimadeira.com/posts/ai-agents-can-blaze-trails/</guid><description>&lt;p&gt;A paper recently went viral under a provocative title: &lt;a href="https://arxiv.org/abs/2606.05608v1"&gt;&lt;em&gt;The End of Software Engineering&lt;/em&gt;&lt;/a&gt;. Six days later, a second version appeared with a calmer name: &lt;a href="https://arxiv.org/abs/2606.05608v2"&gt;&lt;em&gt;Agentic Software: How AI Agents Are Restructuring the Software Paradigm&lt;/em&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;To the author’s credit, the change was more than cosmetic. The revised paper no longer says software engineering is ending. Instead, it describes an expansion into what it calls &lt;em&gt;Agentic Engineering&lt;/em&gt;.&lt;/p&gt;
&lt;div class="paradigm-shift" role="img" aria-label="AI to Software to Result versus Agent to Result"&gt;
&lt;strong&gt;AI → Software → Result&lt;/strong&gt;
&lt;span&gt;vs.&lt;/span&gt;
&lt;strong&gt;Agent → Result&lt;/strong&gt;
&lt;/div&gt;
&lt;p&gt;In the first path, AI helps create a persistent software artifact, which then produces the outcome. In the second, an agent plans and executes the work directly, generating and discarding code whenever useful. Software does not disappear. It becomes part of the agent’s runtime: a means to the result rather than the product handed to the user.&lt;/p&gt;</description></item></channel></rss>