←back to thread

757 points alihm | 2 comments | | HN request time: 0.418s | source
Show context
meander_water ◴[] No.44469163[source]
> the "taste-skill discrepancy." Your taste (your ability to recognize quality) develops faster than your skill (your ability to produce it). This creates what Ira Glass famously called "the gap," but I think of it as the thing that separates creators from consumers.

This resonated quite strongly with me. It puts into words something that I've been feeling when working with AI. If you're new to something and using AI for it, it automatically boosts the floor of your taste, but not your skill. And you end up never slowing down to make mistakes and learn, because you can just do it without friction.

replies(8): >>44469175 #>>44469439 #>>44469556 #>>44469609 #>>44470520 #>>44470531 #>>44470633 #>>44474386 #
nickelpro ◴[] No.44474386[source]
There's no meaningful taste-skill gap in programming because programming doesn't involve tacit skills. If you know what you're supposed to do, it is trivial to type that into a keyboard.

The taste-skill gap emerges when you intellectually recognize what a quality creation would be, but are physically unable to produce that creation, and judge the creations you are physically capable of producing as low quality

The oft cited example is drawing a circle. Everyone knows what a perfectly round circle looks like, but drawing one takes practice.

It doesn't take practice to type code. If you know what code you're supposed to write, you write it. The problem is all in the taste step, to know what code to write in the first place.

replies(2): >>44474500 #>>44474502 #
mjr00 ◴[] No.44474502[source]
> There's no meaningful taste-skill gap in programming because programming doesn't involve tacit skills. If you know what you're supposed to do, it is trivial to type that into a keyboard.

Strongly disagree here. The taste-skill gap still applies even when there's no mechanical skill involved. A lot of amateur music production is entirely "in the box" and the taste-skill gap very much exists, even though it's trivial to e.g. click a button to change a compressor's settings.

In programming, or more broadly application development, this manifests as crappy user interfaces or crappy APIs. Some developers may not notice or care, sure, but for many the feeling is, "this doesn't seem right, but I'm not exactly sure what's wrong or how to fix it." And that feeling is the taste-skill gap.

replies(2): >>44474958 #>>44480346 #
nickelpro ◴[] No.44480346[source]
If you know what sound you want to hear, but don't know the compressor settings to make that sound, that is a taste-skill gap.

If you don't know what sound you want to hear at all, that's undeveloped taste.

If you know what code you want to type, but don't know how to use a keyboard, that would be a taste-skill gap.

If you don't know what code you want to type at all, that's undeveloped taste.

replies(1): >>44487147 #
1. mjr00 ◴[] No.44487147[source]
> If you know what code you want to type, but don't know how to use a keyboard, that would be a taste-skill gap.

Ira Glass is a writer. Do you think he meant the taste-skill gap was when people couldn't physically write the words on the page they wanted?

replies(1): >>44490478 #
2. nickelpro ◴[] No.44490478[source]
I'm not Ira Glass, I have no idea what he meant. I would argue that taste-skill gap doesn't exist in writing either.

You either know what you want to write or you don't. If you hate the words you wrote, write something else. If you don't know what you want to write, that's undeveloped taste, not a gap preventing your from expressing your good taste.