// Issue #47 — May 2026
5 CSS tricks I keep going back to
Sent May 14, 2026 · 4 min read
Hey — Walt here. This week I was deep in a client codebase untangling a layout that had clearly been written by someone who had given up. It reminded me how many small CSS patterns I reach for constantly that I've never actually written down. So here they are. Five tricks, no fluff.
// This week's articles
01
The flex trick that kills most layout bugs
One line — min-width: 0 — and half your overflow problems go away. Here's why it works and when to reach for it.
02
Container queries: a real-world pattern
Forget breakpoints for component-level layout. Container queries let the component respond to its own space — not the viewport. Here's the pattern I've settled on.
03
Why I stopped using CSS resets entirely
Resets were a browser compatibility hack. In 2026, box-sizing: border-box and a handful of targeted rules is all you need.
04
CSS logical properties are worth the switch
margin-inline, padding-block — once you start writing direction-agnostic CSS, you won't go back.
// Quick tip from the trenches
If you're still reaching for parseInt() to convert strings in JavaScript — try the unary + operator instead. +"42" gives you 42. Shorter, faster, and it makes junior devs ask questions, which is always fun.
That's it for this week. If something was useful, forward it to a dev friend. If it wasn't — hit reply and tell me why. I read every response.
— Walt