Design as a second language

When you learn a language as an adult there is a specific frustration that children are spared: you know what you want to say, but you do not have the words. You have the thought fully formed, and it dissolves at the point of articulation.

That is exactly what learning design felt like coming from code. I could look at a good interface and understand it, intellectually and structurally. I could feel what was working. I just could not make it myself. The gap between what I could perceive and what I could produce was humbling.

The breakthrough came when I stopped trying to learn design and started trying to learn to see. The design came after. First I had to understand why things looked the way they looked. Why that particular grey felt off. Why that button placement felt wrong. Why that much whitespace felt generous rather than empty.

Code taught me that systems have logic. They follow rules, and the rules are discoverable. Design has the same quality. The rules are less explicit but equally real. Once you start to feel them, you start to use them. And then you start to break them on purpose.

The thing that made it click: an electrical schematic is one of the most carefully designed objects in the world. Not beautiful in the conventional sense, but every line, every symbol, every annotation is there for a reason. Nothing is arbitrary. Every convention serves legibility. That is design.

I was already a designer. I just had not known what to call it.