TailwindCSS is the biggest jump in productivity for me in years.
I think where it shine most is when you are making your own UI and need to deploy different components/customizations, ie: If you are doing a single page site is not that obvious "why is like this?", but generating UIs on the fly for a admin backend and suddenly THIS IS THE WAY!.
TailwindCSS is like static types for UI. Note:
== fn sum(a,b)
== fn sum(a:U16,b:i32):Result
The "verbosed" nature of both cause some hate, but you will appreciate it the more big/complex the project is.
What you get with tailwind is exact understand of each component and how it will look based on their "types"/classes.
What you get with others like bootstrap is too abstract/implicit looks that you can't figure at a glance. So, tailwinCSS like static typed programming is optimized for "a glance"/local understanding.
What is also very counterintuitive is that my tailwind pages are LESS heavy than boostrap! (true for html and CSS)