Another update. Here’s an AI generated visual that communicates how the vois loop and router work to: 1. Qualify the design request. 2. Iterate on the design execution. 3. Validate the execution and review for content writing improvements. 4. Communicate key design decisions made based on human interaction guidelines and cognitive science principles. Human in the loop to add context when necessary and weigh in on tradeoffs.

The invisible tax of expertise The better you get at something, the easier you make it look, and people who can't tell what they're looking at will often decide it didn't take much. Years of practice get compressed into a result that feels obvious. A senior designer ships a screen that seems like it was always supposed to work that way. Behind it sit hundreds of small calls: what to cut, what to keep, which edge case deserves care and which one doesn't. None of those calls show up in the final screen. When they're done well, they disappear. I call this the invisibility tax. You pay it in years of work, and the better the result, the less credit it earns. Here's where it gets expensive for organizations. Some places can't tell two kinds of simple apart. One kind is simple because someone did the hard thinking. The other is simple because nobody did. On the surface they look identical. So the process meant to find your best people can quietly screen them out. The expert looks too smooth, too easy to justify. The person who shows a lot of visible struggle looks like value. Mediocrity doesn't just fail to produce excellence. It can actively reject excellence, because it doesn't know what excellence looks like. You get what you select for. Products get busier. Interfaces get heavier. Customers end up doing the work the team skipped. The obvious objection: every underappreciated expert says nobody recognizes their talent. How do you tell real mastery from a good act? Ask about the decisions. Someone with depth can tell you what they considered and threw out, and why. Someone without it can only describe what they made. "What did you leave out?" is a better interview question than "What did you build?" An organization's ceiling is set by what it can recognize. Imagine one that learns to look for the absence of clutter and asks who made it that clean. That team would hire people better than its current best, and the work would feel obvious to everyone who used it

Why is accessing Google APIs sooo painful?!

Republican candidate’s signposts exclude any mention of the party they represent, telling you everything you need to know about them.

Obamas energy this weekend

The most successful outcome for Figma Make would be for it to get completely cannibalized by code layers on the canvas.

Figma Make, Buzz, Figjam and Design would make more sense to live on the page level instead of a file level.