<?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: Ez Eldeen M</title>
    <description>The latest articles on DEV Community by Ez Eldeen M (@ezmu).</description>
    <link>https://dev.to/ezmu</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%2F3940345%2F9a00550c-a18a-4961-90f6-0f89da7fc736.png</url>
      <title>DEV Community: Ez Eldeen M</title>
      <link>https://dev.to/ezmu</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ezmu"/>
    <language>en</language>
    <item>
      <title>A Programmer’s Inferno — Circle Five:The Psychology of Distraction</title>
      <dc:creator>Ez Eldeen M</dc:creator>
      <pubDate>Tue, 19 May 2026 20:34:40 +0000</pubDate>
      <link>https://dev.to/ezmu/a-programmers-inferno-circle-fivethe-psychology-of-distraction-1jn1</link>
      <guid>https://dev.to/ezmu/a-programmers-inferno-circle-fivethe-psychology-of-distraction-1jn1</guid>
      <description>&lt;p&gt;14 years ago, I refused to build a fake progress bar for a Java Swing app.&lt;/p&gt;

&lt;p&gt;Or even just count the downloaded update files and call that "progress."&lt;/p&gt;

&lt;p&gt;It would have been easier. Faster. Less code.&lt;/p&gt;

&lt;p&gt;But I didn't.&lt;/p&gt;

&lt;p&gt;Because it felt wrong to deceive the user.&lt;/p&gt;

&lt;p&gt;Today?&lt;/p&gt;

&lt;p&gt;Skeleton loaders. Shimmer effects. Fake spinners.&lt;/p&gt;

&lt;p&gt;All "best practices." All "UX improvements."&lt;/p&gt;

&lt;p&gt;What I rejected for ethical reasons is now taught to beginners as "how to do it right."&lt;/p&gt;

&lt;p&gt;This isn't progress. This is rock bottom.&lt;/p&gt;

&lt;p&gt;📖 &lt;a href="https://medium.com/p/5f7cd1aa433e" rel="noopener noreferrer"&gt;A Programmer's Inferno — Circle Five: The Psychology of Distraction&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/@3z.eldeen/a-programmers-inferno-f90302a1ceea" rel="noopener noreferrer"&gt;A Programmer’s Inferno&lt;/a&gt;&lt;/p&gt;

</description>
      <category>performanceoptimization</category>
      <category>ethicsintech</category>
      <category>softwareengineering</category>
    </item>
    <item>
      <title>A Programmer’s Inferno: We Didn't Notice Software Rotting—Until It Was Too Late!</title>
      <dc:creator>Ez Eldeen M</dc:creator>
      <pubDate>Tue, 19 May 2026 14:01:43 +0000</pubDate>
      <link>https://dev.to/ezmu/a-programmers-inferno-we-didnt-notice-software-rotting-until-it-was-too-late-15e5</link>
      <guid>https://dev.to/ezmu/a-programmers-inferno-we-didnt-notice-software-rotting-until-it-was-too-late-15e5</guid>
      <description>&lt;p&gt;The software industry is in crisis, and we are responsible. We've traded architectural discipline for convenience, and engineering wisdom for bloat.&lt;/p&gt;

&lt;p&gt;My series, "&lt;strong&gt;A Programmer's Inferno,&lt;/strong&gt;" is a descent into the circles of hell that define modern development. Here is the catalog of the &lt;em&gt;first four circles&lt;/em&gt;:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Circle I: Architectural Collapse&lt;/strong&gt; – How we build massive frameworks to solve simple problems, ensuring our systems are broken from day one.&lt;br&gt;
Link: &lt;a href="https://medium.com/@3z.eldeen/a-programmers-inferno-circle-one-architectural-collapse-67272176deda" rel="noopener noreferrer"&gt;Architectural Collapse&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Circle II: Dependency Hell&lt;/strong&gt; – The culture that compels us to pull in thousands of unknown packages just to execute ten lines of code.&lt;br&gt;
Link: &lt;a href="https://medium.com/@3z.eldeen/a-programmers-inferno-circle-two-dependency-hell-50b38915ba64" rel="noopener noreferrer"&gt;Dependency Hell&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Circle III: The Docker Absurdity&lt;/strong&gt; – Masking software failures behind gigabytes of container overhead.&lt;br&gt;
Link: &lt;a href="https://medium.com/@3z.eldeen/circle-three-the-docker-absurdity-c6b63facb48f" rel="noopener noreferrer"&gt;The Docker Absurdity&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Circle IV: Cloud Conspiracy &amp;amp; Jevons Paradox&lt;/strong&gt; – Why the business model of cloud providers relies on our inefficiency.&lt;br&gt;
Link: &lt;a href="https://medium.com/@3z.eldeen/a-programmers-inferno-circle-four-cloud-conspiracy-jevons-paradox-acf8de4e4521" rel="noopener noreferrer"&gt;Cloud Conspiracy &amp;amp; Jevons Paradox&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This isn't just about slow code. It's about planetary energy consumption, digital waste, and the loss of professionalism in our craft.&lt;/p&gt;

&lt;p&gt;It's time to stop being "tool operators"—blindly assembling components we don't understand—and start being engineers again.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Circle Five: The Psychology of Distraction&lt;/em&gt; is coming next.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Which circle do you see most often in your daily work?&lt;/strong&gt; Drop your worst "bloat" story in the comments.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>softwareengineering</category>
      <category>softwaredevelopment</category>
      <category>cloudcomputing</category>
    </item>
  </channel>
</rss>
