The first iterations of tailwind were really interesting. I took a lot of design system concepts from it. There are two problems with tailwind; 1) https://twit

The first iterations of tailwind were really interesting. I took a lot of design system concepts from it. There are two problems with tailwind; 1) https://twitter.com/dillonchanis/status/1706473840367247482/photo/1 https://twitter.com/dillonchanis/status/1706473840367247482/... and B) the tailwind fan boys. Every project of any decent size needs utility classes. No reason not to use tailwind for those. But every time I head that naming things is hard, I can't take that person seriously. You're not naming a baby. and if you change your mind on .pricing__card__header, just use your editors refactoring tools to rename it.