Look, we’ve all written garbage. But some patterns are so bad, so cursed, they deserve their own prison cell inside a Git repo from hell.
Here are the top frontend sins that not only break your UI, but also break the souls of anyone who tries to maintain your code. These are the **anti-patterns that keep me up at night**. And if you’re doing any of these — stop it. Or refactor while I cry in the background.
The CSS equivalent of screaming louder because your argument sucks. If your only fix is !important, your selector is trash and your architecture is a spaghetti-fueled disaster.
We get it, you're in a rush. But dumping style attributes in your HTML like it’s 2003? No. Separate your concerns. Respect your future self.
One level? Cool. Two levels? Risky. Five levels? Welcome to selector purgatory where every hover breaks and nothing works without !important.
Don’t use JavaScript to calculate layout positioning unless you’re building a physics engine. CSS exists. Flexbox exists. Grid exists. Stop reinventing broken wheels.
Putting every variable, class, and style in global scope is like pooping in the swimming pool. It affects everyone, and someone has to clean it up.
Yes, transitions are cool. But animating every hover, scroll, focus, and click like it’s a music video from 2005 is just... chaos. Motion fatigue is real.
If your site looks amazing on 27” screens but breaks into a war crime on iPhone SE... you're not responsive, you're just irresponsible.
ID selectors should be used for anchors, JavaScript hooks, or evil. But not styling. Never styling. Class-based systems exist for a reason — use them.
If you've done these things, we forgive you — barely. But today’s the day you stop. No more !important crutches. No more 400-line stylesheets with names like final-final-V3.css.
Write styles your future self will thank you for. Write code that gets nods from other devs. Write like a Web Runner.
— The Web Runners
We see your codebase. We judge it. And we refactor without mercy.
