<?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: hamzaelidrissi</title>
    <description>The latest articles on DEV Community by hamzaelidrissi (@hamzaelidrissi).</description>
    <link>https://dev.to/hamzaelidrissi</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%2F3860872%2F66aa2dfb-b23c-425f-b087-e37ff62a80b3.png</url>
      <title>DEV Community: hamzaelidrissi</title>
      <link>https://dev.to/hamzaelidrissi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hamzaelidrissi"/>
    <language>en</language>
    <item>
      <title>How AI Agents Are Changing the Role of Developers</title>
      <dc:creator>hamzaelidrissi</dc:creator>
      <pubDate>Sat, 04 Apr 2026 11:30:52 +0000</pubDate>
      <link>https://dev.to/hamzaelidrissi/how-ai-agents-are-changing-the-role-of-developers-5ap4</link>
      <guid>https://dev.to/hamzaelidrissi/how-ai-agents-are-changing-the-role-of-developers-5ap4</guid>
      <description>&lt;p&gt;I recently attended a great talk at ParisJUG hosted at Doctolib, where Patrick Chanezon spoke about:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“The transformation of the developer role with AI agents.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This topic strongly resonated with my daily work as a Senior Java Engineer working with AI-augmented development.&lt;/p&gt;

&lt;p&gt;Here are three reflections from my experience.&lt;/p&gt;




&lt;h2&gt;
  
  
  1. From Developer to Agent Manager
&lt;/h2&gt;

&lt;p&gt;With the rise of AI agents, our role as developers is clearly evolving.&lt;/p&gt;

&lt;p&gt;I find myself spending less time writing every line of code, and more time:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;defining context&lt;/li&gt;
&lt;li&gt;designing architecture&lt;/li&gt;
&lt;li&gt;guiding AI agents that implement solutions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In many ways, we are moving from:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Developer → Agent Manager&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The value is shifting toward:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;orchestration&lt;/li&gt;
&lt;li&gt;validation&lt;/li&gt;
&lt;li&gt;system thinking&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Writing code is no longer the bottleneck.&lt;br&gt;&lt;br&gt;
Thinking clearly is.&lt;/p&gt;




&lt;h2&gt;
  
  
  2. AI as a Mentor… but with a Risk
&lt;/h2&gt;

&lt;p&gt;AI can dramatically accelerate learning.&lt;/p&gt;

&lt;p&gt;For example, reading a 600-page technical book can take days or weeks.&lt;br&gt;&lt;br&gt;
With tools like NotebookLM, you can extract key insights in a few hours.&lt;/p&gt;

&lt;p&gt;But from my experience, something is lost in the process.&lt;/p&gt;

&lt;p&gt;Traditional reading improves:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;retention&lt;/li&gt;
&lt;li&gt;depth of understanding&lt;/li&gt;
&lt;li&gt;long-term intuition&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The real risk is simple:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Delegating too much thinking to AI.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The right approach is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use AI as a teammate, not a replacement
&lt;/li&gt;
&lt;li&gt;Let it challenge your ideas
&lt;/li&gt;
&lt;li&gt;But keep ownership of the reasoning
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;AI should amplify your thinking — not replace it.&lt;/p&gt;




&lt;h2&gt;
  
  
  3. The Hidden Topics: Dopamine and Cost
&lt;/h2&gt;

&lt;p&gt;Two topics are often underestimated when working with AI:&lt;/p&gt;

&lt;h3&gt;
  
  
  Dopamine &amp;amp; Feedback Loops
&lt;/h3&gt;

&lt;p&gt;AI creates extremely fast feedback cycles:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;you generate an idea
&lt;/li&gt;
&lt;li&gt;AI implements it instantly
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is powerful, but it can also lead to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;very long sessions
&lt;/li&gt;
&lt;li&gt;mental fatigue
&lt;/li&gt;
&lt;li&gt;reduced focus
&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Cost Awareness (AI FinOps)
&lt;/h3&gt;

&lt;p&gt;Another key aspect is cost.&lt;/p&gt;

&lt;p&gt;Without proper practices, usage can grow very quickly.&lt;/p&gt;

&lt;p&gt;From my experience, a few simple habits help:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;switching models depending on the task
&lt;/li&gt;
&lt;li&gt;using different agents for different needs
&lt;/li&gt;
&lt;li&gt;writing precise prompts with strong context
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is essentially &lt;strong&gt;AI FinOps for developers&lt;/strong&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;AI agents are not replacing developers.&lt;/p&gt;

&lt;p&gt;But they are clearly transforming our role toward:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;orchestration
&lt;/li&gt;
&lt;li&gt;system-level thinking
&lt;/li&gt;
&lt;li&gt;higher-level decision making
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The real challenge is not adopting AI.&lt;/p&gt;

&lt;p&gt;It’s learning how to use it ntelligently and responsibly&lt;/p&gt;

&lt;p&gt;Thanks to Patrick Chanezon for the inspiring talk&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>career</category>
      <category>softwareengineering</category>
    </item>
  </channel>
</rss>
