I was too subtle but the issue is less understanding CSS and more collaborating in a team where someone decides to add a specific rule that fixes something applies on every page but makes no sense semantically.

Then do that 100 times to create spaghetti. CSS rule anywhere can affect anything whereas tailwind is more local.

You can also bricklay it along lines of components in React, so you know how X component renders always and it wont look like a pig when tranplanted to the legacy billing screen.

I now recall why I like tailwind! Been backending for a while now (zero regrets lol)

The irony is that Tailwind is not semantic at all.