<?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>Forem:  Grace Abayomi</title>
    <description>The latest articles on Forem by  Grace Abayomi (@abayomi_grace).</description>
    <link>https://forem.com/abayomi_grace</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3764920%2F06c2fe3a-c180-451e-b4f9-8546c05f9d34.jpg</url>
      <title>Forem:  Grace Abayomi</title>
      <link>https://forem.com/abayomi_grace</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/abayomi_grace"/>
    <language>en</language>
    <item>
      <title>Competitive Edge in the Age of AI</title>
      <dc:creator> Grace Abayomi</dc:creator>
      <pubDate>Fri, 27 Feb 2026 11:29:45 +0000</pubDate>
      <link>https://forem.com/abayomi_grace/competitive-edge-in-the-age-of-ai-88j</link>
      <guid>https://forem.com/abayomi_grace/competitive-edge-in-the-age-of-ai-88j</guid>
      <description>&lt;p&gt;I had to fix a batch of vulnerabilities in one of our applications at work the other day. &lt;br&gt;
I thought to myself, "I'll get AI to do this for me". &lt;/p&gt;

&lt;p&gt;I knew what needed to be done, dependency upgrades that could potentially break the build. It felt like the perfect task for AI: Upgrade the dependencies. Fix the build. Save me the time.&lt;/p&gt;

&lt;p&gt;I prompted the AI tool, I observed it's reasoning process, really impressive and methodical. When it finished, I noticed over 20 files had been modified, with additional 6-8 dependencies added to the POM file. &lt;br&gt;
Technically, my vulnerabilities were resolved.&lt;br&gt;
However, from experience, I knew there was some sort of overengineering going on. &lt;br&gt;
What AI had done was to patch each vulnerable dependency individually. The symptoms had been treated. &lt;br&gt;
I knew upgrading the actual parent dependency would transitively resolve most of the vulnerabilities in one clean move, thereby treating the root cause. &lt;br&gt;
So I discarded all of AIs changes, and upgraded my parent dependency. A few build fixes and test later, work done.&lt;/p&gt;

&lt;p&gt;This experience reminded me of something important:&lt;br&gt;
Experience is becoming the differentiator.&lt;br&gt;
AI can do almost everything I can do, usually faster and maybe even better.&lt;br&gt;
In a job market increasingly shaped by AI, the real competition isn't speed. AI will win that every time.&lt;br&gt;
The real value is in judgment.&lt;/p&gt;

&lt;p&gt;Knowing when not to patch 20 files.&lt;br&gt;
Know when a solution could be cleaner.&lt;br&gt;
Knowing what will hurt you six months from now.&lt;/p&gt;

&lt;p&gt;The engineers who thrive won't be the ones who compete with AI. They'll be the ones who know how to use it and guide it for optimal result.&lt;/p&gt;

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