Fair, the author's point would have been stronger if the page was made using just static HTML/CSS.
But I have to defend Tailwind, it's not a massive CSS framework, it just generates CSS utility classes. Only the utility classes you use end up in the output CSS.
If you stick to a few useful types like `Option` and `Either`/`TaskEither` you can get a lot of value out of it when writing server side code, particularly when combined with `io-ts` for safely parsing data.
If you go all in and use every utility it provides to write super succint FP code, it can get pretty unreadable.
+1 for Clockwise, it does a great job of automating this. It easily doubled my team's work time ("focus time" in Clockwise).
It also has useful preferences like "prefer morning/afternoon", "no meeting days", which it takes into account when scheduling.
I can't say enough good things about it. It's free at first but I would pay almost any money to keep it, the value of the extra time it gives you is enormous.
http://gitimmersion.com/ - This is a lab taking you through everything. I found it very helpful when introducing Git to my team mates who had little to no experience with source control.
It's a bit light on concepts but is fairly practical.
It’s short term thinking IMO, but it’s my interpretation of the argument AI proponents are making.