the interface is the idea
Design isn't decoration. The way something works is inseparable from what it means.
We treat interfaces as wrappers — the skin stretched over logic that lives elsewhere. The "real" work is the backend, the algorithm, the data model. The interface is how you dress it up for users.
I think this is backwards.
The interface isn't a representation of an idea. It is the idea, made manifest. The choices you make about what to show, what to hide, what to make easy, what to make hard — these aren't aesthetic decisions. They're philosophical ones.
Consider a to-do app. You can implement the same "task management" concept in radically different ways: a simple linear list, a kanban board, a calendar view, an inbox with natural language input. Each one encodes a different theory of how work should flow, what completion means, how priority functions.
The interface doesn't express the idea. It is the idea.
This is why I find purely "functional" approaches to software unsatisfying. When you treat the interface as an afterthought — something to slap on at the end — you end up with products that are technically correct but conceptually incoherent. The seams show.
The best software I've used feels inevitable. Like the interface couldn't have been any other way, given what the thing is trying to do. That's not accident. That's design thinking that started at the concept level, not the component level.
The medium shapes the message. In software, the interface is the medium.