As a backend developer working on my first small site, I'm curious about the CSS writing process. CSS, especially with frameworks like Tailwind, seems incredibly verbose to me. I wonder if most developers just rely on templates or boilerplates rather than writing everything from scratch. What does your workflow look like? Do you start with a blank CSS file and write out everything by hand, or do you typically use pre-existing templates and modify them?
5 Answers
I'm not a fan of LLM-generated CSS—it's often clunky and requires too much refactoring. I prefer starting with minimal boilerplate and building up from there. It gives me better control, and setting it all up myself feels more rewarding. Plus, with the advances in CSS (like variables and nesting), writing hand-crafted styles has become much more enjoyable!
Right?! Relying on AI for this stuff isn't practical—there's so much creativity involved in real coding!
Absolutely, many developers still write CSS by hand! I usually kick off with a reset CSS, then import my variables and fonts, followed by my utility classes and styles for components. It's all about keeping styles scoped to avoid clashes. I find that CSS nesting makes my workflow cleaner too. Although, I'll admit that Tailwind's verbosity can be a bit of a pain; I prefer raw CSS whenever possible. And yes, designers can sometimes complicate things with their pixel-perfect expectations!
This is spot on! Also, you're not alone in being fed up with designers' high-res mockups. They expect so much perfection! It's a funny struggle we all share.
I totally get that! The push for pixel perfection from designers can be frustrating. It's nice to know I'm not the only one who's had to wrestle with that.
Writing CSS by hand is still common, especially for smaller projects. It's not as tedious as people think; once you know the basics, you can create quite a lot without relying on frameworks. I often have a base stylesheet to start from and keep a set of utility classes I reuse across projects. Tailwind can simplify some things, but I find writing tailored CSS gives better control and results.
Exactly! Reusing classes helps keep things manageable without bloating the CSS. Tailwind might be great, but I prefer clean, concise styles.
Yes! The satisfaction of crafting your own clean CSS is hard to beat. There's creativity in it that you just don't get with frameworks.
I find that most developers like to mix and match. It really depends on the project scope. For simpler sites, you can start with utility classes, but when you need customization, hand-coding CSS becomes necessary. LLMs can help, but they often miss the mark on nuance. At the end of the day, writing CSS by hand can be enjoyable and helps deepen your understanding of styles.
So true! It's all about finding that balance where you can leverage quality tools while still enjoying the craft of coding.
Right? There's a fun challenge in writing it by hand, especially with the new features like nesting! It keeps it interesting.
Using frameworks and libraries like Tailwind or Material UI is super common now. They minimize the need for writing CSS from scratch while still allowing some customization. However, I still find myself writing custom CSS for specific needs, especially when dealing with unique designs. The balance is key!
100%! A combination of both methods works best. Utilize frameworks for speed, but never shy away from custom hand-written styles!
Yeah, I think a lot of developers appreciate the efficiency that frameworks offer, but there's still nothing like the freedom of hand-coding.
Totally! Modern CSS has made things so much easier and more fun to work with. LLMs just can't keep up with that kind of nuance.