Aug 25, 2026

You against you a year ago

You aren't born with an eye. It's built from reps and a lot of being wrong.

Jacob Collado
Jacob Collado
Founder, Inertia

People talk about taste like you're born with it. Either you've got an eye or you don't, and everyone quietly sorts themselves into one pile or the other.

I don't buy it. Mostly because I didn't have one. I started with no design background and no real clue what I was looking at. What I had was volume, repetition, and enough time to start noticing patterns.

Beyond what you'd pick yourself

Taste isn't preference. Preference is what you like. Taste is clocking what's working even when you'd never choose it yourself.

Which is what makes it testable, and worth arguing about. A trained eye looks at two versions and says which one's better and why, and is right in a way that survives contact with other people. Skill, not opinion.

Usually it shows up as instant recognition. Someone glances at a layout, knows something's off, can't explain it yet. Looks innate from outside. It isn't. It's compression. A few hundred past judgments collapsing into one fast reaction that feels like a hunch.

Looking isn't studying

Scrolling through good work trains nothing. You've seen thousands of well-designed things this year. Has it made you better? Looking is passive.

The version that works is slower and, honestly, a bit of a grind. You find something good, and you don't let yourself move on until you can say why. Which decision is carrying it? What breaks if you swap the type? Why does that spacing feel deliberate instead of accidental?

You'll get the reason wrong most of the time. Fine, genuinely. Being wrong out loud is what sharpens the next read. Being vaguely impressed does nothing at all.

Good work hides its reasons

Good design shows you what success looks like. What caused it? Rarely. In finished work every decision looks inevitable, which is exactly what makes it useless to study.

Broken work is legible. When something feels cheap you can usually put a finger on why. Inconsistent spacing. Too many type sizes. A hierarchy at war with itself. Four greys where one would have done. The failure is visible in a way success never is.

Pick apart one bad page and you'll learn more than admiring ten good ones.

Ship it somewhere you can't control

None of this replaces making things. Build it, ship it, watch it live somewhere you don't control the context, the browser, or the person's mood.

Then something you were proud of looks amateur three months later. That gap is the actual signal. Your eye moved faster than your last project did, which is about the only proof of progress anyone hands you.

Look back at work from a year ago and still think it's great? Bad sign.

Years, mostly spent wrong

Years. It takes years, no matter how clever you are about it, and there's no skipping the part where you're wrong repeatedly and only find out much later.

Taste shows up years before the ability to meet it. The gap closes through reps, not insight.

The only comparison worth making is you against you a year ago. Measuring yourself against someone ten years in isn't a motivation problem, it's a category error.

Encouraging part: it's learnable at all. Nobody has an eye at the start. Everyone who has one built it, usually while quietly assuming everyone else got theirs for free.