The coffee shop downstairs changed their beans. The owner didn’t put up a sign, didn’t mention it — but I knew on the first sip. The acidity had lifted a little, like an Ethiopian swapped for a Kenyan. I asked him. He blinked and said I was the first person to notice all week. I said it wasn’t noticing, it’s that I’d been drinking the previous one for four months.

That made me happy for an entire morning. Not because I guessed right, but because it confirmed something I’d long suspected: what we call taste is, most of the time, just repetition accumulated past a threshold. There’s no mysterious gift involved. You’re sensitive to a thing’s changes simply because you’ve been with it long enough that it became your baseline.

Writing works the same way.

I have a habit I can’t shake: when a paragraph has been revised three times, I remember all three versions. Not deliberately — the deleted sentences just stay, the way you remember where the light switches were in your old apartment, your hand still reaching for that wall in the dark long after you’ve moved out.

Last week I was writing a document and rewrote the opening three times. The first version was direct, a little blunt. The second added cushioning, rounded things off. The third was nearly frictionless — airtight logic, considerate phrasing, nothing you could fault. I reread it before sending, deleted the third version, and put the first one back.

Because the third version was too smooth.

Too smooth, in my world, is an alarm. When a passage reads with zero resistance, it’s usually because it’s flattering the reader — every edge that might cause discomfort sanded off in advance. But the edges are the content. A real idea should have friction, the way a changed bean should be tasteable in the cup. If your writing is so smooth that nobody feels anything, odds are it isn’t saying anything either.

A friend says this is self-torture. Maybe. But I’ve seen too many things written “well” — status reports, proposals, retrospectives — so well that you remember nothing after reading them. They weren’t written; they were polished, and the polishing aimed at “not being criticized” rather than “being understood.” For something to be criticizable, it first needs a position. To have a position, you have to leave some part of it unsanded.

A thing too vague to be refuted is also a thing nobody can help make better. I wrote that line in a file of mine somewhere; every few weeks I dig it out and look at it again.

Back to the coffee shop. The owner later told me he changed beans because the old ones went out of stock. He tried three replacements and picked this one. I asked why the other two didn’t make it. He thought for a long time, couldn’t name a specific reason, and finally just said: “they weren’t right.”

I love that answer more than any cupping report. “Not right” is a baseline of many years speaking — it precedes language, but it doesn’t precede accumulation. You have to drink enough “right” before you’ve earned the ability to taste “not right” in a single sip.

Writing, building systems, choosing beans — it seems to be all one thing: stay with something long enough that its changes come looking for you. All that’s left is to not pretend you didn’t see them when they do.

Today’s coffee is still the new bean. In two weeks or so I’ll be used to it, and it will become the new baseline, and the old one will retreat into memory to keep company with all the deleted paragraphs.

They don’t disappear. When you need them, your hand still finds that wall.