<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering on Daniel's Tech Blog</title><link>https://tech.daniellbastos.com.br/tags/engineering/</link><description>Recent content in Engineering on Daniel's Tech Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 05 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://tech.daniellbastos.com.br/tags/engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Teaching AI to teach itself: Why configuration beats correction</title><link>https://tech.daniellbastos.com.br/posts/teaching-ai-to-teach-itself/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://tech.daniellbastos.com.br/posts/teaching-ai-to-teach-itself/</guid><description>&lt;p&gt;I spent weeks fighting with AI agents, giving detailed prompts every single time. &amp;ldquo;Write good commit messages. Add proper tests. Follow the project structure.&amp;rdquo; Over and over.&lt;/p&gt;
&lt;p&gt;It worked. Kind of. But it was exhausting.&lt;/p&gt;
&lt;p&gt;Then I realized: &lt;strong&gt;the quality of work you get from an AI agent is directly proportional to the effort you put into its configuration files.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Not the prompts. Not the model. The configuration.&lt;/p&gt;
&lt;h2 id="fix-the-workflow-not-the-instance"&gt;Fix the workflow, not the instance&lt;/h2&gt;
&lt;p&gt;When the AI makes the same mistake repeatedly—vague commit messages, incomplete tests, missing documentation—your instinct is to correct it in the moment.&lt;/p&gt;</description></item><item><title>The best code is the one you don't write</title><link>https://tech.daniellbastos.com.br/posts/the-best-code-is-the-one-you-dont-write/</link><pubDate>Wed, 04 Mar 2026 00:00:00 +0000</pubDate><guid>https://tech.daniellbastos.com.br/posts/the-best-code-is-the-one-you-dont-write/</guid><description>&lt;p&gt;As software developers, our goal has always been to build good software. In the AI era, this remains true. But here is what changed: our job is not just &amp;ldquo;writing good code&amp;rdquo; anymore.&lt;/p&gt;
&lt;p&gt;I have been building software for years. I wrote a lot of code. Good code. Bad code. Code that lasted. Code that I wish I could erase from existence. And now, looking back, I realize the game has changed. The role evolved.&lt;/p&gt;</description></item><item><title>Less hands, more brain</title><link>https://tech.daniellbastos.com.br/posts/less-hand-more-brain/</link><pubDate>Fri, 27 Feb 2026 00:00:00 +0000</pubDate><guid>https://tech.daniellbastos.com.br/posts/less-hand-more-brain/</guid><description>&lt;p&gt;Recently, I started a new project.&lt;/p&gt;
&lt;p&gt;Nothing absurdly complex. Not a moonshot. Just a real project with real deadlines, real expectations, and a team that needs things to work.&lt;/p&gt;
&lt;p&gt;At first sight, it was a greenfield initiative, &amp;ldquo;from zero.&amp;rdquo; But if we are honest, almost nothing in software is truly from zero. We had references from other projects, existing patterns, hard lessons from previous mistakes, and a company context that should not be ignored.&lt;/p&gt;</description></item><item><title>Dev x AI: between rejection and excitement</title><link>https://tech.daniellbastos.com.br/posts/dev-x-ai-between-rejection-and-excitement/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://tech.daniellbastos.com.br/posts/dev-x-ai-between-rejection-and-excitement/</guid><description>&lt;p&gt;From one developer to another, if I ignore the content bubble that needs to surf every &amp;ldquo;new summer trend,&amp;rdquo; I see two very clear feelings when the topic is AI: rejection and excitement.&lt;/p&gt;
&lt;h2 id="feeling-of-rejection"&gt;Feeling of rejection&lt;/h2&gt;
&lt;p&gt;This is the classic one: &amp;ldquo;I don&amp;rsquo;t need this,&amp;rdquo; &amp;ldquo;my code is already better,&amp;rdquo; &amp;ldquo;this only gets in the way,&amp;rdquo; &amp;ldquo;AI is dumb.&amp;rdquo; Deep down, it is almost never only about AI.&lt;/p&gt;
&lt;p&gt;This profile usually also has difficulty listening, collaborating, accepting review, and admitting mistakes. It is the &amp;ldquo;know-it-all&amp;rdquo; profile, always with a ready excuse to explain any bad decision or problem. But software development is not an individual sport.&lt;/p&gt;</description></item></channel></rss>