Forever watching people reinvent CSS classes for no reason. (I appreciate that this article actually does show doing it with classes, but it's still grating to me that these "frameworks" just keep reinventing style="...")

The eternal pendulum swinging between BEM and atomic css forever. The best is to start with atomic and then extract a few BEM use cases as duplication emerges. Then you've got the best of both worlds.

Roughly half of css is extremely specific to one place and not worth extracting. The remainder though is actually important to the design system and is worth deduplicating and formalizing into BEM / variants. The trouble is when you try to BEM everything and end up with thousands of classes that are only used once.

Tailwind class soup is something I see often in LLM-generated code. For some reason, every starter template in existence decided to include Tailwind, and then the coworker generating this code (who doesn't have frontend experience at all) just rolls with whatever the LLM shits out.

I believe there's a proper way to use Tailwind, but I can't be bothered to read the docs for it. It makes far more sense to me to either use plain CSS or, if I'm using a component library, then whatever that library comes with for its theming system.

Also, this whole article basically boils down to "use a proper theming system", which it even admits can be as simple as some CSS classes with standardized names.