It’s conversational style of explaining the common use design patterns makes it easier to understand and more fun to read.
Design pattern is one of the “soft skill” that developer should add to their experience. One might never use them depending on their work requirement, but having these design pattern concept in their mind will help developing better softwares.
Once you finish reading this book, I believe, it’s easier to move on to the GoF Design Pattern book.
TLDR; I just did a project using Tailwind CSS. It’s as good as it advertised.
I came from working with Bootstrap for a long time. It has been my go to HTML/CSS framework. I can quickly build a good business looking website quickly with Bootstrap.
I just had a small project that I needed to work on. It’s not difficult so I got to spend sometimes on it using Tailwind.
At first, since coming from Bootstrap, there’s some initial learning curve needed to overcome with. Once I got it setup and running, I see the benefit of using a Utility First Framework approach to develop the front-end. It’s quick, easy to customize, and importantly, easy to read. (We spend 10 times more to read code than writing code, maybe 20 times more to read HTML/CSS more than writing HTML/CSS code ).
It’s good to have more tools to tackle problems and I think both Bootstrap and Tailwind are good tools to have in the toolbox.