<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Kato Emmanuel</title>
    <description>The latest articles on DEV Community by Kato Emmanuel (@kato_emmy).</description>
    <link>https://dev.to/kato_emmy</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4024341%2F6dc13f47-fdd3-408f-8e6e-1ad681de262f.jpg</url>
      <title>DEV Community: Kato Emmanuel</title>
      <link>https://dev.to/kato_emmy</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kato_emmy"/>
    <language>en</language>
    <item>
      <title>AI in Software Engineering</title>
      <dc:creator>Kato Emmanuel</dc:creator>
      <pubDate>Wed, 11 Nov 2026 12:12:34 +0000</pubDate>
      <link>https://dev.to/kato_emmy/ai-in-software-engineering-3ekn</link>
      <guid>https://dev.to/kato_emmy/ai-in-software-engineering-3ekn</guid>
      <description>&lt;p&gt;AI is changing how we build software, but not in the way the hype suggests.&lt;/p&gt;

&lt;p&gt;It won't replace engineers. It's changing where our time goes.&lt;/p&gt;

&lt;p&gt;What's already working:&lt;br&gt;
• Boilerplate and repetitive code written in seconds&lt;br&gt;
• Faster debugging, with a second pair of eyes on stack traces&lt;br&gt;
• Tests, docs, and code reviews that no longer get skipped&lt;br&gt;
• Learning an unfamiliar codebase in hours instead of days&lt;/p&gt;

&lt;p&gt;What still needs a human:&lt;br&gt;
• Deciding what to build and why&lt;br&gt;
• System design and trade-offs&lt;br&gt;
• Reviewing AI output critically, because it can be confidently wrong&lt;br&gt;
• Understanding the users and the business&lt;/p&gt;

&lt;p&gt;The engineers who do well won't be the ones who type the fastest. They'll be the ones who think clearly, ask good questions, and know when to trust the tool and when not to.&lt;/p&gt;

&lt;p&gt;How are you using AI in your workflow? I'd like to hear what's actually helping and what isn't.&lt;/p&gt;

&lt;h1&gt;
  
  
  AI #SoftwareEngineering #Programming #Developers #Tech
&lt;/h1&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>softwareengineering</category>
    </item>
  </channel>
</rss>
