This past week marked the start of WWDC25, Apple's yearly developer conference where they reveal new platforms, technologies, and (most relevant here) design languages. During the presentation they released their newest iteration, dubbed Liquid Glass. I have a lot of thoughts on this new language, but my immediate thought while I was watching the presentation was "I wonder if CSS can do that". It turns out, yes, with great effort, it can.

Many teams start with the MVP. But what if the key to shipping great products wasn’t starting small — but starting big? Could great products start at the finish line?

Programming-as-pop-culture is oppositional to the rigour required of engineering. When the folks talking loudest about "scale" and "high quality" and "delivery speed" (without metrics or measurement) continually plop out crappy experiences, but are given huge megaphones anyway, we need to collectively recalibrate.

All web developers know, at some level, that accessibility is important. But “eat your vegetables” is one of the least effective arguments in the world. So I would like to list some of my personal, completely selfish reasons for building accessible UIs. No finger-wagging here: just good old hardheaded self-interest!

Paradoxically, by privileging screen reader users with additional information, they no longer have access to the intended experience. Despite good intentions, severing parity has made the link less accessible.