
My UX personas don't have stock photos (and that's why they work)
A persona with a made-up name and a stock-photo smile is report decoration. How I build personas that actually change a design decision.
Read note →Notes on development, design, and the decisions behind them.

A persona with a made-up name and a stock-photo smile is report decoration. How I build personas that actually change a design decision.
Read note →
There's a huge difference between building a product and keeping it running on a Tuesday at 3am when a payment webhook fails. What I learned taking GymSmartAccess from idea to a real business.
Read note →
Atomic design is easy to explain and often applied badly: components that are technically atomic but that nobody reuses because they were born coupled to a single screen.
Read note →
The question isn't which one is better. It's what needs interactivity and what doesn't, and that distinction changes how much JavaScript gets shipped to every visitor's browser.
Read note →
The framework you pick matters less than you think. The decisions that actually determine whether a product survives happen earlier, and they're business decisions, not architecture ones.
Read note →
Testing the structure before designing on top of it costs an afternoon and saves redesigning a menu twice. How to run one and how to read the numbers it returns.
Read note →
A badly written survey is worse than no survey: it hands you numbers that confirm what you already believed. The most common mistakes and how I avoid them.
Read note →
The five stages I work through before calling an interface finished, with real numbers from the redesign I did for Argentina's largest tech retailer.
Read note →
Designing and coding the same product changes the order of decisions. How I organize the path from a Figma file to real components, without the friction of two people passing a file back and forth.
Read note →