There was a time when I'd open a blank .html file, sketch out a <div> skeleton, and start hand-placing every margin and flexbox rule like it was a craft I was proud of. I'm not doing that anymore. Not "trying to do less of it" I mean I genuinely cannot remember the last time I manually wrote a stylesheet from scratch, and I don't expect that to change.
Here's why.
The bottleneck moved. When I'm building something whether it's a POS dashboard, a fiscal-compliance tool, or some side project ,the part of the work that actually needs me is the logic: the data model, the API contract, the edge cases around tax rules or inventory state. Markup and styling are the most mechanical, most spec-able, most pattern-matched part of the entire stack. That's exactly the kind of work that's cheap to describe and expensive to hand-type. Once I noticed that, hand-writing CSS started to feel like manually computing a checksum instead of calling a library function.
Describing a UI is faster than building one. "Card layout, three-column on desktop collapsing to a stack on mobile, subtle shadow, brand color as the accent" takes me ten seconds to say and gets me 90% of the way to something usable. Getting that same result by hand means flexbox debugging, browser quirks, remembering whether it's justify-content or align-items this time, and then doing it all again for the responsive breakpoints. The gap between "describe it" and "type it all out" is just too large to ignore once you've felt how small it can be.
CSS was never the interesting problem. I like solving problems where there's a right answer buried in ambiguity — reconciling ledgers, handling fiscal-integration quirks, making sure a transaction is atomic even when the network isn't. Centering a div, fighting specificity wars, or figuring out why a flexbox gap isn't applying in Safari never scratched that itch. It was always overhead standing between me and the part of the job I actually cared about.
Review is a different skill than authorship, and I've gotten good at review. People assume "not writing CSS" means "not knowing CSS" or "not caring about the output." That's backwards. I still care enormously about whether the UI is accessible, coherent, and fast I just exercise that care by reading and correcting generated output rather than typing it character by character. Knowing what good CSS looks like is what lets me catch when a generated layout is subtly wrong. The skill didn't disappear, it moved up a layer.
Why I don't think I'll go back. This isn't a phase I expect to snap out of once the novelty wears off, because the underlying trade only gets more lopsided over time — the tools generating and refining frontend code keep getting better, while the argument for hand-authoring markup mostly rested on "it's the only reliable way to get it right," and that premise is the part that's eroding fastest. Short of some new frontend paradigm that makes hand-written HTML/CSS meaningfully more expressive than describing intent and reviewing the result, I don't see the case for going back.
I still respect the craft. Some of the best interfaces I've used were clearly the product of someone who cared about every pixel by hand. But that's not where my hours are best spent, and I've made peace with that.