Taste Is Not a Preference

Ask someone why they like a piece of music, a room, a piece of writing, and the honest answer is often just: I don't know, I just do. That response gets treated as the end of the conversation, as though taste were simply an unexamined reaction, arbitrary and personal, not worth investigating further. It's the wrong place to stop.

A preference is immediate and largely unreasoned. It doesn't require any particular history or exposure. Someone can prefer one color over another the first time they see them side by side, with no context and no comparison. Preferences are real, but they're also shallow, in the literal sense that there isn't much underneath them.

Taste is different. Taste is what develops after someone has looked at, listened to, or made a large enough volume of things in a category that they start to notice what separates the work that holds up from the work that doesn't. It isn't immediate. It's built through repetition and comparison, the same way a palate develops after tasting hundreds of variations of something, or an editor's eye develops after reading thousands of manuscripts. The person with trained taste isn't reacting instinctively in the way the person with a mere preference is. They're recognizing something specific: proportion, restraint, coherence between a thing's parts and its stated intention, the presence or absence of an unearned shortcut.

This distinction matters because it changes what taste is actually good for. A preference tells you what one person happens to like. Trained taste tells you something closer to why a piece of work is succeeding or failing on its own terms, regardless of whether it happens to match anyone's personal preference. A person with genuine taste can recognize when something is well made in a style they personally dislike, and can recognize when something is poorly made in a style they personally love. That capacity, holding judgment and personal preference apart from each other, is the actual skill.

It would be a mistake, though, to push this argument too far in the other direction and claim that taste is objective in the way a measurement is objective. There is no instrument that outputs a taste score. Trained judgment still varies across people, cultures, and periods, and plenty of things once dismissed by expert consensus have been reevaluated later, sometimes because the consensus was wrong, sometimes because the culture around the work changed. What's being claimed here is narrower and more defensible: that taste can be cultivated, that cultivated taste sees things preference alone cannot, and that the difference between the two is worth taking seriously, not that there exists one correct, permanent standard that trained taste is measuring against.

This is also why taste can't be manufactured on demand, in the way a brand guideline or a style sheet can. It has to be built, slowly, through the unglamorous work of looking closely and often, and comparing what's in front of you against everything else you've already seen.

That slowness used to be a minor inconvenience, easy to overlook when output itself was the harder thing to come by. It is starting to look more like the whole advantage. Producing something has never been easier or faster, and a reasonable baseline of competence, the kind that once took years to reach, is now close to a default setting. None of that touches taste, because taste was never a measure of how much could be made or how quickly. It's the separate, older skill of knowing, once a thing exists, whether it's actually worth keeping. As the volume of what can be made keeps climbing, that skill only becomes harder to fake and more necessary to have.