Code Quality on Coderrob

Fast Is Slow When You're Neck Deep in AI Slop

Fri, 10 Apr 2026 12:00:00 -0500

The Pattern Nobody Wants to Talk About

I’ve seen a distinct pattern where AI slows down software development.

I know. Heresy. But hear me out.

Agents are fast, but in the old saying kind of way:

Fast is slow, and slow is fast.

People push back on this. “Humans are faster,” they say.

Honestly? I doubt that’s true either.

What I believe is that most people are single-threaded. One brain, one task, one context.

Trust but Verify: The Math of Rigorous Software Development

Fri, 10 Apr 2026 10:00:00 -0500

Between Satire and Ridicule

It started, as these things often do, with a comparison nobody asked for.

I made a post saying that, with AI-assisted workflows, I can contribute anywhere from 20 to 300,000 lines of change in a day.

That number was not meant to say, “Look at me, I make ALL the tokens go brrrrrrrt…”

It was me counting additions plus deletions across real work: feature creation, refactoring, documentation, automation, test updates, generated assets, project scaffolding, cleanup, and the supporting files needed to make the work sustainable.

Announcing ESLint Zero-Tolerance AI Anti-Slop Rules

Tue, 10 Feb 2026 10:00:00 -0600

AI-assisted development has a trust problem.

Generated code can look polished, type-safe, and reviewable while still smuggling in shortcuts that quietly erode a codebase over time. The faster teams move with agents, the more those shortcuts compound.

ESLint Zero-Tolerance is my attempt to put hard boundaries around those patterns in TypeScript projects: not as abstract guidance, but as enforceable rules and presets that make low-trust code harder to ship.

The Announcement

I’ve published the ESLint Zero-Tolerance AI anti-slop rules here:

Breaking Up the Big Bottom Library: Streamlining Your Code for Long-Term Health

Wed, 11 Sep 2024 21:58:05 -0500

Over time, code libraries have a habit of expanding like that one “utility” drawer in your kitchen. At first, it’s helpful—everything in its right place, ready for use. But before long, that drawer becomes a catch-all for every stray function, random helper, and one-off module you couldn’t quite categorize. Eventually, it’s too bloated to find anything efficiently.

When that happens, it’s time to consider not just a cleanup, but a deeper restructuring. Because left unchecked, your code library could evolve into something far more dangerous—a monolith.

Clean Up Your Conditionals: Refactoring If-Else with Switch Statements

Sun, 18 Aug 2024 13:17:48 -0500

If you’re like me, you’ve probably dealt with your fair share of long, messy deeply nested if-else chains. They can get out of hand pretty fast, right?

One minute you’re making a simple decision, the next you’re wading through a maze of conditions and deeply nested logic. But guess what?

There’s a trick that can help clean this up: using switch and switch(true).

In this post, we’ll take a closer look at how you can use switch statements to break free from the chaos and make your code more readable, more maintainable, and without overloading to your brain juggling the contextual outcomes of each branching statement.