What taste actually means

1. The word

People say "taste" about engineers like it's mystical — they just have it. They don't. Taste is a specific, learnable skill, and naming it precisely is the first step to building it.

Taste is:

The ability to look at something and recognize, before it breaks, what's going to hurt you later.

That's it. No mysticism. A senior engineer reading your PR isn't seeing what you're seeing. They're seeing the future versions of your code — the one where you needed to add a feature and your design didn't accommodate it, the one where the abstraction had to be undone, the one where the on-call engineer at 2am couldn't read the function names.

That forward-vision is taste. And the thing that grows it is exposure to enough past failures that the patterns become legible at a glance.

2. Why taste is the bottleneck now

Here's the thing about taste. AI can write the code. AI cannot decide whether the code should be that shape.

That decision — what shape the code should be, what the abstraction should be, whether to write it at all — is where the value sits. Anyone with a keyboard and a model can produce working code. The question that distinguishes engineers from operators is whether the working code is the right working code.

That distinction is taste, and it doesn't come from typing more. It comes from reading more.

3. Three flavors of taste

When seniors talk about "the right shape," they usually mean one of three things, blended:

• Readability taste. Will the next person to open this file understand it in thirty seconds?
• Change taste. When the requirements shift (and they will), will this design bend or break?
• Boundary taste. Are the right things together and the right things apart? Is the seam where it should be?

You build each one by seeing many examples of code that has and lacks them. Not by reading more textbook examples — by reading real code under stress.

4. The next four pages

The rest of this chapter is the practical curriculum for building taste:

• How to read other people's code, on purpose.
• The vocabulary for things that feel wrong, so you can name them.
• The diff diet — why fifty real pull requests beats five tutorials.
• The disposition that drives all of the above.

This chapter is the most long-term thing in the course. Taste compounds slowest and matters most.