Future of UX · 2026-07-08 · 22 min
A client of mine just rebuilt their entire Figma design system - roughly 700 components - as code components in Claude Code. It took one day. And now their designers prototype in code, while Figma has become the tool they open "when they occasionally need to design something." In this episode, I unpack what this story reveals about where our jobs are heading. The "should designers code?" debate is over - but we didn't end it. The job market did. And the way our roles are changing isn't arriving as a memo. It's arriving as convenience. In this episode: Why prototyping in the real system (instead of a Figma simulation) is a genuine qualitative leap - and why the design-to-dev handoff gap just disappeared The four quiet problems nobody talks about: fast isn't faithful, two sources of truth, the illusion of production-ready, and the question of where invention lives now Why role creep in 2026 doesn't come from your boss - it comes from your tools The one question that matters more than "should designers code?": are you building the mental model, or just orchestrating outputs?
#163 The Quarterly: My 24h Work week and What I'm Actually Working On (And What I Got Wrong)61 / 100
#160 AI Customer Research: Why Designers Should Learn Claude Code with Caitlin Sullivan63 / 100
#162 The Case of the Vanished Judgment#159 Beyond the Copilot: The 4 AI Patterns Every Designer Should Know#158 Why Junior Design Jobs Are Vanishing (And What To Do About It)