The software industry is in crisis, and we are responsible. We've traded architectural discipline for convenience, and engineering wisdom for bloat.

My series, "A Programmer's Inferno," is a descent into the circles of hell that define modern development. Here is the catalog of the first four circles:

Circle I: Architectural Collapse – How we build massive frameworks to solve simple problems, ensuring our systems are broken from day one.
Link: Architectural Collapse

Circle II: Dependency Hell – The culture that compels us to pull in thousands of unknown packages just to execute ten lines of code.
Link: Dependency Hell

Circle III: The Docker Absurdity – Masking software failures behind gigabytes of container overhead.
Link: The Docker Absurdity

Circle IV: Cloud Conspiracy & Jevons Paradox – Why the business model of cloud providers relies on our inefficiency.
Link: Cloud Conspiracy & Jevons Paradox

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

It's time to stop being "tool operators"—blindly assembling components we don't understand—and start being engineers again.

Circle Five: The Psychology of Distraction is coming next.

Which circle do you see most often in your daily work? Drop your worst "bloat" story in the comments.