Do designers need to code? Wrong question.

Every few months this debate resurfaces, usually as a LinkedIn hot take or a quiet anxiety in a design team Slack. After a few years designing with one hand in Figma and the other occasionally in VS Code, I've stopped trying to answer it directly. Because the question isn't really about code. It's about curiosity.

When I started out, design and development felt like two separate worlds. Designers dreamed things up, engineers made them real. Over time, especially working on more complex data products where the UI and the underlying system are deeply intertwined, that clean separation started to feel less useful. More like a gap than a boundary.

Understanding how components behave, how states change, and how data flows doesn't make you less of a designer. It makes you a more useful one. Not because you can ship production code, but because you stop designing in screenshots. You start designing in flow, thinking about interactions, constraints, edge cases, and what happens when something goes wrong. That changes what you put in your Figma files.

The practical version of this isn't "learn React." It's being comfortable opening a text editor, tweaking some CSS, or understanding why a "simple animation" might take half a sprint. It's being able to look at a code review and understand roughly what changed. It's speaking enough of the same language as engineers that a handoff becomes a conversation rather than a delivery.

For me, it's never been about being a unicorn. It's about not designing things that fall apart the moment they meet a real codebase. That curiosity, the drive to understand how things actually work, is one of the most useful things you can bring to a team.