Frontend

One thing I changed my mind about in 2023 is tailwind CSS.

I started the year curious, but not convinced. 

Now I can't imagine working without it - particularly with shadcn.

Over the last 10 years I've gone thru: global CSS -> SASS -> BEM -> PostCSS  -> CSS in JS -> CSS Modules -> Inline styles (fuck it) -> Tailwind

Senior prompt engineer. Shipped on farcaster: @larrybot, @qdau, @frames, @framesfun, /open-frames, farcasterchannels.com, farcaster.id, @mod, @search, @discove

tailwind gives you the best of inline styles:
- code colocated by relatedness, not by language or part of stack
- no mental overhead/naming/referencing
- no jumping between files
- copy pastable

But with improvements:
- standardized values & systems
- more concise
- bundling & optimization
- lib composability

my gripe with TW is the mental translation required for things I already know how to do in CSS. Been using it for over a year and I still need to keep the docs site open for anything more complicated than flex layout.

I use it at work because of shadcn but only grudgingly

likes building things • https://alexgrover.me

Honestly it might just not be for you. Really just know flex, grid, p for padding, m for margin, colors from your theme, divide, and gap is like 95% of what I need

yeah me too - it is another convention to learn. I kinda wish their syntax was attribute:property-value but that has other downsides