Why it worked
The video likely resonated with developers who have experienced a similar cognitive shift due to using utility-first CSS frameworks like Tailwind. The relatable struggle and the direct question at the end encourage engagement and sharing within the target audience.
Summary
The creator discusses how using Tailwind CSS for an extended period can rewire a developer's thinking, making them default to Tailwind syntax even when needing to write pure CSS. They admit to struggling to recall pure CSS properties like 'justify-center' after relying heavily on Tailwind.
Structure
- 1Introduction to the POV
- 2Struggle to recall pure CSS
- 3Explanation of Tailwind's impact on thinking
- 4Question about Tailwind's effect on developers
Product placement
Tailwind CSS: ACTS - it is a CSS framework that the creator uses to style web pages. The creator mentions they think in Tailwind first and translate it back to CSS. Removing it would change the creator's workflow and the topic of discussion. Tailwind CSS: APPEARS - mentioned in the on-screen text as the subject of the video. Removing it would not change what happens in the video.
On-screen text
POV : You've used tailwindcss
for too long
I actually
tailwindcs
Any of the two
i can work with
So what
So what's justify center in
Um, justify cen
um
well,