LWP::ConsoleLogger::Everywhere lets you debug LWP and Mojo UserAgents you don't even know about. Now we also have support for HTTP::Tiny.

You can either add UserAgent debugging to your code directly or, through the magic of perl’s -M you can invoke it on the command line without touching a single line of code.

The guts of this module are stolen from Plack::Middleware::DebugLogging,

Despite broad browser support, container queries remain surprisingly underused and frequently misunderstood.

A very interesting way to distinguish @media and @container queries is the layout type.

Media queries are for the “macro” layout; they look outward. Stuff like page structure, the header that spans the window, footers, main grid layout, system preferences (prefers-color-scheme), device capabilities (touch screens). You know, anything that is majorly true to the entire page structure.

Container queries, I’d say, are for “micro” layouts, i.e., most things that live inside the “macro” layout. We use them when any content needs to responsively fit whatever space it is allocated. Components that come to mind are things like cards, widgets, forms, navigation, and so on.

In other words, think “page layout” vs. “component layout”.

AI is not a substitute for divergent thinking, and the false certainty it gives will never save you from having to iterate.

Just like an airplane’s time on the runway is still part of the flight, discovery is part of design and must give creative work momentum and direction.

The Waterfall way of “big design up front” is implied to be practiced by some other people, outside the room. Inside the room are only innovators, who are above that kind of thing.

To the people in charge of calendars, there is nothing more alluring than the idea that you can simply know the right thing to do up front, and then do that thing exactly once, never having to budget time for testing or rework.

Modern CSS features that replace Sass, PostCSS plugins and JavaScript hacks: nesting, :has(), container queries, subgrid and more, checked in September 2026.

Big stylesheets used to get their order from a folder structure and a build tool. Reset first, then base styles, then components, then utilities, plus a rule that nobody adds !important before the third code review.

@layer writes that order into the CSS itself:

A rule in a later layer beats any rule in an earlier layer, whatever its specificity. .p-0 wins over .card .button because utilities comes after components, and the order of the files no longer matters.

wallhop is a free paywall bypass. Paste any article link to read it without paywall popups, ads or clutter. No signup, no extension. A simple 12ft.io alternative.