Product sense means predicting which product decisions will succeed based on patterns learned through experimentation — and knowing when those patterns apply.

Feed the machines the raw structured data they want on the backend, but don't let the order they require dictate your human design.

A running notebook of Rauno Freiberg's in-progress UI explorations. Raw sketches, dead ends, and iterations shown alongside the working version, unpolished by design.

About twenty-five years ago I stopped composing at the keyboard and switched over to fountain pen on paper.

CSS infinity solve some pretty specific problems elegantly, but can also just be plain fun to use.

If our design specs only tell models what the interface is made of, they have already forgotten what the interface is for.

Pablo Stanley has built as many creative tools as anyone in our industry. In this episode he gives us a behind-the-scenes of his latest creations .

The useful question is not whether the organisation should think fast or slow. It is whether this particular decision is genuinely reversible, what failure would actually cost, and whether anyone will come back to fix it if the bet does not pay off.

An open source library of tasteful html-in-canvas & WebGL components. Framework agnostic. Copy, paste, ship.

Tokens are the layer we can still control. And if we let go of the instinct to componentise every single surface of the product, we might actually be able to build faster, at greater scale, and stay just as consistent, maybe more.

Dropdown lists are one of the most familiar controls in forms, but that convenience comes at a cost: dropdowns hide available options behind a click, adding friction to every selection and slowing decision making.

Structure is everything, and it all starts with small units. The whole stack is really three concepts layered on top of each other: the loop, the harness, and the factory.

The durable AI habits will belong to the teams that keep the low effort and quietly repair the friction that moved.

The question to ask before creating any token is simple: will this value ever need to change independently of the property it's applied to?

Rather than thinking of a skill as a saved prompt the user or agent can retrieve as needed, think of a skill as a plugin: an extension of the harness.

Designers already have the mental model for all of this, in fact we've had it for decades.

We've reached a point where an idea becomes a prompt and a prompt becomes an app in the store in days. The finished result appears almost instantly, and nobody steps backwards through anything.

The one piece of career advice I'm giving everyone right now is to get a side project.

Screens should always be designed to pause the user so that they make a clear, conscious decision.

I think about it like — if you had to understand what a codebase is from the commit logs, that's kind of what we're doing with agent chats.

Craft isn’t perfectionism. Perfectionism is self-indulgent: it optimizes for the maker’s satisfaction. Craft is empathetic: it optimizes for the person on the other side. We’re not doing art. We’re designing for others.

Some see it as an invigorating return to what brought them to the discipline in the first place, from the joy of creating to finally being able to sweat the details that separate a mediocre product from a great one.

AI leverage becomes workplace pressure when every saved hour simply raises the output expected next time.

Shared-element transitions are useful because they preserve object identity across that break.