Interfaces Are Translations
Every screen is a sentence in someone else's first language.
[ essay ]
An interface translates the system’s native vocabulary into language the user already thinks in.
Internal models speak in IDs, enums, and database nouns. Users speak in tasks, outcomes, and anxiety. Every label, error, and empty state is a sentence in that translation — and most failures sound like the schema leaking through. When I rewired the mystic-bytes reading index, the breakthrough was not visual polish. It was replacing pipeline jargon with the question readers actually ask: “What should I read next?”
Bad interfaces teach your ontology. Good ones sound like a competent colleague. Great ones return the user’s intent with slightly clearer verbs and fewer surprises. They do not make the user learn your architecture to accomplish a task you already understand.
You are not obligated to expose your data model. You are obligated to make the next action obvious.
Translate before you decorate.
— JV · Dark Heart Labs.