Phil is Principal Developer Experience Engineer at Netlify.
With a passion for browser technologies, and the empowering properties of the web, he loves seeking out ingenuity and simplicity, especially in places where over-engineering is common.
After more than 20 years of building web applications for companies such as Google, Apple, Nike, R/GA, and The London Stock Exchange, Phil has worked to challenge traditional technical architectures in favour of simplicity and effectiveness.
Phil is co-author of “Modern Web Development on the JAMstack” (O’Reilly, 2019)
Utility-first CSS: Can it un-muddle my code, my head, and my life?
Keeping your CSS efficient and organized can be a challenge. There are many popular approaches out there it help architect your CSS so that it can remain usable as your projects grow. None of them have really suited me. My best intentions have always given way to shortcuts, compromises and dark patterns. I'm the worst. But I suspect I'm not totally alone.
Lately, another approach has emerged called utility-first CSS. Spearheaded by CSS frameworks such as TailwindCSS and Tachyons, they provide predefined utility classes which you can use right away. I was skeptical, but some experimentation and an open mind has made me a fan. Let me tell you why.