> 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…
I'm confused. I often say of every genAI I've seen of all types that it is totally lacking in taste and only has skill. And it drastically raises your skill floor immediately, perhaps all the way up to your taste, closing the gap. Maybe that actually is what you were saying? But I'm confused because you used the opposite words.
Being too ambitious is a clever form of self-sabotage
121–130 of 221 posts
Re: Being too ambitious is a clever form of self-sabotage
#122Earlier quoted context omitted.
This is Rick Rubin pretty much. He has 100/100 in taste, but almost 0/100 in skill. He can't really play an instrument, but he knows exactly what works and what doesn't and can articulate it.
That’s an odd take for a massively successful person. In the realm of producing hip-hop, his taste and skill are at the top of the industry. Sort of like saying Bill Belichick has a skill gap because he’s not a top NFL player. AFAIK he never played pro ball at all (and college wasn’t at a top D1 program). Bit, he’s undeniably one of the most successful coaches in the business.
I pay a lot of attention to football as a hobby (and a gambling outlet) so these next two seasons at UNC for ‘ol Bill will be really telling.
Re: Being too ambitious is a clever form of self-sabotage
#123Earlier quoted context omitted.
I usually see the opposite. Detractors from AI often refuse to learn how to use it or argue that it doesn't do everything perfectly so you shouldn't use it. Proponents say it's the process and learning that builds depth and you have to learn how to use it well before you can have a sensible opinion about it. The same disconnect was in place for every major piece of technology, from mechanical weaving, to mechanical c…
> Detractors from AI often refuse to learn how to use it or argue that it doesn't do everything perfectly so you shouldn't use it. But here is the problem - to effectively learn the tool, you must learn to use. Not learning how to effectively AI and then complaining that the results are bad is building a straw-men and then burning it. But what I am giving away when using LLM is not skills, it's the ability to learn t…
Re: Being too ambitious is a clever form of self-sabotage
#124> 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…
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 s…
Re: Being too ambitious is a clever form of self-sabotage
#125Earlier quoted context omitted.
it rewards viral, vague behavior that only draws clicks but doesn't actually generate knowledge
Can you expound? I've heard about some controversy around them not moderating hateful content, which fair enough. But how does it reward anything if you're not engaging with anything outside of direct article links or newsletters you subscribe to? IMO your comment is not constructive unless you think the linked article is "viral vague behavior that only draws clicks"
Re: Being too ambitious is a clever form of self-sabotage
#126So project managers accomplish nothing?
Re: Being too ambitious is a clever form of self-sabotage
#127My parents once owned a photography studio. My stepfather often said something like, "A great photographer doesn't only take great photos; he takes many photos of various quality, and never shows anyone the bad ones."
Re: Being too ambitious is a clever form of self-sabotage
#128> The quality group only need to present one perfect photo.
> At semester's end, all the best photos came from the quantity group.
I think the more interesting experiment would be to give both groups the same assignment in terms of volume, but tell the quality group they had to submit N photos but designate one as their choice, to be graded on the quality of it. I think this would be interesting because my hypothesis is that people differ in what they consider "good" and the quality group would end up indicating the "wrong" photo as their choice nearly 100% of the time.
Re: Being too ambitious is a clever form of self-sabotage
#129And drinking to much water is also bad. We already know that too much of anything is bad and that virtue is in the middle. Please stop writing articles like this.
Re: Being too ambitious is a clever form of self-sabotage
#130Earlier quoted context omitted.
This is a radical misrepresentation of the dispute.
I disagree with you. Please expand.
The fact isn't that we don't know how to use AI. We've done so and the result can be very good sometimes (mostly because we know what's good and not). What's pushing us away from it is its unreliability. Our job is to automate some workflow (the business's and some of our owns') so that people can focus on the important matters and have the relevant information to make decisions.
The defect of LLM is that you have to monitor its whole output. It's like driving a car where the steering wheel loosely connected to the front wheels and the position for straight ahead varies all the time. Or in the case of agents, it's like sleeping in a plane and finding yourself in Russia instead of Chile. If you care about quality, the cognitive load is a lot. If you only care about moving forward (even if the path made is a circle or the direction is wrong), then I guess it's OK.
So we go for standard solutions where fixed problems stays fixed and the amount of issues is a downward slope (in a well managed codebase), not an oscillating wave that is centered around some positive value.