Your SPA Is Leaking Memory. Soak Test It
Some teams force-reload their single-page web apps (SPAs) every few hours just to clear the memory the app leaked. A frontend soak test finds the leak instead.
Thoughts on building fast, accessible, and resilient web apps — drawn from years of real-world experience, a couple of books, and a lot of hard lessons. Expect deep dives, practical tips, a bit of history, and the occasional opinionated take on where the web is going.
Some teams force-reload their single-page web apps (SPAs) every few hours just to clear the memory the app leaked. A frontend soak test finds the leak instead.
Thousands of AI agent skills have flooded GitHub recently, most of them teaching models what they already know. The land grab is on.
Safari and Firefox change how big sites render based on the domain. TikTok, Netflix, Instagram… even SeatGuru. Chrome doesn’t. Why is that?
Designers have been complaining for decades that what ships doesn’t match what they designed. The fix isn’t better handoffs or AI tools. It’s engineers who can see what designers see.
Pretext went viral for its beautiful canvas demos. But the community is showcasing the wrong feature.
How working within hard limits produced some of the most elegant software in history, and what we can learn from it.
You don’t need more performance heroes on your engineering team. Make the fast path the easy path.
Every millisecond your JavaScript runs is a millisecond borrowed from your users. Here's how to be a better guest on the main thread.
After a decade of React dominance, it’s time to remember that frameworks run inside the web, not the other way around.
Make your dynamic content accessible by default with the HTML tag that time forgot.
Most frontend reviews sign off clean code. But your users don’t see the code, they see the bugs you missed.
We keep changing how we style the web, but the real problem isn’t CSS. It’s how we build around it.
What happens when accessibility stops being a best practice and starts being the law? We’re about to find out.
Apparently, frontend developers are about to be made obsolete. This all sounds very familiar.
Loading spinners. Hydration delays. 300kB for a blog post. There’s a better way to build the web.
The early web had no layout system. No CSS. So we improvised, slicing, stretching, and nesting our way to structure.
You’re going to hate me for saying this, but I actually like being on-call. Honestly! It’s taught me more about frontend quality than any bug tracker ever did.