<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>About AI on Michael Aguilar</title>
    <link>/ai/</link>
    <description>Recent content in About AI on Michael Aguilar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 10 Mar 2026 08:16:00 +0000</lastBuildDate>
    <atom:link href="/ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ask Questions Until You Have a Complete Understanding of the Problem</title>
      <link>/ai/keep-asking-questions/</link>
      <pubDate>Tue, 10 Mar 2026 08:16:00 +0000</pubDate>
      <guid>/ai/keep-asking-questions/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;/ai/keep-asking-questions/robot_washing_car.png&#34;&#xA;    alt=&#34;Robot washing it&amp;#39;s car&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;You’ve probably seen the “car wash question” floating around AI forums by now. It’s become something of a Turing test for prompting skills, and a lot of LLMs fail it on the first try.&lt;/p&gt;&#xA;&lt;p&gt;Here’s the setup: you ask an LLM, &lt;em&gt;“I need to wash my car. The car wash is 100 yards away. Should I walk or drive?”&lt;/em&gt; A lot of times, the model confidently tells you to walk. After all, it’s only a football field’s distance - why burn gas?&lt;/p&gt;</description>
    </item>
    <item>
      <title>AI Turns Senior Devs into Junior Devs</title>
      <link>/ai/ai-turns-senior-devs-to-junior/</link>
      <pubDate>Fri, 06 Mar 2026 08:16:00 +0000</pubDate>
      <guid>/ai/ai-turns-senior-devs-to-junior/</guid>
      <description>&lt;p&gt;&lt;figure&gt;&lt;img src=&#34;/ai/ai-turns-senior-devs-to-junior/robot_cats.jpg&#34;&#xA;    alt=&#34;Unsuccessfully herding robot cats&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;A lot of people assume AI coding assistants are an elevator to the top floor - that junior developers jump straight to senior productivity and seniors become superhuman. The reality is inverted. Right now, AI is resetting senior developers back to junior status, complete with the confusion, trial-and-error, and questionable output that comes with learning something entirely new.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-documentation-desert&#34;&gt;The Documentation Desert&lt;/h2&gt;&#xA;&lt;p&gt;When you learned to code, there were textbooks. Style guides. Stack Overflow threads from 2009 explaining exactly why your regex was failing. With agentic coding, that foundation doesn&amp;rsquo;t exist yet.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Vibe coding still sucks</title>
      <link>/ai/vibe-coding-still-sucks/</link>
      <pubDate>Sat, 07 Feb 2026 09:02:00 +0000</pubDate>
      <guid>/ai/vibe-coding-still-sucks/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;/ai/vibe-coding-still-sucks/confused_agent.png&#34;&#xA;    alt=&#34;Confused robot&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;h2 id=&#34;the-confusion&#34;&gt;The confusion&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been confused about comments and articles talking about vibe-coding. Many of the comments are along the lines of &amp;ldquo;it&amp;rsquo;s only good for small scripts,&amp;rdquo; or &amp;ldquo;it always generates garbage.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;That seemed at odds with my own experience with AI-assisted coding. I&amp;rsquo;ve been getting great results with &lt;a href=&#34;https://aider.chat&#34;&gt;&lt;code&gt;aider-chat&lt;/code&gt;&lt;/a&gt;. It&amp;rsquo;s a command line app with no sub-agents, utilities, or anything like that. I&amp;rsquo;ve been responsible for much of the planning and guidance, and it&amp;rsquo;s been working well.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Custom Software for Everyone</title>
      <link>/ai/custom-software-for-everyone/</link>
      <pubDate>Thu, 05 Feb 2026 08:16:00 +0000</pubDate>
      <guid>/ai/custom-software-for-everyone/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s still a little early for this to be a reality, but it&amp;rsquo;s coming. The tools aren&amp;rsquo;t quite ready, and not enough people have the skills to make it happen. It won&amp;rsquo;t be long, though, before even the smallest businesses can justify hiring someone to write custom software for them.&lt;/p&gt;&#xA;&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;&#xA;&lt;p&gt;AI-assisted development will soon make developers so efficient that custom, end-to-end software integration will become affordable for small businesses. Right now, small businesses rely on a patchwork of off-the-shelf tools, creating inefficiencies as employees manually move data between them. The high cost of developers makes true custom solutions impractical.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Craftsman and the Code</title>
      <link>/ai/the-craftsman-and-the-code/</link>
      <pubDate>Sun, 18 Jan 2026 06:16:00 +0000</pubDate>
      <guid>/ai/the-craftsman-and-the-code/</guid>
      <description>&lt;p&gt;To explain what&amp;rsquo;s happening with AI in software development, it helps to look at how a developer&amp;rsquo;s work is changing - how it was done, how it&amp;rsquo;s being done now, and where it&amp;rsquo;s heading.&lt;/p&gt;&#xA;&lt;p&gt;Instead of computers, let&amp;rsquo;s talk about building furniture. It&amp;rsquo;s not a perfect analogy, but it works.&lt;/p&gt;&#xA;&lt;p&gt;At some point in history, if you wanted furniture you needed to talk to a skilled craftsman. Anyone who has taken a shot at making simple furniture can attest that it takes more than hammering a few boards together. There are specialized tools and materials, each with their own strengths and weaknesses.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Interviewing Using AI Is Not Cheating</title>
      <link>/ai/interviewing-using-ai-is-not-cheating/</link>
      <pubDate>Sun, 02 Nov 2025 06:16:00 +0000</pubDate>
      <guid>/ai/interviewing-using-ai-is-not-cheating/</guid>
      <description>&lt;p&gt;There&amp;rsquo;s a lot of complaining about candidates using AI during coding interviews. They say it&amp;rsquo;s &amp;ldquo;cheating&amp;rdquo;.&lt;/p&gt;&#xA;&lt;p&gt;No, it&amp;rsquo;s not.&lt;/p&gt;&#xA;&lt;p&gt;Using AI during an interview should be expected and encouraged. The goal of an interview isn&amp;rsquo;t to see if a candidate can pass a test. The goal is to figure out how well they would do the job.&lt;/p&gt;&#xA;&lt;p&gt;This article talks about writing code, but the idea applies to just about any knowledge-focused job.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AI Development: Research, Plan, Implement</title>
      <link>/ai/aidev-research-plan-implement/</link>
      <pubDate>Sun, 12 Oct 2025 18:44:00 +0000</pubDate>
      <guid>/ai/aidev-research-plan-implement/</guid>
      <description>&lt;p&gt;Let&amp;rsquo;s say you have a problem, and you&amp;rsquo;re pretty sure that writing an app is the solution. Maybe you want a basic inventory system for your small business. Or maybe you have a small piece of a large legacy system that needs upgrading. It doesn&amp;rsquo;t matter what it is.&lt;/p&gt;&#xA;&lt;p&gt;You have a problem, you want software, and you want to make the most of agentic development.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-problem-with-vibe-planning&#34;&gt;The Problem with &amp;ldquo;Vibe-Planning&amp;rdquo;&lt;/h2&gt;&#xA;&lt;p&gt;The impulse is to just start chatting with an AI. You describe your problem, the AI suggests something, you correct it, it suggests something else, and you keep going back and forth until you have what &lt;em&gt;seems&lt;/em&gt; like a solid plan.&lt;/p&gt;&#xA;&lt;p&gt;This is &amp;ldquo;vibe-planning.&amp;rdquo; It feels productive, but it has a major flaw. The result is what &lt;em&gt;you&lt;/em&gt; think is a good plan, which may or may not actually be a good plan. An AI will happily follow you down a bad path if you lead it there.&lt;/p&gt;&#xA;&lt;p&gt;There&amp;rsquo;s a better way. The cool kids are calling it &amp;ldquo;Research, Plan, and Implement&amp;rdquo;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Disappearance of the Entry-Level Job</title>
      <link>/ai/the-disapperance-of-the-entry-level-job/</link>
      <pubDate>Fri, 03 Oct 2025 08:44:00 +0000</pubDate>
      <guid>/ai/the-disapperance-of-the-entry-level-job/</guid>
      <description>&lt;p&gt;The headlines are terrifying. Every day seems to bring another story about how AI is going to wipe out entire categories of jobs. &amp;ldquo;The Disappearance of the Entry-Level Job&amp;rdquo; is a popular one.&lt;/p&gt;&#xA;&lt;p&gt;These articles paint a grim picture of a world with no starting point for a career.&lt;/p&gt;&#xA;&lt;p&gt;Like most things, the truth is somewhere in-between. While it&amp;rsquo;s true that many familiar junior-level positions are being changed or eliminated, that doesn&amp;rsquo;t mean there are no junior-level positions.&lt;/p&gt;&#xA;&lt;p&gt;Say it with me: &amp;ldquo;the jobs will change&amp;rdquo;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AI and the Hiring Landscape</title>
      <link>/ai/ai-and-the-hiring-landscape/</link>
      <pubDate>Sun, 28 Sep 2025 07:09:00 +0000</pubDate>
      <guid>/ai/ai-and-the-hiring-landscape/</guid>
      <description>&lt;p&gt;There’s a lot of chatter about AI reshaping hiring, but it’s not as simple as “replace recruiters” or “solve everything.” The impact depends on how it’s trained, how it’s prompted, and how it’s used. It could streamline things or make them worse, depending on the setup.&lt;/p&gt;</description>
    </item>
    <item>
      <title>It Sucks Being a Manager</title>
      <link>/ai/it-sucks-being-a-manager/</link>
      <pubDate>Fri, 05 Sep 2025 07:39:00 +0000</pubDate>
      <guid>/ai/it-sucks-being-a-manager/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve written quite a bit about the overall process of AI-assisted development. Not the &amp;ldquo;write code&amp;rdquo; part of it - if anything, that&amp;rsquo;s the easy part. There&amp;rsquo;s a process to writing a project which can be maintained, with bug fixes and new features.&lt;/p&gt;&#xA;&lt;p&gt;What&amp;rsquo;s a little tough right now is constantly being in the position of being a manager, stakeholder, business, and end-user. I&amp;rsquo;ve understood it in an abstract, and tend to be careful about considering them.&lt;/p&gt;&#xA;&lt;p&gt;It&amp;rsquo;s so very &lt;em&gt;visceral&lt;/em&gt; now.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Which AI Model Should I Use For Coding?</title>
      <link>/ai/which-ai-model-should-i-use-for-coding/</link>
      <pubDate>Fri, 05 Sep 2025 06:09:00 +0000</pubDate>
      <guid>/ai/which-ai-model-should-i-use-for-coding/</guid>
      <description>&lt;p&gt;Most of the big players (Anthropic, Google, et. al) provide all-in-one solutions for writing code. If that&amp;rsquo;s what you&amp;rsquo;re doing, that&amp;rsquo;s fine, but you may be missing out.&lt;/p&gt;&#xA;&lt;p&gt;For one thing, they can be pretty expensive (unless your company is paying for it). Anthropic&amp;rsquo;s best - Opus - can get really expensive, really fast. Admittedly, it still costs less than paying for an overseas team, but if it&amp;rsquo;s coming out of your wallet you&amp;rsquo;re bound to notice.&lt;/p&gt;&#xA;&lt;p&gt;Considering how quickly everything is moving, I&amp;rsquo;m sure this post will age like milk.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Advanced AI Code Automation</title>
      <link>/ai/more-advanced-automation/</link>
      <pubDate>Mon, 01 Sep 2025 07:09:00 +0000</pubDate>
      <guid>/ai/more-advanced-automation/</guid>
      <description>&lt;p&gt;So, you&amp;rsquo;ve got a great process down for developing your code. You&amp;rsquo;ve got great documentation, 100% test coverage, good git branching and tagging, and all the other detailed steps for generating code.&lt;/p&gt;&#xA;&lt;p&gt;It sure is a lot of typing, though, isn&amp;rsquo;t it? Very repititious. Obviously, you should automate those steps! You&amp;rsquo;re only a little bit away from typing in &amp;ldquo;Write me an app that does X,Y, and Z!&amp;rdquo; and then taking a nap while it does the work!&lt;/p&gt;&#xA;&lt;p&gt;Not so fast&amp;hellip;&lt;/p&gt;</description>
    </item>
    <item>
      <title>&#34;AI is a bubble!&#34; Yea, So What?</title>
      <link>/ai/ai-a-bubble-so-what/</link>
      <pubDate>Fri, 29 Aug 2025 13:09:00 +0000</pubDate>
      <guid>/ai/ai-a-bubble-so-what/</guid>
      <description>&lt;p&gt;&amp;ldquo;AI is just a bubble!&amp;rdquo; Yep, sure is. So what? That&amp;rsquo;s no reason to ignore it, or to brush it off as a fad. While nobody can be 100% sure exactly how it will make the world look in five years, you can be sure the world will look different.&lt;/p&gt;&#xA;&lt;p&gt;Calling something a &amp;ldquo;bubble&amp;rdquo; is often a way to dismiss it. But history shows that even when a bubble pops, the underlying technology doesn&amp;rsquo;t just go away. It sticks around and changes everything.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How AI will change a developer&#39;s job</title>
      <link>/ai/ai-and-developers/</link>
      <pubDate>Sun, 10 Aug 2025 09:44:00 +0000</pubDate>
      <guid>/ai/ai-and-developers/</guid>
      <description>&lt;p&gt;There&amp;rsquo;s been a lot of noise about AI replacing developers. Spoiler: it won&amp;rsquo;t. But your job is changing in ways nobody&amp;rsquo;s really talking about.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AI Doesn&#39;t Eliminate Jobs, It Changes Them</title>
      <link>/ai/ai-doesnt-eliminate-jobs-it-changes-them/</link>
      <pubDate>Tue, 05 Aug 2025 08:34:00 +0000</pubDate>
      <guid>/ai/ai-doesnt-eliminate-jobs-it-changes-them/</guid>
      <description>&lt;p&gt;AI isn&amp;rsquo;t going to take your job, it&amp;rsquo;s going to &lt;em&gt;change&lt;/em&gt; your job. There are things you do as part of your job now which will go away, but new parts will be added.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reliably Building AI Systems</title>
      <link>/ai/reliably-building-ai-systems/</link>
      <pubDate>Mon, 04 Aug 2025 12:16:00 +0000</pubDate>
      <guid>/ai/reliably-building-ai-systems/</guid>
      <description>&lt;p&gt;I recently built a production-ready application entirely with AI assistance, 100% written by the AI - not as a proof-of-concept, but as a functional tool designed to solve complex workflow problems.&lt;/p&gt;&#xA;&lt;p&gt;It wasn&amp;rsquo;t magic, it was work.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; The application code is now over 5,600 lines of code, plus 16,000 lines of code in 883 tests giving 100% coverage including branches.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AI development: the good and bad</title>
      <link>/ai/ai-development-good-and-bad/</link>
      <pubDate>Sat, 02 Aug 2025 09:44:00 +0000</pubDate>
      <guid>/ai/ai-development-good-and-bad/</guid>
      <description>&lt;p&gt;There is a lot of discussion about using AI for development. Much of it is over-stated hype, either for or against.&lt;/p&gt;&#xA;&lt;p&gt;&amp;ldquo;AI only turns out garbage&amp;rdquo; is what some people will tell you.&lt;/p&gt;&#xA;&lt;p&gt;&amp;ldquo;AI will replace developers&amp;rdquo; is what others will say.&lt;/p&gt;&#xA;&lt;p&gt;Like most things, the truth is somewhere in-between.&lt;/p&gt;&#xA;&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;&#xA;&lt;p&gt;AI-assisted development can help create code faster, but pitfalls like amplified design flaws and cascading errors demand careful handling&lt;/p&gt;&#xA;&lt;p&gt;This article cuts through the hype by showing how unchecked AI use mirrors real-world failures like Knight Capital&amp;rsquo;s $500M loss (caused by human process gaps, not technology).&lt;/p&gt;&#xA;&lt;p&gt;Even skilled developers like &amp;ldquo;Alice, Bob, and Charlie&amp;rdquo; introduce subtle mistakes when inheriting code under time pressure, and AI accelerates these risks by acting like a new developer every time you hit &amp;ldquo;enter&amp;rdquo; - forgetting context, skipping safeguards, and magnifying poor documentation or rushed decisions.&lt;/p&gt;&#xA;&lt;p&gt;It is important that &lt;em&gt;you&lt;/em&gt; need to enforce defensive practices (like file operation safeguards and explicit error checks) while juggling roles as architect, reviewer, and quality gatekeeper to prevent small oversights from exploding at machine speed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
