*This is part of my English preparation for upcoming global meetings, as a non-native English speaker.
Is Tailwind overrated?
🎥 Watch the original video here:
1. Note-Taking Practice
💡 Tailwind
- Wes: not a favorite approach, but certainly understand why so many people use it.
- Scott: appreciates that it provides a system for efficiency and consistency, but prefer other tools in terms of authoring experience.
- CJ: thinks it’s underrated because it isn’t just inline styles — it’s a full design system.
1inp-1means not ‘one pixel’ but a specific unit, and it’s the same acrossm-1,my-1, etc. Once you get that, design becomes more consistent. - CJ: open props can have different variable names for every type of thing (unlike Tailwind)
- Wes: Tailwind is a de facto standard in that every single project that uses Tailwind and the same scale. AI is very good at writing Tailwind
💡TypeScript
- CJ: TypeScript takes longer to write, and there’s a learning curve. Still it helps you to understand interfaces and let you expect what value it can have.
- Wes: beneficial for DX and preventing bugs. During migration from JS to TS, found so many edge cases.
- Scott: TypeScript saves a lot of time, except when fighting with crazy generic types from library code.
2. Vocab Building
💡authoring experience
- The experience of a developer while writing and working with code.
- e.g. an authoring experience on a library
💡DSL
- Domain Specific Language
- e.g. memorize all of the DSL around Tailwind
💡a de facto standard
- Something that is not officially or legally a standard, but is commonly used and widely accepted as if it were.
- e.g. benefits to Tailwind being a de facto standard
💡obtuse errors
- errors from the bundler that are confusing or unclear.
- e.g. I am so tired of these obtuse bundle errors that gives you no information
💡spin up
- to start or launch something quickly, especially in a tech/dev context — like starting a server, service, or container.
- e.g. I can spin up MySQL if I need it.
