←back to thread

759 points alihm | 5 comments | | HN request time: 0.001s | 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 #
chatmasta ◴[] No.44469556[source]
This is exactly why I’m wary of ever attempting a developer-focused startup ever again.

What’s not mentioned is the utter frustration when you can see your own output is not up to your own expectations, but you can’t execute on any plan to resolve that discrepancy.

“I know what developers want, so I can build it for them” is a death knell proportionate to your own standards…

The most profitable business I built was something I hacked together in two weeks during college holiday break, when I barely knew how to code. There was no source control (I was googling “what is GitHub” at the time), it was my first time writing Python, I stored passwords in plaintext… but within a year it was generating $20k a month in revenue. It did eventually collapse under its own weight from technical debt, bugs and support cost… and I wasn’t equipped to solve those problems.

But meanwhile, as the years went on and I actually learned about quality, I lost the ability to ship because I gained the ability to recognize when it wasn’t ready… it’s not quite “perfectionism,” but it’s borne of the same pathology, of letting perfect be the enemy of good.

replies(4): >>44470028 #>>44470894 #>>44472540 #>>44473800 #
gsf_emergency_2 ◴[] No.44470028[source]
>letting perfect be the enemy of good.

My attempt to improve the cliche:

  Let skill be the enemy of taste
2 issues here. Neither can be developed (perfected?) in isolation, but they certainly ramp up at different rates. They should probably feed back into each other somehow, whether adversarially or not
replies(1): >>44470439 #
whatevertrevor ◴[] No.44470439[source]
The issue as the article points out is you can grow taste much much faster by only engaging in consumption, which leaves skill in the dirt.
replies(1): >>44470689 #
gsf_emergency_2 ◴[] No.44470689{3}[source]
I've heard that one way to pace is to... only consume your own stuff (aka dogfooding :)

More grown-up way to do it is to consume your mates' stuff?

(Trying to go from where TFA left off)

replies(1): >>44473380 #
1. the_af ◴[] No.44473380{4}[source]
I think you must consume (I hate that word, but let's go with it) elsewhere. Someone said (maybe Stephen King in "On Writing"?) in order to be a writer you must be voracious reader, and there's no escaping this. It rings true to me.

Of course the problem of taste growing much faster than skill remains, but I don't think the answer is to "consume" (yuck) less. I actually don't know if there's an answer.

replies(3): >>44474886 #>>44477997 #>>44481735 #
2. zambal ◴[] No.44474886[source]
I don't think it's actually a problem. Taste can guide the direction skill needs to go.
3. gsf_emergency_2 ◴[] No.44477997[source]
>yuck

Some alts to choose from: "use","utilize","imbibe","process","assimilate","experience"

4. jpc0 ◴[] No.44481735[source]
Something important is “consuming” critically.

You can be a passive consumer and never improve your taste or skill. However when you consume with the intent of asking how and then attempting to answer that question ( for skill ) and why ( for taste ) you get a much different experience.

Read code, looking for patterns. Look at design looking for patterns.

Then play, try to implement what you saw, implement to opposite and see how if feels, see what happens to the code.

This is a lot of work, but helps you improve.

replies(1): >>44485230 #
5. gsf_emergency_2 ◴[] No.44485230[source]
You've just suggested to me following optimization:

  Prioritize "consuming" your frenemies' stuff
Because one always has to pay full attention when doing that :)