> 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.
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.
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
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.
After sleeping on it and reading some replies I think I worked out what they were saying. Take drawing - your skill at producing an image is raised to a professional aesthetic (what I was saying) but your skill at drawing is unchanged (what they are saying).
But they're saying your taste, in the context of self-judgment at attempting to learn to draw, might also be raised to a professional aesthetic, because you can already produce images of that level by typing words.
I guess I will add that a difference here is we are talking about taste somewhat differently. To me, genai has been a demonstration that taste and skill are not two points on the same dimension.
The gap will open itself back up again. If you can do anything in 10 seconds with a GenAI, it won't be long until 1,000,000 people have all done it and it's considered poor taste...
Closing the gap? I think we're inverting the gap: Many people now have access to a higher skill level than they've developed taste for (if they ever did), which makes them unable to judge their own slop.
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.
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 computing, to motorized carriages, to synthesized music. You can go back and read the articles written about these technologies and they're nearly identical to what the AI detractors have been saying.
One side always says you're giving away important skills and the new technology produces inferior work. They try to frame it in moral terms. But at heart the objections are about the fear of one's skills becoming economically obsolete.
> It's interesting seeing people argue about AI, because they're plainly not speaking about the same issue and simply talking past each other.
It's important to realize this is actually a general truth of humans arguing. Sometimes people do disagree about the facts on the ground and what is actually true versus what is bullshit, but a lot of the time what really happens is people completely agree on the facts and even most of the implications of the facts but completely disagree on how to frame them. Doesn't even have to be Internet arguments. A lot of hot-button political topics have always been like this, too.
It's easy to dismiss people's arguments as being irrelevant, but I think there's room to say that if you were to interrogate their worldview in detail you might find that they have coherent reasoning behind why it is relevant from their perspective, even if you disagree.
Though it hasn't really improved my ability to argue or even not argue (perhaps more important), I've definitely noticed this in myself when introspecting, and it definitely makes me think more about why I feel driven to argue, what good it is, and how to do it better.
>It's interesting seeing people argue about AI, because they're plainly not speaking about the same issue and simply talking past each other.
There's actually some ground truth facts about AI many people are not knowledgeable about.
Many people believe we understand in totality how LLMs work. The absolute truth of this is that we overall we do NOT understand how LLMs work AT all.
The mistaken belief that we understand LLMs is the driver behind most of the arguments. People think we understand LLMs and that we Understand that the output of LLMs is just stochastic parroting, when the truth is We Do Not understand Why or How an LLM produced a specific response for a specific prompt.
Whether the process of an LLM producing a response resembles anything close to sentience or consciousness, we actually do not know because we aren't even sure about the definitions of those words, Nor do we understand how an LLM works.
This erroneous belief is so pervasive amongst people that I'm positive I'll get extremely confident responses declaring me wrong.
These debates are not the result of people talking past each other. It's because a large segment of people on HN literally are Misinformed about LLMs.
This is not what Ira Glass meant by taste gap. What he rather means is that taste is important. It’s what gets you into the field and what makes you stick around. Happy to be corrected on this.
yes that was the gist of Ira Glass's quote, but he also added to it that it makes you feel frustrated when you have taste but are not creating things that live up to that taste, but that as a young artist you should push through that.
Here is a copy paste of the quote:
“Nobody tells this to people who are beginners, I wish someone told me. All of us who do creative work, we get into it because we have good taste. But there is this gap. For the first couple years you make stuff, it’s just not that good. It’s trying to be good, it has potential, but it’s not. But your taste, the thing that got you into the game, is still killer. And your taste is why your work disappoints you. A lot of people never get past this phase, they quit. Most people I know who do interesting, creative work went through years of this. We know our work doesn’t have this special thing that we want it to have. We all go through this. And if you are just starting out or you are still in this phase, you gotta know its normal and the most important thing you can do is do a lot of work. Put yourself on a deadline so that every week you will finish one story. It is only by going through a volume of work that you will close that gap, and your work will be as good as your ambitions. And I took longer to figure out how to do this than anyone I’ve ever met. It’s gonna take awhile. It’s normal to take awhile. You’ve just gotta fight your way through.”
― Ira Glass
I don't know much about Ira Glass and I'm not going to be a 5 minute wikipedia expert about it, so maybe I'm missing out on very relevant philosophy (I hope someone links the must read thing), but those would be very intentionally inverted meanings of the taste/skill dichotomy.
LLMs are good at things with a lot of quantity in the training set, you can signal boost stuff, but its not perfect (and its non-obvious that you want rare/special/advanced stuff to be the sweet spot as a vendor, that's a small part of your TAM by construction).
This has all kinds of interesting tells, for example Claude is better at Bazel than Gemini is, which is kind of extreme given Google has infinite perfect Bazel and Anthropic has open source (really bad) Bazel, so you know Gemini hasn't gotten the google4 pipeline decontamination thing dialed in.
All else equal you expect a homogenizing effect where over time everything is like NextJS, Golang, and Docker.
There are outlier events, like how Claude got trained on nixpkgs in a serious way recently, but idk, maybe they want to get into defense or something.
Skill is very rarely the problem for computers, if you're considering it as district from taste (sometimes you call them both together just skill).
If anything it's the opposite, except maybe at the very low end: AI boosts implementation skill (at least by increasing speed), but not {research, coding, writing} taste. Hence slop of all sorts.
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.
> 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.
That's absolutely not the case. I can look at code and realize that it's garbage because the architecture sucks, performance degradation is out of the window, and there's lots of special casing and unhandled edge cases. That's the taste part. But I can also absolutely be underqualified and be unable to figure out how to improve the architecture, fix performance issues, or simplify special/edge case handling.
To be strategic, you think hard enough how to get somewhere and carefully plan and eliminate unknowns until you reach a point when getting there is no longer interesting.
Congratulations: you have successfully turned your cool idea into a chore. It’s just a lot of trivial typing and package management and it might not even be all that impressive when it is done.
Your idea is not at all a path well-trodden, but it is a path down which you’ve sent a high-resolution camera FPV drone so many times that you doubt you will see anything new in person.
What might happen then is that you try to keep it interesting by making it more impressive and raising the bar, by continuing to think and plan even harder. Why not write it in Rust? Why not make it infinitely extensible? More diagrams, hundreds more of open tabs…
It can absolutely lead to cool ideas with strategic and well-defined execution plans. Unfortunately, it is also difficult to break this loop and actually implement without an external force or another mind giving you some reframing.
> Congratulations: you have successfully turned your cool idea into a chore.
The article gave me a vague, off-topic sense of unease but your comment crystallised the feeling for me.
I really wish less emphasis is placed on this kind of blue-sky, "strategic" thinking, and more placed on the "chores". Legwork, maintenance, step-by-step execution of a plan, issue tracking, perspective shifting etc. are all, in my opinion, critically important and much more deserving of praise and respect than so-called "strategic" thinking.
Which, IME, most people can't do anyway! After they've talked their big talk you suggest that there's a practical, on-ground problem and they look at you accusingly, like you're sabotaging their picture. And I'm like, no, my friend; reality is sabotaging your picture, it's just the two of us here and you're not losing any face by me pointing that out, and also if you were an actual strategic thinker you'd have taken my on-ground problem into account already...
This might come from childhood and problematic praise patterns. You can grow to both crave praise and surprise, but at the same time when you get it not really value it. You might be interested to do impressive work as play when you don’t know how it will pan out, but if you don’t feel like it is interesting enough then you are demotivated.
I think it is important to be able to strategise, especially if you can delegate parts of the work. If you cannot delegate, there needs to be a balance with capacity for grunt work. One way to address it perhaps is learning to get in the zone and enjoy ongoing work as a process. Unfortunately, sometimes it is hard to snap out of big picture view and get to it.
I’ve found the best strategies are the ones you can abandon. clearly defined tactics and an appropriate application of people and resources require a quarterback with an ability to audible.
It’s possible to make no mistakes and still lose, it’s when people get offended about something they are wrong about that creates a tolerance for Pyrrhic victories.
> It’s just a lot of trivial typing and package management and it might not even be all that impressive when it is done.
> What might happen then is that you try to keep it interesting by making it more impressive
This feeling is something that immediately sets off an alarm in my head.
IRL every time I tried to impress someone, I said or did stupid things. These experiences are now part of cringe memories about myself.
In software, the paradox is often that making something simple is difficult, but easily reproducible and unimpressive for most people. It is kind of like the engineers' version of when people say that their 4yo kid could do the same drawings as Picasso.
Just go through the last 90% and finish the thing. Like Antoine de Saint-Exupéry said, perfection is reached not when there's nothing else to add, but when there's nothing more to remove.
Then put the V1.0 tag on it and move it to maintenance mode. Then move to the next project, which very well might be about covering a different set of needs in the same area.
Planning as a dopamine hit, turning creativity into project management, then raising the complexity bar just to feel engaged again. It's like chasing novelty within the sandbox instead of stepping outside it
RIP the project Ive spent 5 years on. Spent more time doing thinking than doing. Shifted goals higher and higher and never felt satisfied with what I had done. And now at the supposed end even my perfect goal seems completely uninteresting
I think this is why it helps a lot to build something you actually use. Because then, the barometer for what is good becomes a lot more defined: "Did I solve the problem I had", and then slowly build up from there.
Instead of trying to imagine a thing that someone else might or might not need.
I've been slowly chipping away at a heroku alternative called Canine [1] for the better part of a year now on the side, and for once, I don't feel tons of pressure or self loathing for not working on it quickly enough.
I use it every day now, and whenever I come across something that I wish was a little better (at the moment, understanding how much memory is used by the cluster is a pet peeve), I ruminate on it for a few days before hopping in and making some changes. No more, no less. It helps me get away from "what is the perfect solution", to "can i fix this thing that annoys me right now"
I really think that's the wrong question, but I don't know how to formulate it any better... it should be somewhere between playful curiosity ("how did it advance me a step in my own interests?"), pragmatic foresight ("how did it open up new possibilities?"), and bland reflection ("why was it the necessary thing to do at that moment?").
> "can i fix this thing that annoys me right now"
Whatever your questions might be, I sure hope they won't only aim for a boolean answer.
my intuition on all this, and what both you seem to be getting at is that is wildly difficult to understand the problems of others at least to the degree that you understand your own problems, which even then understanding one's own problems is hard... which leads to the perspective of focusing on what they understand (their own problems), and then as a side-effect of addressing their own problem helping others by documenting their problem and attempted solutions... documenting and broadcasting adds a little bit of overhead but it seems like an environmentally-friendly approach to participating in society in a healthy way
In the spirit of July 4, John Lewis Gaddis explores a similar theme in "On Grand Strategy". This is one of my favourite explorations, where he compares Abraham Lincoln and John Quincy Adams:
> Compare Lincoln’s life with that of John Quincy Adams. Great expectations inspired, pursued, and haunted Adams, depriving him, at critical moments, of common sense. Overestimations by others—which he then magnified—placed objectives beyond his reach: only self-demotion brought late-life satisfaction. No expectations lured Lincoln apart from those he set for himself: he started small, rose slowly, and only when ready reached for the top. His ambitions grew as his opportunities expanded, but he kept both within his circumstances. He sought to be underestimated.
The point -- being too ambitious can slow you down if you're not strategic.
Some people grow to both crave praise but also when they get it not really value it; they want people to be always surprised at cool stuff they can do but are not motivated to do boring uninteresting work. This may be accompanied by one or more of: perfectionism, narcissism, rejection anxiety, etc.
I suspect this might have to do with praise patterns in childhood.
> e.g. By definition the 99.9th percentile person cannot live a 99.999th percentile life, if they did they would in fact be that amazing.
This seems far too deterministic and I think is contrary to what you're replying to.
It sounds more like a 99.999th percentile person[0] that constantly reaches too far too early, before being prepared, will not have a 99.999th percentile life. A 99th percentile person who, on the other hand, does not constantly fail due to over-reach, can easily end up accomplishing more. (And there are many other things that might hold them back too - they might get hit by a car while crossing the street.)
[0] in whatever measurement of "capability" you have in mind
Can we invoke a version of 80-20 rule here, that 0.1% people will easily capture success of 80% while subsequent marginal capture takes increasingly more investment and luck?
The first two sections reminded me of an observation I've made about myself: the more I delay "doing the thing" and spend time "researching" or "developing taste", the more I turn into a critic instead of a creator.
> Your taste develops faster than your skill
> "the quality group could tell you why a photograph was excellent"
They are critics now. People with a huge taste-skill gap are basically critics — first towards themselves and gradually towards others. I don't want to generalize by saying "critics are just failed creators", but I've certainly found it true for myself. Trying to undo this change in me and this article kind of said all the words I wanted to hear. :)
It's both dense and beautifully written. Feels like every paragraph has something profound to say. This kind of "optimizing-for-screenshot-shares" writing usually gets overdone, but since this actually had substance, it was amazing to read.
For those who haven’t run across it, I like the man in the arena speech from Theodore Roosevelt to put things in perspective when I turn into a critic, or get harsh feedback from a critic.
“It is not the critic who counts; not the man who points out how the strong man stumbles, or where the doer of deeds could have done them better. The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood; who strives valiantly; who errs, who comes short again and again, because there is no effort without error and shortcoming; but who does actually strive to do the deeds; who knows great enthusiasms, the great devotions; who spends himself in a worthy cause; who at the best knows in the end the triumph of high achievement, and who at the worst, if he fails, at least fails while daring greatly, so that his place shall never be with those cold and timid souls who neither know victory nor defeat.”
> At semester's end, all the best photos came from the quantity group.
The quantity group learned something that cannot be taught: that excellence emerges from intimacy with imperfection, that mastery is built through befriending failure, that the path to creating one perfect thing runs directly through creating many imperfect things.
This reminded me of Roger Federer, who has won 82% of all matches but only 54% of all points.
I really enjoyed this article and also believe that in many cases doing is superior to planning.
Just a word of caution: the author doesn’t account for cost. All examples given are relatively low-cost and high-frequency: drawing pictures, taking photos, writing blog posts.
The cost-benefit ratio of simply doing changes when costs increase.
Quitting your high-paid job to finally start the startup you’ve been dreaming of is high-cost and rather low-frequency.
I don’t want to discourage anyone from doing these things, but it’s obvious to me that the cost/frequency aspect shouldn’t be neglected.
That's a really important point, and I completely agree.
This perspective reminds me of an excellent book I recently read, How Big Things Get Done: The Surprising Factors That Determine the Fate of Every Project, from Home Renovations to Space Exploration and Everything In Between by Bent Flyvbjerg and Dan Gardner.
This book focuses on extremely high-cost "megaprojects" and emphasizes the critical importance of thorough "planning" before execution. This stands in stark contrast to the low-risk creative activities discussed in the article, which makes the point about cost even more compelling.
However, rather than being a complete counter-argument, I see a significant overlap. The book advocates *for low-risk, low-cost experimentation and creative exploration during the planning phase* through methods like miniature prototyping and CAD simulations. In this sense, both the article and the book highlight the value of iterative approaches, whether it's through frequent, small-scale actions or through meticulous, low-cost trials before committing to high-cost endeavors.
> This reminded me of Roger Federer, who has won 82% of all matches but only 54% of all points.
This is in large part just a function of the way the rules of tennis work. e.g. consider gambling games, where there are games where the house only has a 1% edge, but if you play long enough, the casino will get 100% of your money.
> At semester's end, all the best photos came from the quantity group.
My 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."
I think the lesson at the end of that semester is a bit muddied. It says the quantity group figured out a bunch of stuff due to multiple photos being taken, but there are a couple things we don't know:
1-Just because the single photo group only submitted one photo, they may have taken just as many as the quantity group
2-How were "best" photos determined (by prof? by class vote?)
If quality group took as many photos, then the issue is really about the subjective selection of "best" photo. The first group had 100x as many photos to choose from than the 2nd group, so it could be more about how well each person in the 2nd group was able to select best photo from their collection compared to however "best" photos were selected out of all photos.
This is not a very pedagogic method. Why divide the group?! Have everyone go thru the same exercise seems more valuable to me. This would get you fired today tbh.
I’m very good at one thing (thank goodness), but I do some other things that I’m not good at, to remind myself how nice it feels to just do something without the pressure of having to be good at it.
I also think being a beginner at other things reminds me that failure is what learning feels like, which gives me some perspective when my “real” job feels difficult although I’m supposedly so good at it.
When I look back at big things I’ve done, they’re all the result of just “doing the thing” for a long time and making thousands of course corrections. Never the result of executing the perfect crystalline plan.
Readit News
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.
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.
My attempt to improve the cliche:
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 notMaybe that actually is what you were saying? But I'm confused because you used the opposite words.
But they're saying your taste, in the context of self-judgment at attempting to learn to draw, might also be raised to a professional aesthetic, because you can already produce images of that level by typing words.
I guess I will add that a difference here is we are talking about taste somewhat differently. To me, genai has been a demonstration that taste and skill are not two points on the same dimension.
He can't really play an instrument, but he knows exactly what works and what doesn't and can articulate it.
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.
Deleted Comment
Detractors say it's the process and learning that builds depth.
Proponents say it doesn't matter because the tool exists and will always exist.
It's interesting seeing people argue about AI, because they're plainly not speaking about the same issue and simply talking past each other.
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 computing, to motorized carriages, to synthesized music. You can go back and read the articles written about these technologies and they're nearly identical to what the AI detractors have been saying.
One side always says you're giving away important skills and the new technology produces inferior work. They try to frame it in moral terms. But at heart the objections are about the fear of one's skills becoming economically obsolete.
It's important to realize this is actually a general truth of humans arguing. Sometimes people do disagree about the facts on the ground and what is actually true versus what is bullshit, but a lot of the time what really happens is people completely agree on the facts and even most of the implications of the facts but completely disagree on how to frame them. Doesn't even have to be Internet arguments. A lot of hot-button political topics have always been like this, too.
It's easy to dismiss people's arguments as being irrelevant, but I think there's room to say that if you were to interrogate their worldview in detail you might find that they have coherent reasoning behind why it is relevant from their perspective, even if you disagree.
Though it hasn't really improved my ability to argue or even not argue (perhaps more important), I've definitely noticed this in myself when introspecting, and it definitely makes me think more about why I feel driven to argue, what good it is, and how to do it better.
There's actually some ground truth facts about AI many people are not knowledgeable about.
Many people believe we understand in totality how LLMs work. The absolute truth of this is that we overall we do NOT understand how LLMs work AT all.
The mistaken belief that we understand LLMs is the driver behind most of the arguments. People think we understand LLMs and that we Understand that the output of LLMs is just stochastic parroting, when the truth is We Do Not understand Why or How an LLM produced a specific response for a specific prompt.
Whether the process of an LLM producing a response resembles anything close to sentience or consciousness, we actually do not know because we aren't even sure about the definitions of those words, Nor do we understand how an LLM works.
This erroneous belief is so pervasive amongst people that I'm positive I'll get extremely confident responses declaring me wrong.
These debates are not the result of people talking past each other. It's because a large segment of people on HN literally are Misinformed about LLMs.
Here is a copy paste of the quote:
“Nobody tells this to people who are beginners, I wish someone told me. All of us who do creative work, we get into it because we have good taste. But there is this gap. For the first couple years you make stuff, it’s just not that good. It’s trying to be good, it has potential, but it’s not. But your taste, the thing that got you into the game, is still killer. And your taste is why your work disappoints you. A lot of people never get past this phase, they quit. Most people I know who do interesting, creative work went through years of this. We know our work doesn’t have this special thing that we want it to have. We all go through this. And if you are just starting out or you are still in this phase, you gotta know its normal and the most important thing you can do is do a lot of work. Put yourself on a deadline so that every week you will finish one story. It is only by going through a volume of work that you will close that gap, and your work will be as good as your ambitions. And I took longer to figure out how to do this than anyone I’ve ever met. It’s gonna take awhile. It’s normal to take awhile. You’ve just gotta fight your way through.” ― Ira Glass
LLMs are good at things with a lot of quantity in the training set, you can signal boost stuff, but its not perfect (and its non-obvious that you want rare/special/advanced stuff to be the sweet spot as a vendor, that's a small part of your TAM by construction).
This has all kinds of interesting tells, for example Claude is better at Bazel than Gemini is, which is kind of extreme given Google has infinite perfect Bazel and Anthropic has open source (really bad) Bazel, so you know Gemini hasn't gotten the google4 pipeline decontamination thing dialed in.
All else equal you expect a homogenizing effect where over time everything is like NextJS, Golang, and Docker.
There are outlier events, like how Claude got trained on nixpkgs in a serious way recently, but idk, maybe they want to get into defense or something.
Skill is very rarely the problem for computers, if you're considering it as district from taste (sometimes you call them both together just skill).
Deleted Comment
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.
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.
Congratulations: you have successfully turned your cool idea into a chore. It’s just a lot of trivial typing and package management and it might not even be all that impressive when it is done.
Your idea is not at all a path well-trodden, but it is a path down which you’ve sent a high-resolution camera FPV drone so many times that you doubt you will see anything new in person.
What might happen then is that you try to keep it interesting by making it more impressive and raising the bar, by continuing to think and plan even harder. Why not write it in Rust? Why not make it infinitely extensible? More diagrams, hundreds more of open tabs…
It can absolutely lead to cool ideas with strategic and well-defined execution plans. Unfortunately, it is also difficult to break this loop and actually implement without an external force or another mind giving you some reframing.
The article gave me a vague, off-topic sense of unease but your comment crystallised the feeling for me.
I really wish less emphasis is placed on this kind of blue-sky, "strategic" thinking, and more placed on the "chores". Legwork, maintenance, step-by-step execution of a plan, issue tracking, perspective shifting etc. are all, in my opinion, critically important and much more deserving of praise and respect than so-called "strategic" thinking.
Which, IME, most people can't do anyway! After they've talked their big talk you suggest that there's a practical, on-ground problem and they look at you accusingly, like you're sabotaging their picture. And I'm like, no, my friend; reality is sabotaging your picture, it's just the two of us here and you're not losing any face by me pointing that out, and also if you were an actual strategic thinker you'd have taken my on-ground problem into account already...
I think it is important to be able to strategise, especially if you can delegate parts of the work. If you cannot delegate, there needs to be a balance with capacity for grunt work. One way to address it perhaps is learning to get in the zone and enjoy ongoing work as a process. Unfortunately, sometimes it is hard to snap out of big picture view and get to it.
It’s possible to make no mistakes and still lose, it’s when people get offended about something they are wrong about that creates a tolerance for Pyrrhic victories.
This feeling is something that immediately sets off an alarm in my head.
IRL every time I tried to impress someone, I said or did stupid things. These experiences are now part of cringe memories about myself.
In software, the paradox is often that making something simple is difficult, but easily reproducible and unimpressive for most people. It is kind of like the engineers' version of when people say that their 4yo kid could do the same drawings as Picasso.
Just go through the last 90% and finish the thing. Like Antoine de Saint-Exupéry said, perfection is reached not when there's nothing else to add, but when there's nothing more to remove.
Then put the V1.0 tag on it and move it to maintenance mode. Then move to the next project, which very well might be about covering a different set of needs in the same area.
Instead of trying to imagine a thing that someone else might or might not need.
I've been slowly chipping away at a heroku alternative called Canine [1] for the better part of a year now on the side, and for once, I don't feel tons of pressure or self loathing for not working on it quickly enough.
I use it every day now, and whenever I come across something that I wish was a little better (at the moment, understanding how much memory is used by the cluster is a pet peeve), I ruminate on it for a few days before hopping in and making some changes. No more, no less. It helps me get away from "what is the perfect solution", to "can i fix this thing that annoys me right now"
[1] https://canine.sh
I really think that's the wrong question, but I don't know how to formulate it any better... it should be somewhere between playful curiosity ("how did it advance me a step in my own interests?"), pragmatic foresight ("how did it open up new possibilities?"), and bland reflection ("why was it the necessary thing to do at that moment?").
> "can i fix this thing that annoys me right now"
Whatever your questions might be, I sure hope they won't only aim for a boolean answer.
Deleted Comment
> Compare Lincoln’s life with that of John Quincy Adams. Great expectations inspired, pursued, and haunted Adams, depriving him, at critical moments, of common sense. Overestimations by others—which he then magnified—placed objectives beyond his reach: only self-demotion brought late-life satisfaction. No expectations lured Lincoln apart from those he set for himself: he started small, rose slowly, and only when ready reached for the top. His ambitions grew as his opportunities expanded, but he kept both within his circumstances. He sought to be underestimated.
The point -- being too ambitious can slow you down if you're not strategic.
I suspect this might have to do with praise patterns in childhood.
e.g. By definition the 99.9th percentile person cannot live a 99.999th percentile life, if they did they would in fact be that amazing.
This seems far too deterministic and I think is contrary to what you're replying to.
It sounds more like a 99.999th percentile person[0] that constantly reaches too far too early, before being prepared, will not have a 99.999th percentile life. A 99th percentile person who, on the other hand, does not constantly fail due to over-reach, can easily end up accomplishing more. (And there are many other things that might hold them back too - they might get hit by a car while crossing the street.)
[0] in whatever measurement of "capability" you have in mind
In particular IQ is not associated with better life outcomes after you have "enough", and that "enough" isn't Mensa level.
> Your taste develops faster than your skill
> "the quality group could tell you why a photograph was excellent"
They are critics now. People with a huge taste-skill gap are basically critics — first towards themselves and gradually towards others. I don't want to generalize by saying "critics are just failed creators", but I've certainly found it true for myself. Trying to undo this change in me and this article kind of said all the words I wanted to hear. :)
It's both dense and beautifully written. Feels like every paragraph has something profound to say. This kind of "optimizing-for-screenshot-shares" writing usually gets overdone, but since this actually had substance, it was amazing to read.
(See how I turned into a critic?)
“It is not the critic who counts; not the man who points out how the strong man stumbles, or where the doer of deeds could have done them better. The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood; who strives valiantly; who errs, who comes short again and again, because there is no effort without error and shortcoming; but who does actually strive to do the deeds; who knows great enthusiasms, the great devotions; who spends himself in a worthy cause; who at the best knows in the end the triumph of high achievement, and who at the worst, if he fails, at least fails while daring greatly, so that his place shall never be with those cold and timid souls who neither know victory nor defeat.”
The quantity group learned something that cannot be taught: that excellence emerges from intimacy with imperfection, that mastery is built through befriending failure, that the path to creating one perfect thing runs directly through creating many imperfect things.
This reminded me of Roger Federer, who has won 82% of all matches but only 54% of all points.
I really enjoyed this article and also believe that in many cases doing is superior to planning.
Just a word of caution: the author doesn’t account for cost. All examples given are relatively low-cost and high-frequency: drawing pictures, taking photos, writing blog posts.
The cost-benefit ratio of simply doing changes when costs increase.
Quitting your high-paid job to finally start the startup you’ve been dreaming of is high-cost and rather low-frequency.
I don’t want to discourage anyone from doing these things, but it’s obvious to me that the cost/frequency aspect shouldn’t be neglected.
This book focuses on extremely high-cost "megaprojects" and emphasizes the critical importance of thorough "planning" before execution. This stands in stark contrast to the low-risk creative activities discussed in the article, which makes the point about cost even more compelling.
However, rather than being a complete counter-argument, I see a significant overlap. The book advocates *for low-risk, low-cost experimentation and creative exploration during the planning phase* through methods like miniature prototyping and CAD simulations. In this sense, both the article and the book highlight the value of iterative approaches, whether it's through frequent, small-scale actions or through meticulous, low-cost trials before committing to high-cost endeavors.
This is in large part just a function of the way the rules of tennis work. e.g. consider gambling games, where there are games where the house only has a 1% edge, but if you play long enough, the casino will get 100% of your money.
And I added the notion that even if you miss almost half of your swings you can still win big time.
My 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."
1-Just because the single photo group only submitted one photo, they may have taken just as many as the quantity group
2-How were "best" photos determined (by prof? by class vote?)
If quality group took as many photos, then the issue is really about the subjective selection of "best" photo. The first group had 100x as many photos to choose from than the 2nd group, so it could be more about how well each person in the 2nd group was able to select best photo from their collection compared to however "best" photos were selected out of all photos.
If you look at a book of Picasso's drawings/paintings he has thousands of examples of half finished, complete shit.
The masterpieces are the result of picking the best output.
I also think being a beginner at other things reminds me that failure is what learning feels like, which gives me some perspective when my “real” job feels difficult although I’m supposedly so good at it.
When I look back at big things I’ve done, they’re all the result of just “doing the thing” for a long time and making thousands of course corrections. Never the result of executing the perfect crystalline plan.