Switched from inline styles to a CSS framework 2 years ago

I used to write all my styles directly in HTML tags for every project, even small ones like a simple contact page for my local library. After 3 sites turned into a mess of duplicate code, I started using Tailwind last spring and it cleaned everything up fast. The utility classes take some getting used to, but I spend way less time debugging layout issues now. Has anyone else made a similar switch and found it hard to go back?

3 comments

3 Comments

miller.paul9d ago

The whole inline vs framework thing reminds me of how people organize their kitchens. You see, some folks keep every spice in the original store containers scattered all over the counter. Works fine for a few meals but then you're digging through ten different bags just to find oregano. Then one day they buy a spice rack and suddenly everything has its place. That's exactly how I felt moving from inline styles to a proper system. It's not just about the code being cleaner, it's the mental peace of knowing exactly where to look when something breaks. Once your brain adapts to that kind of order, going back feels like cooking with your hands tied behind your back.

thompson.xena9d agoMost Upvoted

Wait, you actually had your spices in store containers scattered all over the counter before you organized them? That's insane, I thought everybody at least kept them in the same cabinet.

the_lee4d ago

Read something somewhere that people who keep their kitchens messy actually cook more because they're not afraid of messing things up. Sounds like nonsense to me honestly. I used to have my spices just tossed in a drawer and it drove me crazy every time I needed something. Got one of those tiered racks that sits in the cabinet and now I can see everything at once. Makes a bigger difference than you'd think.