Why I Still Prefer SCSS Over Utility-First CSS

Structure, clarity and team conventions still matter.

Utility classes can be productive, but I still value styles that express a component's intent and keep implementation details in one place. SCSS gives my teams a familiar structure without requiring every template to double as a detailed account of its visual decisions.

CSS rewards people who understand its model more than people who accumulate workarounds. The cascade, intrinsic sizing and modern layout tools solve a surprising number of problems once we stop fighting them.

The answer is rarely a universal rule. It is a way of looking at the decision clearly enough to choose on purpose.

Prefer the thing that survives contact

Front-end work has a habit of looking simple from a distance. The browser then introduces real content, small screens, old devices, keyboard navigation and somebody using the product in a way nobody drew in the design file.

That is why I favour choices that are easy to inspect. Start with semantic HTML, let CSS do the layout work it was designed for, and add JavaScript where it creates genuine value. Cleverness is occasionally useful; legibility is useful every day.

The best front-end code does not show off. It makes the interface feel obvious.

The web is wonderfully forgiving, but users should not have to rely on that forgiveness. Build from sturdy foundations and the interesting parts become much easier to enjoy.

I do not always manage it perfectly. The aim is to make the better choice easier to recognise the next time it appears.