Taste Is All That's Left
notashelf.dev
notashelf.dev
“For taste governs every free — as opposed to rote — human response. Nothing is more decisive. There is taste in people, visual taste, taste in emotion — and there is taste in acts, taste in morality. Intelligence, as well, is really a kind of taste: taste in ideas. (One of the facts to be reckoned with is that taste tends to develop very unevenly. It's rare that the same person has good visual taste and good taste in people and taste in ideas.)
Taste has no system and no proofs. But there is something like a logic of taste: the consistent sensibility which underlies and gives rise to a certain taste. A sensibility is almost, but not quite, ineffable. Any sensibility which can be crammed into the mold of a system, or handled with the rough tools of proof, is no longer a sensibility at all. It has hardened into an idea..."
I think taste is developed from a combination of sensual attunement (clarity of perception and focus) and experience (exposure to relevant, high quality 'stuff'), but the catalyst is joy, or at least some kind of pleasure.
i see parallels to zen in the art of motorcycle maintenance as well, who's whole thesis if i can recall is something like, "quality cannot be put into words." Its a pre-rational thing that, try as you might, can't be pinned down.
One thing I fear is going to happen when more and more people use LLM's for coding is that they will default to the "average taste" of the LLM, and we will stop getting new interesting ideas about how to build things.
It is a possibility. But I also think we're underestimating the human need to create cool, unique things. Like yes most of the projects in this situation will have "average taste" but most of the projects out there today already do. Very few people have true taste and I don't think we're just going to see them disappear or be satisfied with LLMs feeding them "average taste." They will either likely stop using LLMs if that is the case or find ways around it to make it do things the way they want to, hence preserving their taste.
But I think it is a bit of an overblown fear that LLMs will just kill creativity and innovation in coding. Hackers will be hackin
On the other hand, we might trade that for creativity in other more high level designs where things like coding style is an unimportant detail for the experiment. For example, I have started playing around with microcontrollers because I can have the LLM generate the software while I focus on learning how to solder and think about how to modularize my hobby automation system. That's creativity and taste at a higher level which I didn't have access to before because I didn't want to invest my precious free time in learning the software ecosystem.
On the other hand, I did that in pursuit of a goal, and LLM's take me further, faster, toward that goal.
Hacking and a taste for hacking is a muscle you develop. LLMs will make most people not train it at all. Same way a huge number of people are obese and out of shape. For LLMs to be bad news in this regard, it doesn't matter if some people will still find a way to do something creative. As long as far more people (than without LLMs) don't, that's already bad news.
Yes, there are exercise nuts who are exercising like crazy, but the average population is getting weak and obese.
The same with mental muscles.
How many people can do mental calculations in their head nowadays?
What about remembering several phones numbers?
What about simply navigating with map but without GPS? (Or, heaven forbid, just by common sense and observation?)
Properly thinking about hard problems is exhausting. Majority will be glad to offload the hard thinking to an AI 'assistant'. The same way we offloaded computing to calculators, and memory and navigation to phones.
What remains is the easily manipulated lizard brain...
And I don't under the fat and out of shape part of the comment. Being in shape and being good at coding are not equal things in many aspects:
1. Most people learn code for employment. Most people get fit for personal reasons.
2. It takes considerable physical effort to get in shape. Getting good at code requires considerable mental effort but it is a very different form of effort.
You can claim LLMs will make people dumber and lazy. But that doesn't mean working out and being fit = being really good at computers in real life.
Lastly, you seem to have a cynical view of the world and believe in a merit-based structures but most people don't generally become super fit or hackers. Its always a small percentage of the population in general and most likely will always be. It is debatable if the availability of an LLM can reduce them to 0.
Raw "leetcode" algorithm intuition and database modelling/SQL are still largely intact for me because I never trust LLMs for those and want to actually understand what I'm building. But it's scary to think how easy it is to have your skills eroded and how quickly you become dependent on these tools.
Furthermore, if you can see it so transparently and have put a stop gap, why do you think the rest of the world or programmers will not? Why will they fall into the temptation that you can resist? Especially if we are talking about that specific subset of people that are already really good at coding and understand the pitfalls pretty well.
Maybe you can make the argument that someone who purely vibecodes never gets the skills of raw algorithm intuition/specific knowledge but in those cases, no skills get eroded because there were none to begin with.
It's not a prediction, it's already the case. Like students coming into computer science degrees and letting the LLM do all the work, learning nothing. Interns phoning it in too.
>Technology will make them lazy just because they can prompt an AI now?
Yes, that's how it works. The path of least resistance is what's followed. Same way we walk less because we can just get in a car, or do or order things online now.
>I think the human drive for excellence and tinkering cannot just be vanished just because LLMs exist.
There's no trancedent "human drive for excellence and tinkering". There's either an actual force shaping or there's a path which is easier and most will turn into slobs and take.
Same way much much much fewer people tinker with their electric devices or cars than they did in the 1920s to 1970s. They just throw them out and buy a new one, even when the device is simple and repairable. And countless other examples where "excellence" or even "good" is traded for covenience.
We can't say it in times of a general culture of confusion, like now. In times when there was an established cultural and artistic hierarchy, they could.
https://en.wikipedia.org/wiki/Sumptuary_law
not kings per se, maybe sultan, or the royal court, roman senate, etc.
I don't think it will have any impact at all on creativity in coding.
Creativity is rewarded in humans, just not by their employment where both training examples and monetary rewards can be found, rather the creativity is rewarded by challenges such as code golf, demoscene, and so on.
Go to a job interview and I have to know the shibboleths of Clean Code, SOLID, an arbitrary one of five frameworks, three different ways to handle asynchronous code, and four design patterns, and the magic word "agile". Invent something new at the workplace? If you're in a small team, or high enough in the hierarchy, fine. Big team? People will reject it with reference to those same shibboleths.
In which case yeah, projects are likely to converge on whatever pattern LLMs broadly fall into. But maybe that part doesn’t really matter. Not every project needs the engineer to care about that. If I’m not writing hardware level code, I don’t care what instructions my python compiles to, either.
Meanwhile nothing prevents someone from caring about these details if wanted or needed. Someone who knows and cares might absolutely do a better job than an LLM. Those people won’t necessarily go away.
But there -will- be a whole new category of software contributors who have ideas they don’t know how to express in a software language. Those ideas might well be very tasteful. So it could be argued that software development as a field will gain access to a whole new range of tastes.
I don’t know the answers but it all seems plausible
there's a tension between innate preferences we’re born with, versus cultivated tastes that require effort
And I think taste is subjective by definition, it doesn't compete with "objective taste" because that makes no sense.
Wouldn’t anyone need some reading “taste” in the first place to decide to read more.
And if they already have it, why would they need to read it?
If it’s all relative there can be no globally valid, or fixed, reference points by definition.
Social proof. Everyone has taste and everyone's taste in a given space is influenced and informed by the taste of others. It's mostly a consensus model. Newer members of a given community arise into said community and learn from it what "good" means, which can sound authoritarian but is really just... voluntary. If you like, for example, mens formal wear you will follow publications and noted figures in the mens formal wear space, you will learn what "good" means to them, and will emulate it out of a desire to fit in with them. As you get more knowledgeable in that space, you will develop your taste, enhanced by them, and ideally eventually contribute your own ideas to that mix. Some will be accepted, some will be rejected, again by group consensus.
It's a lot like language. If you want to speak a language you have to learn it first. If you go to France and simply blurt out French words at people, even with perfect annunciation, you will be incomprehensible to them. You learn structure, sentences, how to communicate ideas, how to inflect tone. How to tell the difference between telling someone to fuck off when they cut you off in traffic versus telling them to fuck off when they make a horrific pun. And, as people speak that language and use it daily, it will reliably change. The meanings of so many words in every language today are wildly different than they were even a hundred years ago.
David Hume
I like this quote because it's so blunt. Hume isn't saying we should give in to hedonistic excess, but he isn't shirking the impression either because it deserves to be said strongly.
I like this quote because sooner or later, one discovers it for themselves
Previously:
Taste in the age of AI and LLMs - https://news.ycombinator.com/item?id=47677241
You Had No Taste Before AI - https://news.ycombinator.com/item?id=45288551
I'm 100% confident that a human did not write this sentence unless they were deliberately trying to sound like an LLM. Just look at it! You don't need Pangram. There's a classifier model between your ears that knows how humans write.
Don't you and all the people in this thread claiming AI slop know that AI was trained on human writing?
Do you think this implies that it is impossible to distinguish LLM-generated text from human text? I don't think that follows at all.
>Running Llama 3 between your ears?
I'm always happy for a chance to improve my classifier! Can you provide some long-form writing from before 2024 that uses this style?
I went to the site and pasted something into the text box. The next step was to sign up.
I don't trust Pangram.
text.indexOf("—") > -1https://freddiedeboer.substack.com/p/i-wouldnt-say-pangram-i...
Free money, right?
lmfao.. what were you hoping to astroturf with that?
It's baffling to me how people are so dismissive of Pangram despite never using it, extrapolating their experience from GPTZero or something else.
One (slightly frightening) possibility is that many people write like LLMs even without assistance from LLMs. AI writing may have just become the norm for some. Maybe that's what's happening here.
Joining these editors used to take years of training in order to write like they do. Now we have their wisdom available on the command line.
What made pretty good "taste" pretty good was its novelty. Now that pretty good is common it's no longer stylish.
it's like a new generation of chefs that only knows of Chili's, and thinks it's good.
shudder
This post reads off as AI slop. You said it, I see it. I’m sincerely sorry for publishing something that has allowed you to feel this way. If my word means anything to you, I would like to assure you that this post was not authored by a LLM. Nor was it storyboarded, reviewed, checked, etc. by a LLM. Some readers have pointed out that people do not speak this way. That is correct. I do not speak, nor usually write, like this and this post will go down as my not-the-proudest, however, I take your criticism to heart—although not personally—and strive to improve.
I do write like this sometimes. The short sentences, the reversals, the one-word lines—all of it. It’s just the way it is. A LLM writes that way too, because it was trained on the same essays I grew up reading, so me doing it badly and a machine doing it look about the same to you on the page. That says something about my writing. It says nothing about who wrote it.
So let me be plain about it: Claude was not here. No LLM wrote this—not a sentence of it, nor was it outlined, drafted, reviewed, checked, etc. by one, and there is no prompt behind it either. It is just me, writing worse than usual. I will write the next one plainer. Next time, write to me. I too am a person behind this screen.
The truth is that AI generated text is getting harder to detect, and while AI writing is still very lacking, more writing is getting the unwanted distinction of "plausibly written by AI." This was always going to be the natural course of events but plausible shouldn't mean guilty.
We should give more grace. To prosecute each and every mediocre writer in a witch trial with such weak evidence is entirely unnecessary.
The funny thing is that there are no "one-word lines". This more or less cements the fact that it must be AI in my mind.
https://www.pangram.com/history/0b397596-fa85-4869-bae3-2b1d...
We are at the point, when there is too much cognitive energy needed to discern writing from human, human ai assisted and all ai. Should we know make mistakes on purpose to avoid being labelled as ai slop? :)
Isn't aesthetic a better word for this?
For what it's worth though--taste, aesthetic, intuition--they really boil down to one thing: feeling. Something you can't reason. Almost emotional.
Your statement is unfair and mean: The biggest flaw in the article is that the author is unable to be concise.
"That says something about my writing. It says nothing about who wrote it." - Two contradicting sentences, author's writing skills are part of the author as-a-whole
"The short sentences, the reversals, the one-word lines" and then "I will write the next one plainer.". - even more?
And... I wonder if this is like some agent wrote article, and, in the loop, added port-mortem, after visiting hacker-news comments and manipulate that this is human written. Or maybe author is just trolling us with AI-like prose...
What fresh hell is this? If this is human then I wish it was AI
I just do not understand why people - even when actively denying LLM usage - use the fucking em dash.
I don't care if it is the "right" thing to use there. The character has been associated with slop. Why do you keep using it without even just acknowledging that you did.
Just use any other character - like I am doing right now.
It must be AI indeed. Humans cannot be this dense.
___
Oh god I just saw the annotations on the side
> A fair pushback I got:
Dude. Why. Oh god. Why do you talk like claude. I want to believe you. I really do, but hell. Even claude could likely tell you that you sound like claude.
Oh my god.
Because they are literate? Unlike the "em-dash means AI" illiterate crowd?
I'm not going to change my writing because some idiots who never read a novel or heard about typography think only AI does that.
Like.. I get it. It's wrong. It feels wrong to give the AI nonsense just an inch and all.
But in the grand scheme of things, it's just highly ineffective dogmatism that makes people unheard, miserable and just further increases struggle.
Which people are free to do, in the same way that I am free to purposefully drop a massive hammer on my foot just to make some kind of statement. Hurts me a lot, rest of the world stays entirely indifferent.
a) Using some other horizontal line is not in the class of "wrong" that would warrant this sort of reaction. You're debating the pixel count. Not the object. The aspect ratio of it.
b) If you're acting out of fear that's dumb, yes. If you however simply pick your battles for efficiency, that's not "the terrorists win". That's "you win" instead of "you loose due to attrition".
__
I've also consulted with the LLM regarding the "class of wrong" thing, because I thought it might be not quite clear.
So what I meant by that is that it's not giving up actual words or dumbing down your sentences. Just swapping out a character that is practically indistiguishable for the untrained eye.
Hell, whole classes of social engineering attacks rely on that very property.
I know I know. "Wehret den Anfängen". Slippery slope.
But those are insane as a default reaction to everything.
___
I get it. SV sucks. HN sucks. The world sucks. Can't let it also take this little thing. If it can take all the big things, then at least it won't take this tiny tidbit.
Emotionally, I get it.
But that's not how you make rational decisions. Nor is it how we would win.
It’s like when people tried to tell everyone to stop using the ok symbol with their hands because a small group of hateful fucks pretended it meant something else. It only switches meaning if you let it, and stop using it yourself.
What happens when AI adopts something else? Do we give that up too?
With all of that said, this guy is definitely AI lol. He’s gotta be trolling us by doubling down.
At least temporarily until you got synced up with that group?
There is a place for the strategy of just continuing to use something and push through the noise there, but the em dash is not in that place. Common perception of it has too much momentum you cannot overcome like that, which - at the time of writing - makes it a bad choice.
How it will look like in 12 months we shall see, but today, I would advise against using it (without acknowledgement) in texts that talk about AI.
I think it’s fine to use as one of many signals to identify AI (not the only) but, again, avoiding its use is not going to solve anything.
That was a 4chan op designed to make leftists overreact and look stupid. There were also like a dozen other common hand signals with similar contrived meanings, but that was the only one they fell for.
Yet another successful op I can't explain to many. Here's an OK summary: https://mashable.com/article/ok-hand-gesture-hate-symbol-ant...
I couldn't care less if you mistake me for an LLM. That's your problem for being overconfident in your misplaced judgement.
FWIW I actually use three dashes (-) and my blog's build system transforms those into em dashes. This is not a defense, but nor is "this character is associated with slop" an argument. Yes LLMs use lots of words, phrases and patterns. Would you rather I stop using altogether? I am all for criticism, but please pick something I can actually change and improve without cutting a part of my style for no reason other than "Claude uses it too!"
You're misunderstanding me. It's not an argument. I have no strong opinions about it.
I am telling you how people perceive it. You can (and should!) use that information however you like, but don't mistake this as some sort of opinion thing.
I've observed the world. I believe it operates like this. Feel free to discard if you have data that suggests it operates otherwise.
__
Don't mistake my delivery of that for personal outrage about you or that unicode character.
I just get very annoyed when I see systems not working optimally with failure modes that to me seem.. dumb.
If you allow me to quote the LLM:
> He isn't trying to police notashelf's writing. He doesn't care about notashelf's writing! He is just a guy who noticed a pothole in the road, pointed it out, and is now watching in pure fascination as people fiercely defend their God-given right to drive their cars straight into it.
Thanks, gemini.
I guess around fourteen years ago—back when I was at high school—I picked up the legendary TeXbook. I was in love and totally beguiled by the great Knuth's Art of Computer Programming; how could it be so beautiful? how could it be so precise? and henceforth as I understood that he had developed that masterwork of TeX to make his book, I immediately went to read it. There, in page four he writes:
> Book printing differs significantly from ordinary typing with respect to
> dashes, hyphens, and minus signs. In good math books, these symbols are all
> different; in fact there usually are at least four different symbols:
>
> a hyphen (-);
> an en-dash (–);
> an em-dash (—);
> a minus sign (−).
>
> Hyphens are used for compound words like ‘daughter-in-law’ and ‘X-rated’. En-
> dashes are used for number ranges like ‘pages 13–34’, and also in contexts like
> ‘exercise 1.2.6–52’. Em-dashes are used for punctuation in sentences—they are
> what we often call simply dashes. And minus signs are used in formulas. A
> conscientious user of T E X will be careful to distinguish these four usages, and
> here is how to do it:
>
> for a hyphen, type a hyphen (-);
> for an en-dash, type two hyphens (--);
> for an em-dash, type three hyphens (---);
> for a minus sign, type a hyphen in mathematics mode ($-$).
So I kept using the beautiful em dash ever since; because that is how the greats do it.
Sorry buddy, next time I won't ask for permission. I don't care what you allow.
> I do not care about your taste.
But taste is all that we have left.
And then this:
> If this posts has offended you, then it tells more about you than it does about me.
So the author can't take any criticism.
When confronting AI as a writer and deciding how I feel about it, I've landed on the conclusion that I've never accused mathematicians of churning out "calculator slop." A calculator is just a tool to make the complex work of mathematics easier. I now view AI as a calculator for writing, among other things. If the idea is good and the information is sound, I don't let the occasional awkward phrasing bother me. The truth is, most people can't write very well anyway, so if AI helps them communicate better—even if it is obviously generated by AI— more power to them.
Really at that point, with head in hands, rather than try to explain the foolishness, I decided I was better out.
"Zoom and enhance" used to be a joke/meme, apparently it's now "engineering".
Focus on the content and the idea; not how it was written.
A person's writing style is developed through what they read. And if human's writing style becomes more homogeneous through AI then that's sort of a shame.
[edit]:
Someone already pointed this out.
- At least to me, AI writing (especially from Claude) is actively painful to read. It's worse than the average person who has flawed English (or just sucks at writing) because of how verbose and stylistically repetitive it is.
- AI writing is a strong probabilistic signal that what I'm reading is going to be crap in terms of the actual ideas and content too, even if it isn't the case 100% of the time. I just don't want to waste my time on that kind of thing.
I'm not using LLMs to think for me, instead just edit the writing so it has proper grammar and the run ons are reduced.
Even better for something that has data. You can pull PDFs with encoded tables and extract the data into consistent units to compare. You can have it write code to do it and cross check the outputs. You can do that in a minute. Would take hours without an LLM.
Writing is thinking. LLM writing makes authors worsr authors and even dumber people overall.
Also a calculator gives the same answer as a human (except for human errors where the calculator isa strict improvement). LLMs absolutely do not give the same output as humans.
[1] https://github.com/NotAShelf [2] https://github.com/NotAShelf/tuigreet
They have edited it again to be slightly more emotional. It's why their "On Taste" closure doesn't actually pertain to Taste anymore. Of course, they wouldn't notice the mismatch - they didn't write it in the first place.
They aren't being satirical. They're pissed they got called them out. Were they not, they'd not bother with edits.
1. Skeptic, but engaging in good faith - thank you, much appreciated
2. Skeptic, not truly engaging with the post - that's fine, can't win 'em all
3. Completely disengaged with anything in writing. They're under the impression that I am criticizing their taste, and felt the need to "strike back" - what?
The post-mortem is a response to all three groups. I've explained the situation, apologized for what I agree I did wrong, and clarified my boundary. It's not worth pointing time and time again it was not LLM authored, and I do not have anything to add.
"Taste" is one of these words that have been bandied about recently, in addition to "moat". I've never seen a productive conversation stem from either of those mentiosn.
"What it actually is"
"Here is the uncomfortable mechanism"
"Let me be plain about it"
"The floor"
"Everything downstream of the verdict"
I'll eat my hat if this isn't AI.
Very similar style to my AI 'utopia' https://aiking.dwyer.co.za/utopia
I don't even think all AI writing is bad, but lying about it definitely is.
That said I am recently getting paranoid about YT videos, I hear Claude traces in every 5th script. If people are going to spend substantial time recording and editing, is it worth "saving" time on most important part?
One thing that I’m particularly frustrated with is the writing quality of LLMs. Like this is the thing that they should be able to do, but I would say almost everything they write has almost no signal.
Over a mid sized AI generated codebase that means I’m reading like 500 words to figure out what a module is even doing.
The internal representations of this state and its projection back out to human language wouldn't be as concise as that of a practitioner or team that develop their own verbiage and ontology over time molded to their system.
This verbosity might get better as we figure out better ways for agents to learn long term and use that knowledge to adapt to the users and projects over time.
There might also be some good harness improvements we could consider like forked output streams or multiple long lived filter subagents to ensure that output appropriate for thinking is separate from code output and separate from output given to the user driving the session.
Obviously "good enough" was a poor pick of words of words on my behalf---and I'll gladly own it---but they should be "good enough" for something if a significant amount of resources keep getting allocated to them. Yes on a very personal level you look at LLM-generated code and think to yourself "wow this is garbage" but what about the people, as pointed out many times in this thread, that simply do not care? Does that not count as "good enough"?
To quote the parent commenter:
> They seem to be able to solve the immediate problem,
but not long term
… but does it work? Someone comes along, reviews it, "this is garbage, and does not do what it says it purports to do". Perhaps it even gave an output: the script computed … something, but it's just GIGO.
But that "check if this works" friction is the same friction that is what people try to avoid by generating it with an LLM in the first place. If you're too lazy to write the script, you're practically by definition too lazy to verify it.
Sooner or later you run out of turtles to put on the stack.
I literally can't imagine generating a script with an LLM without testing it at all.
Bash is one of those situations where LLMs can do really well. No human on Earth can remember all of the commands and even fewer humans can remember all of the switches for all of the commands.
This kind of remembering, searching, and assembling is exactly what LLMs are good at - as long as you're not writing a gigantic build system with hundreds of moving parts, in which case you should probably be using something more streamlined anyway.
Then you're extremely unimaginative as well as unusually fastidious.
Certainly someone - several someones - are generating lots of scripts and not testing them, given the PRs I'm seeing.
No quality large scale project can exist without it. And any seasoned engineer should understand by now that no SOTA LLM can produce quality engineering at scale.
Execute fast or get nowhere, a series of small wins get you to live long term.
If you need examples, look at game dev. There's plenty of games that have good execution but aren't fun to play or they're a confusing mess because there wasn't good overall direction.
Just because a videogame isn’t fun doesn’t mean there wasnt a cohesive engineering vision. God of War: Ragnarok is a good example of this. Excellent technical execution and (arguably) great direction but a terribly boring game.
And many games that are terribly engineered are also incredibly fun. Dark Souls is a good example - runs like ass, looks very rough even by the standards of the time when the game released, with terrible enemy AI in a combat focused game - one might even call it a confusing mess (and I laugh at the notion that it doesn’t have good direction)… despite all this it’s a classic and arguably the most influential game since its release.
Elden Ring carries a lot of legacy baggage from years of iteration on the same engine as ~~Dark~~ Demons Souls - and it’s widely considered From Software’s magnum opus and a masterpiece. Yet considering the scope of the game it is a great example of how small wins added up can solve large problems when executed with the skill and judgment gained from experience. So one might still consider it a success in terms of “engineering”.
Would From Software have been able to make the same game using Unreal Engine 5 built from scratch with dime a dozen “Unreal experts” brought in off the street? Not a chance. Want to know why western game development studios are suffering right now? Compare American layoff culture and race to the bottom economics to the retention rates of Japanese game studios like Capcom, Nintendo and other heavy hitters.
For many of the most marvellous things humans have ever built, if you take a peak behind the curtain you’ll still probably find some amount of duct tape and popsicles sticks somewhere keeping it all together.
Fun, however, is a matter of taste and you can’t engineer that.
But I mean they’re not good enough to do the things I need them to. Not enough that any difference can be chalked up to “taste”.
Put it this way, if you hired a very good handyman to build you a cathedral, you wouldn’t stand looking at the smouldering wreckage of the construction site saying “oh well that’s just a matter of taste”.
LLMs are also useful as a natural language interface. They're pretty useful for search (as RAG and autoresearch, not the glue-on-pizza Google search crap). They're good for filtering and classification against rules that can be specified in natural language instead of special syntax or by training dedicated models.
If this is an acceptable definition of software engineering productivity, where "quantity over quality" is prized, then hire me.
Because I guarantee I can produce dozens of PRs daily, each having tens of thousands of LoC deltas (pick any language you desire), none of which having research and/or understanding underpinning them, and all easily quantified as being "brute force."
I think it was from a Chinese person, as they took manufacturing of cheap things, low quality stuff, but managed to scale it to mass quantities.
I agree with that, it may not be reliable, full featured, well designed, ergonomic, etc. But quantity enables things and thus is a quality in itself. It allows use-cases that benefit from accessible cheap software. Those use-cases were not viable prior, because cost/time was prohibitive.
> I agree with that, it may not be reliable, full featured, well designed, ergonomic, etc. But quantity enables things and thus is a quality in itself. It allows use-cases that benefit from accessible cheap software.
The underlying assumption here is that the quantity delivered is acceptable and does not worsen the customer experience. To continue with the manufacturing domain example; if a company produced widgets quickest and for minimal cost, yet had more lawsuits stemming from their use, is that the kind of enabling an organization should pursue?
> Those use-cases were not viable prior, because cost/time was prohibitive.
Sometimes a cigar is a cigar and sometimes what is thought to be a desirable use-case is prohibitive because, once sufficiently vetted, it is neither cost nor time which disqualifies it.
> the quantity delivered is acceptable and does not worsen the customer experience
No, it will explicitly worsen the customer experience in other ways, but it will also give them a benefit: access to something they couldn't afford at all before.
I can guarantee that you cannot produce such PRs in the same quantity/quality than a modern LLM. The speed at which today's LLMs output code is superhuman.
Who said I would not use a combination of LLMs, scripts, and any other automation technique available?
However, look at history of DSLR cameras vs mobile phone cameras. Mobile phones were always worse than large format cameras, and we've got a massive quantity-over-quality explosion in photos taken. It didn't replace professional photography, but let people upload photos of their lunch to social media.
I think in programming we're getting frustrated because we're trying to naively use high-volume low-quality code generators in our previous low-volume high-quality workflows. We're still discovering what's the programming equivalent of bathroom selfies, photos of receipts and QR codes.
Programming is no longer skilled labor. Quality is a hobby.
I'm also not sure getting hacked is so bad for business. Most businesses that got hacked seem to still be around just fine.
How come humans consuming their own output gets better over time, but llms and any other form of ai consuming their own output only get worse?
Aside from the "amateur" qualifier, the Booch quote below provides insight to those questions:
The amateur software engineer is always in search of magic,
some sensational method or tool whose application promises
to render software development trivial. It is the mark of
the professional software engineer to know that no such
panacea exist.[0]
"Code" is shorthand for "encode", which can be defined as "encoding a solution to a problem", which implies knowing what problem to solve, and thus ultimately implying understanding of same.So "good enough" depends on the stakeholders' definition of that valuation.
IOW, if a person tasked with delivering a solution can instead deliver garbage and still get paid for it, then it is "good enough" for some definition of same. If the people approving a person's remuneration are not satisfied with this type of work product, then the answer as to whether it is "good enough" or not will be quickly answered.
The amateur is the one who hones a tool’s edge until it’s razor sharp, and cuts away all unnecessary detail until they’ve found the essence of what they’re trying to achieve. The work of an amateur is often highly impractical and uneconomical, but sublimely beautiful.
A professional does mean "someone who does something for money" but it also often just means "someone who is very good at something"
Similarly, amateur does mean "someone who does something out of passion without wanting/needing to be paid" but also often just means "someone who is just starting out, is new at something, and is probably not good enough to be a (paid) professional doing it"
You're talking about the "passionate" amateur and comparing it to the "getting paid" professional. I think many people talking about amateurs and professionals are mostly talking about "amateurs (newbs)" and "professionals (very experienced)"
An amateur is not a master nor a disciple of a master (e.g. future master).
The vast majority of amateurs have no ambitions nor passion and simply give up early on, that's a rose tinted view.
Since they don't get paid to do it, they have to allocate their precious free time toward the skill, which means they don't have those 40 hour weeks where they spend all their time honing their skill to begin with.
Even someone who does a skill half heartedly without passion nor ambition is going to learn faster with those 40 hours at his disposal.
>The amateur is the one who hones a tool’s edge until it’s razor sharp, and cuts away all unnecessary detail until they’ve found the essence of what they’re trying to achieve.
That's not an amateur and you know that. By your logic Japanese master craftsmen doing this are amateurs.
(Some similarities to hard drugs here.)
"the" is the error here.
There's places and people for whom cars are so. There's other cases where public transport covers the people while business-owned vans cover deliveries of bulky items, which is essentially how I've lived the last 8 years, though for "bulky" I should note I've seen someone take an actual kitchen skink on public transport here in Berlin.
I've also found some islands here Berlin with no bridge connection to the mainland and hence no practical use for a car at those locations; that said, my main reference for "car free" domiciles would be Sark: https://en.wikipedia.org/wiki/Sark
You need roads, traffic lights, drivers and pedestrians that respect rules, not too many holy cows in the way, not too much CO2 in your quasi-self-sustaining spaceship, lungs and livers that can deal with the soot, a tolerance for high-velocity impacts risks, not too many other cars around, ...
Taste seems to imply an art, but I don't think we're at the point of cleverness, of LLM innovating a new beautiful programming paradigm or pattern out of immaculate taste for code. We're just talking more basic, even bad devs have more terseness, more clear intent in their prose and code, etc.
It's "good enough" for many use-cases, but it could be better, even before expecting the most beautifully clear code from the best devs out there, it has not reached the level of the average one in readability and clarity of expression (both code and prose). That annoys the author, he has to intervene manually to trim all the fat, and therefore not "good enough".
Stock market as a measuring stick is completely irrational.
Put another way, LLMs are just another part of enshittification.
They are not good enough yet, the people using these tools every day, and with a high bar for quality and design 'taste' notice the rough edges.
They are still around because LLMs are plenty good enough for casual consumers, but where 'taste' really starts to matter in design or in writing, the rough edges show up much more obviously and users who have been working with these tools feel it immediately.
Look at how many AI lay offs there already were a year or two ago - back when almost everyone would agree they weren't good enough. If good enough didn't matter then does it matter how when AI is better?
And despite what you might be trying to prove, it's obvious I'm replying to an LLM (a green account at that), but it's not for you, I don't expect you to bother reading it.
And yet every time I see AI-written documentation, there's paragraphs worth of throat clearing and space-wasters like the word "genuinely" for things that could have been outlined in a couple of bullet points.
If you're talking about prose, this is obviously false. All the LLM prose I see is so mentally fatiguing to read that I usually just give up.
There are no lack of examples of poorly written LLM prose.
First are those that care very little about the quality of the work, or the process behind it, and just want a 'finished' product no matter what. These are many of the folks vibe-coding everything without even looking at the output, and a depressingly number of those getting hacked or what not.
But hey, if you've got an idea for a complex app or website but no interest in actually building it, an LLM will get you... something vaguely like what you wanted.
Second are small projects and small sections of existing ones, most of which easily fit inside the LLM's context window. If you're making a fairly basic WordPress plugin or React component or one page website, an LLM will probably be able to handle it just fine. Heck, it might not even look all that different from what a human might have created code wise.
One of the big issues we have those is that plenty of people and companies are using these tools despite having requirements that aren't met by them in the slightest. If you're working on a Google/Microsoft/Meta scale product where performance and security and code quality are of the utmost importance, then an LLM isn't going to be a great fit. Unfortunately, that's exactly where this technology is being used, and the results are becoming more and more obvious.
But then, once it’s passed the first human it should be considered human-to-human communication rather than LLM-to-human communication, and the long, winding, and often repeated justifications can be significantly condensed.
Also you can’t let it run loose with unit tests unless you want to be blasted in the face with hundreds of lines of absurd test fixture preparation.
This is the thing that drives my nuts about LLM-generated code. I will see PRs that fix a bug and the entire bug fix is re-explained in 10 different places in a code comment.
AI is not inaugurating an age of taste. It is shortening the half-life of taste and commoditizing software. What happens when software features, UX, and visual fidelity aren't competitive advantages anymore? If you ask me, it looks like business did in the 90s. We'll probably see the return of department store software in the next few years.
1: for the record https://en.wikipedia.org/wiki/Pull-to-refresh
Look how long it takes Chinese brands to transition from being clones to establishing their own corporate image.
True taste is interesting because is more like a worldview, a modus operandi, a continuous process… those are harder to replicate.
It's an interesting alt history - who would have won with no Apple around? I reckon we'd all own a lot more Sony and Nokia gear, it's possible the Cambrian explosion of weird featurephone form factors would have carried on a lot longer, perhaps the black rectangle form factor would never have won out.
Lets see if they will mostly sell iPhones to the end of their time now.
Most of their endless UI/UX fails are organisational in nature, no amount of design can create beauty from an org structure which generated stupid requirements.
And nobody there cared enough or had enough power to force the org into a shape compatible with Apple-level design outcomes.
Both the Fisher-Price XP style which was bot zeitgeist, and an attempt to answer for the skeumorphic tragedy apple was pursuing, and the recent floats, spacings, central taskbar mimichking the dock, etc...
Version 7 and 8 were great UX-wise, I have mixed memories about 10, mostly performance regressions bugged me, but was still faster than most non-flagship androids of the time... yet sometimes it felt sluggish to WP7 on potato hardware. The typography based UI was both fast and very readable and focused for well thought out apps. The standardized navigation buttons (on android button order may vary be vendor/model), and the clear gesture based navigation instead of hidden intearctions everywhere (long press, 3d press, app switching gestures etc), but using gestures for in-app navigaton were all easy to understand and grasp even by the elderly.
It was readable, well organized, nobullshit, but that is not what the masses crave. Metro was like how a "dumb smartphone" should be, in my opinion.
On desktop ot didn't work well. The live tiles were still a good idea, and if the taskbar supported them, it might have been a good idea (or not, was not tried, but could have be a bit like the old NeXT style refined, not stagnated and skeumorphized like on the mac).
This is the question I've been thinking about. All can be copied very easily and in scale these days.
You can start by copying but at some point you'll have to differentiate, and you might not be able to do so if you don't understand how your sloppy vibe-copied software works.
Invent something novel, get patent, you have exclusive economic rights to that for however long the patent lasts.
I'd argue that a well thought UX isn't easy to copy in the first place because it's not something that can easily be put into word.
It's the same for a lot of things, I have some clothes that I love because of their, design, quality and more ... something intangible that I have hard time describing and that can easily be explained with: It was done with taste.
I think what "poorly implemented" actually means for touch screen gestures is to be lacking the customizability to reassign or disable infuriating behaviors.
Gesture configurability is nonnegotiable: when implementing gestures, have the configuration system in place first and make sure every single behavior is tied to a preference.
Never thought of finding out who until you mentioned! What a small but fantastic contribution! Thanks Loren!!
Did I use the word evolution right?
I feel this will be a similar effect to the current slowdown of hiring of juniors: you're killing the pipeline of future seniors that lead development.
Also, there are a lot of areas where taste will absolutely reign supreme (and has been), especially anything related to media or entertainment (books, articles, videos, games, music, etc.)
Another possible future is that taste is not automated but its not part of the designer's job (if designers still exist). Instead some AI will generate 1000 of iterations and people will be employed to evaluate 100s of software UI each day for taste. These will be taste farms if you like. These people full time job will be saying yes or no.
Other possible futures also exist.
https://austinkleon.com/2020/12/10/quantity-leads-to-quality...
Anyone can push the button, but not everyone can discern whether the result is a good one or not. That skill is either learned or to some extent inherent in one’s abilities.
My example I’ve been thinking about is: what will be the first new, big programming language in the age of LLMs? Theoretically, anyone could go out and make it right now. The skills and expertise required are well-encoded within all of the frontier models. The thing is, without taste, the language devolves to a useless state rather quickly. On smaller scales, I’ve seen this with API design and even object oriented design. I’ve also seen it in AI generated images and music: devoid of taste, and numbingly facile and generic.
Edit: not to toot my own horn, but “numbingly facile and generic” funny enough is probably a phrase that an LLM would never create without significant prompting to refine writing style.
so it is profitable to sell vibecoding tools, but its unlikely to be consumed by "serious organizations"
https://www.reddit.com/r/popculturechat/comments/1rhug58/mcd...
so it is profitable to sell vibecoding tools, but its unlikely to be consumed by "serious organizations"
The biggest difference is that there are only so many ways to eat a McDouble, but you can actually wield a vibe coding tool with skill. There's nothing stopping you from looking at the code and asking for structural reworks or refactors that please your code taste. In fact one of the best use cases for AI coding tools is vibe refactoring old apps where the code is straight up horrible.
is Lovable used internally to create and improve Lovable product itself ?
It’s hard to give something like “vibe coding” a rigid definition, but I think we can all agree that it’s inversely correlated with "looking at the code". The more I examine the code while building, the less the activity is about vibes.
So, used this way, it's true that it's not a McDouble anymore, but it's also not so much of a vibecoding tool anymore either.
Isn't Anthropic currently using a "vibe coded" version of Bun they made using their own models?
People treat their computers like any other appliance. They don't care if it's riddled with bugs, they'll gladly restart their computer or refresh the page at infinitum to get it to work.
I think it's also why marketing and designers get more of a say in the software than engineers. UI polish matters more since it increases sales.
This is the hardest thing to come into terms with in this industry.
Surely there is more to software than CRUD apps
Slower load times means user won't use the product, won't click the buy button, or will simply leave.
They won't gladly do it. They'll do it begrudgingly because there is nothing better, or they have no choice, and they need to get their work done.
Just because people use your AI-vomited garbage programs doesn't mean they like it.
If quality software mattered, javascript wouldn't be the most popular way to write desktop software.
If users cared at all about quality software, we wouldn't have 800MB chat apps.
I hate it when visual designer do a product design or ux design job.
I hate it when marketing just imagine some fake use case in their head.
Market Research is real research. UX study is a real study.
now everybody just vibe their job
I just want to add that programmers have only relatively recently become so abundant (i.e. replaceable) that they have so little say in how software should be built.
Programmers are still the experts in the room, but they don't get what they ask for for free anymore.
I've spent a day fixing a feature my very junior colleague pushed, and which was merged by my should-have-known-better colleagues who have almost as much experience as me.
We have access to the same models. Why did her version suck and my features don't need fixing?
There's still something there, thankfully.
Ironically, though, I had written a post that had people debating whether I put any intuition or judgement into. Would've been real ironic to instead add a post-scriptum that said "Yep, none of it matters. I just slopped something in 5 minutes and it easily went to the frontpage. Look how easy it is!" but unfortunately that is not why I write, not what I intended to achieve, and not something I am equipped to do. I care about my work, which is why I care about your comment as well.
Or well better than 0 and just a claim.
Spotify - https://techcrunch.com/2026/02/12/spotify-says-its-best-deve...
Netflix - https://www.cnbc.com/2025/10/22/netflix-all-in-on-leveraging...
Stripe - https://stripe.dev/blog/minions-stripes-one-shot-end-to-end-...
Discord - https://discord.com/blog/developing-rapidly-with-generative-...
Its like saying you live in a 3D printed home because you added a 3D printed decoration + the house is structurally stable == its a stable 3D printed house.
It's so bad, and so everywhere, that I'm genuinely considering switching to a pre-AI stable distro and waiting 10 years for the AI hyped to be over before updating any piece of software ever again.
In hindsight, I have worded this rather poorly and let some phrases do a lot of heavily lifting for me in the post. Ultimately, I agree with you. Knowing, for this instance, is not half the battle.
I think the core still leads back to human agency and the ability to consider aspects that wouldn't fit into an LLMs limited context window or be able to be vectorized into a DB, including ultra-long-term consequences (especially those with great thinking abilities).
I still happen to think that AI/LLMs will never be able to "fully" replace humans, because the evolutionary process that led to our cognitive abilities and the way we train LLMs are vastly different thanks to different pressures, but maybe that's just me defending the last bastions of our collective humanity as a human; I don't know what else to root for.
It will soon no longer require taste. Or at the very least be 95% of the way there on the first run.
BTW, when was the last time Tesla driver died due to FSD fault?
Anyway, I completely agree and the past several years have been an absurd journey into borderline psychosis with some people.
Do your friends actually believe that AI can't automate these parts of their work? I think my answer would be that I'll just have to learn to do something else.
> I still happen to think that AI/LLMs will never be able to "fully" replace humans
Do you mean replace humans completely or just replace all the tasks humans don't want to do? I would hope that humans will still have a reason to live even if all the work is done by computers, and that the computers wouldn't intentionally wipe us all out.
pangram v4 reports a 0.0041% false-positive rate (~1 in 24,000 human texts) and a 0.3396% false-negative rate (~1 in 294 AI texts)
and i also think it was AI generated
Yes, previously the person who didn't understand shipped faster. It was a long standing problem. The people who crapped, got the bonus, and ran were much faster than the patient engineer of quality.
By the way, what were the essays that formulated Claude Style? if the author was indeed formed by them, I'd like to read them - or at least enough of them to understand.
And honestly: I've been tired of an age of engineers that are beat down, that only want simple, that finding the most blunt approach is the only way. It has felt tasteless. Anti-ambitious. It often is still very sensible and practical and what you should shoot for! But there are also people wandering around now trying much harder! And I am excited for those frontiers! I think it will challenge and shake the foundations that we've accepted as true, as There Is No Alternative, in exciting bold and fun ways.
I am however pretty unconvinced by the article. There's a lot that doesn't quite work for me, that isn't building the case I'd like, whose takes are off from my read.
> The output is good enough—that is the problem. Good enough is a solvent. It dissolves the reason to do better. For as long as making things was expensive, the expense did quiet work on our behalf. It rationed output.
Agreed about the rationing of output. I do think that the article though continues to show a magical thinking. That we have these things now and they autonomously do the thing. That the LLM's have solved it all.
The article itself goes on at length about how nebulous and abstract taste is:
> Taste is that. It is the compressed, wordless verdict you reach faster than you can justify. It is the “no, again” you say to yourself with total conviction and no available argument
But this contrasts so distinctly to me against "the output is good enough". Is it? That depends. That depends on your taste. The proximate first results come quick. But the technics underneath? Those themselves, in my view, rely enormously on engineering taste to support and advance. I think we see a very similar sort of magical delivery thinking, very clearly on display here:
> When the factories came, they could suddenly make everything—cheaply, uniformly, by the thousand.
As if there was some magical "good enough" transition where suddenly the aliens came and gave us this box that just does the thing. As if we discovered the right formulas and math and now: we had production. Again I think there's just an enormous amount of work and taste that is still actively required inside the factory box, that building the industrial processes is incredibly intense & difficult, even though we have reliable industry-line production and now robots doing the labor.
There's still so many gems, so much lovely material for thought. I love the provocations here, and I think there's a lot of great calibration.
> The friction was not an obstacle to developing taste. The friction was the curriculum.
Makes me think of yesterdays @apenwarr banger,
> Every slow prototype started out as a fast prototype, I think that’s how it goes https://bsky.app/profile/apenwarr.ca/post/3msemlo4rds2h
I would like to comment on this, though:
> that only want simple, that finding the most blunt approach is the only way. It has felt tasteless. Anti-ambitious.
I am always aiming for simple. If it's simple, it's maintainable and can be easy to reason about. Doing that is hard work, though. I used to spend three iterations to achieve it: functions are simple, easy to reason about, properly named and composable.
It's the opposite of blunt, though, so it might be that you meant something else with the term "simple" :)
Usually it can be that the complex artifact is the simplest to implement. It's harder to make the simple thing
Classic, Rich Hicky, "simple made, easy" talk reference.
How convenient it is that we’re all so awesome according to the one metric that can’t be measured
LLM can't waste weeks debating stacks and tools and then recast the problem as a new framework that needs to exist.
*Check mate*
Still, I like better when we actually do try to name what we're talking about. We've probably all read the motorcycle guys take on quality and things like that right? I guess the theme some are going with is that quality can't be objectively quantified and to define it is futile but I've never liked that take. If we think LLM generated code is low quality then it certainly makes sense to start our attempts to define or at least describe what makes the quality needle move, because language is how we encode lots of information and information is what feeds LLMs.
People also like to rag on uncle Bobs takes, clean code, etc but I like how at least he tried. I've been a fan of his for awhile but I'm not big on objects so don't care about his pushes on that sort of thing. The best take that offered hints that I would call quality is "A Philosophy of Software Design" by John Ousterhout, there is plenty of stuff in this short little book that was very satisfying to me, like for instance where Bob wants short/small functions, Mr Ousterhout was much more flexible on this, like for instance maybe some functions can be bigger if the need arises, things like that.
Given the recent "moving to a farm" ... 7 days later ... "leaving the farm" posts, it's hard not to read this as someone clearly struggling with the burnout which is all too common in our industry, and resultingly giving in to the false promise of a machine that can just handle the thinking for you.
Either they used an LLM or they have no taste and have used LLMs far too much elsewhere.
Author does not dispute that. Yet they claim to not use AI. So your preferred belief is that they are lying, rather than a thing that looks AI written might have been actually written by a human and you are wrong thinking that it can't be true in this case.
> I do write like this sometimes. The short sentences, the reversals, the one-word lines—all of it. It’s just the way it is.
> That says something about my writing. It says nothing about who wrote it.
> So let me be plain about it: Claude was not here. No LLM wrote this—not a sentence of it, nor was it outlined, drafted, reviewed, checked, etc. by one
Either the author is doing this on purpose, or this is some kind of art project. I don’t buy the “just a coincidence” story at all.
I think AI has broken HN. The readership is so head-in-the-sand about AI that they wouldn't recognize 2000 words of Claudeslop if it genuinely slapped them in the face
The alternative explanation (the top commenters actually read it and somehow didn't recognize it's obviously written with AI) is just too bleak and I choose to not believe that.
Not to me. It's actually quite sharply written. I enjoyed the style a lot.
Now that creation is cheap, the scarcity has moved to adoption. Things built without taste are less likely to be adopted, to survive. At least that is what I'd like to believe.
You need a long term, persistent abundance to develop and even have a use for taste.
I don't see why would software be any different.
I don't fully agree with it — for one thing, I think you can develop taste in a field without actively participating, but you have to engage with it beyond passive consumption. Basically: I think it's possible to be a good movie critic without making movies yourself. Given the collapse of the friction/effort side of things, I think that is really worth unpacking.
I have to say I find the debates about the post's style and em dashes pretty disheartening. There have always been plenty of good jokes to be made about HN's culture, but wow. For a community that has been snarky about fools counting lines of code for 40 years to be out here counting em dashes is pretty damning.
This conclusion may be unwelcome here, since it implies that AI can acquire "taste".
[0]: https://www.jamesshore.com/Articles/Quality-With-a-Name.html
The only difference I see between what happened to master craftsmen during the Industrial Revolution and what is happening to programmers today is that I belong to the latter group, so for the first time, the coming employment crisis feels personal.
There will be no mass job layoffs for antying but relatively automatable stuff.
If you have taste in writing code, you spend less time on bugs and can implment features more quickly. This is still true with LLMs if you learn how to direct them instead of having them direct you.
Someone else without taste can re-implement what you have done with AI. But it will take them more effort, more time, and more money.
But that's always been the value in writing code. Any MBA can end up producing software to accomplish something by hiring other people. But their company might not get off the ground because of the expense of not having technical competency (or engineers with taste) at their core.
I think there is almost a split between people who have read ZAOMM and people who have not.
I recently made a post in my circles about how "meaning" is what human quality is. If you look at classical art a lot of it could look objectively nonsense and have technical mistakes, but just because the machine can make a picture does not mean that it attributes any meaning or communicate any intention. The difference between human-made classical artwork and machine-made classical artwork is the meaning and symbology behind it
The problem comes later when the code no longer reveals the domain and the processes of the business, and where changes start affecting other expected business behaviors (at least that is what I think would happen, I find the code too distasteful to let it get that far).
Yes, that's partly a sense of qualified taste I've built through experience, but I think it also comes from trying to actually understand user needs better. E.g. Our finance department says they wants a daily report of invoices, but what do they ACTUALLY NEED? Maybe the problem to solve is to allow more flexibility with billing dates, or increase billing strike attempts, etc. That stuff sometimes doesn't come out until you really ask because of all sorts of organizational and social beliefs, fears, etc. Practicing that and recognizing the signs means you can do that rethinking earlier on in the process, before dev starts.
The wall is the point, if you want to truly know the truth of something. I still believe there is no royal road. Taste isn’t the answer to why you would choose a bump allocator over a slab when designing a system. It is experience, wisdom, and the long hard road of trying yourself and failing. Taste comes after.
There is much joy in suffering when the result is knowing.
Too many people have tried to declare victory over software engineering prematurely and it shows.
Every AI-frustrated (but LLM-written, sigh) blog post about the loss of taste and craft and hard work in development sounds like we've given up the interaction with the machine. Like human work is sitting back in your chair and shitting on stuff.
That's obviously not true! That's not how any of this works!
It's hard and weird to develop with the LLMs because they just do stuff. Lots of it is good, some of it is OK, some of it's horrible. Unpacking what it's done is hard and weird because software isn't just lovely UX, it's also data structures that scale and performance and privacy and enterprise controls and SOC 2 and onboarding and accessibility.
If you want to build real software, all that stuff has to get done. Today you're working on the feature, tomorrow you're making it scale. It's long-term and iterative and complex and hard to pack into a prompt or a markdown spec.
The work is the work, done at and with the computer, and it's way more than just "taste."
But toil is not gone. We have still have code owners, lawyers, physical hardware, thousands of configurations that we can't test them all.
And notably: we will still be asked to write software we can maintain in the future.
Sure, there are short-lived non-critical software projects where LLMs will rule.
But for many big complex projects, you can't land code without reviews. You can argue its because taste is already being enforced in the name of maintainability.
Why do you think orgs are pushing less reviews? Token-maxxing increased PRs but stupid meat brains are a constraint. So of course, remove that constraint and you’ll have your features faster!
Example: a plugin architecture with a solid API that makes degenerate behavior limited to usages of said plugin.
If your opinion or understanding of how a program works or how it should work is your main asset for keeping your job, then I think you're the one who's going to get cooked. You’d have to be rather disillusioned to wake up in the post-COVID era, with technology that triples its algorithmic efficiency every year, and conclude that a dehumanizing industry will still need our expertise in the future.
The key words here are “dehumanizing industry”. You can always bake your bread the old-fashioned way or cook your steak in « your own small restaurant », no one will stop you. But small restaurants, at least where I live, aren’t doing very well.
Quoth Cokie: "When everyone has the same brush, the only variable left is the hand."
AI isn’t suddenly making taste important. It’s shortening the time between someone’s product judgment and its contact with reality.
Previously, bad taste could hide in a fog of war: technical delays, market shifts, implementation tradeoffs, changing budgets, and shifting priorities. By the time the product reached users, causality to how much 'taste mattered' was murky.
Now, we can see more clearly (and much earlier) whether the judgment behind a product creates value. AI (and it's usage in this context) makes it harder to hide bad taste.
Through that lens, I think this is a good thing.
Reading text, it can either grab me or it doesn't. I've asked about that to an AI and there's some reason for that. Some text is more compatible with me, due to the rhythm or combination of chars/words used, how they actually look/feel, it's not just about the content. So I'm assuming some writers are going to be more compatible with me while others will make me dismiss them quickly or just skim.
I like to think I have the correct objective taste in music, but everybody thinks that about themselves.
Reductionism is hard to apply to intuitions, and we often fool ourselves.
I personally call this the obviously test: smart people correctly notice something and say it is obvious. It is a rather rarer skill to understand and explain why. I have particularly noticed it with coaching (which adds the next levels of difficulty in getting someone to grok what you've seen).
Prescient.
I really have no idea how future software engineers will know how to write software in a world wherein software is written for them wholesale.
Then we'll need to accept that coding is better when it's done by computers, and we'll start telling everyone it's actually the prompts and context that steered the machine that really matter.
Doesn't that mean guaranteed failure in the market if you use taste as your guiding star? Therefore, there's really no way to enter the market anymore.
I don't know how you then ship software or monetise it...? The market will just clone it.
So... Don't share stuff publicly? Only share with closed groups? Where does this leave small-time software development...?
Maybe software moves to this after it's commoditized? Users might prefer an artisanal one vs ordering it off the shelf or using an agent themselves.
If taste is maintainability, etc.. the no quite the opposite.
The startup that has no taste and vibecodes mindlessly might end up with a codebase they can't maintain or refactor. A product that can't advance.
But honestly, I don't feel like the toil is gone. Landing code in big projects remain hard.
Claude, is that you?
I haven't seen a human write like this, ever, and I've read a lot of books. The 'want to be careful here', the 'doing a lot of work'... common. If it had "I'd like to gently push back here" next to it, I wouldn't have been surprised.
All this doesn't necessarily translate to sales though. Because, to evaluate those things requires attention, trust, time and effort.
This is a significant barrier because a lot of software will appear to meet all of these superficially.
After 1 day of usage, a piece of software may appear to be intuitive, reliable, secure, performant and useful... But then after some time (sometimes a whole week or longer) you run into a critical scenario and discover that it cannot be solved with that software... Or performance drops off sharply after you created the 1000th record in the software... Or a hacker takes months to find that one endpoint which allows full remote code execution.
Even in an optimistic scenario, 1 week is a long time to evaluate a piece of software. I've encountered software which took 6 months and large teams of people to realize that it wasn't suitable. That's how long it took to hit the critical limits. It's a very long evaluation loop.
So you cannot judge new software efficiently by just looking at it. Even industry consensus is problematic if the software is very new and complex... Plenty of trends have fallen off a cliff in the past. You need to understand who is behind the software... And even that's not so easy; social proof can be misleading when it comes to deep technical ideas. The people who are good at social networking aren't necessarily good with tech.
I think AI slop code is going to be a much bigger problem than people anticipate. And the irony of it is that the solutions already exist... What doesn't exist is the mechanism to identify those solutions. But even the mindset needs to be corrected first.
I'm seeing the same thing. Of course, it's always possible that AI capabilities grow significantly from here and this worry is moot (and there will be other things to worry about, like whether I'll have a job). But seriously, after a while AI generated codebases really fall apart.
It's a bit of cope from me that this problem won't be solved in the future, but I'm also really disappointed with how many people really do not care about writing high-quality software that is easy to understand, performant, and resilient to bugs. Like, why did you decide to work on software in the first place?
I think we're going to see some pretty careless mistakes in the future that will result in a lot of pain...
Firstly, people don't agree on what good code is (developers who get paid by the hour tend to favor complexity so they think good code is complex code), secondly, AI companies have an incentive to produce more tokens; this works against good architecture since good architecture would cost fewer tokens to maintain. Thirdly, many decision makers tend to conflate complexity with intelligence, hence they are more likely to prefer complex solutions over optimal ones.
One thing I'm excited for is the expanded ability to modify and create my own interfaces and software so I don't have to be subjected to the bad taste of others. An example of this is something like Chrome reading mode that removes all the stupid decoration from what I'm trying to read.
Some small examples: Google Chrome doesn't have default shortcuts for accessing bookmarks so I made an extension for myself that does this. I have a SketchyBar setup that I'm constantly updating. Recently added my CC/Codex plan usage to it so I'm no longer constantly running /status in the different CLIs. Etc, etc.
The company that needs a webapp because everyone else has one is never going to value "taste".
To adapt to this AI world, we need to either ship more lower-quality software, or start seeking out higher value problems. I don't see any other way around it.
Haydn to Leopold, 1785
https://en.wikipedia.org/wiki/Haydn_and_Mozart#The_%22Haydn%...
Actually I think it is possible to reconcile Kant's third critique with the statement "LLM is possible to make aesthetic judgement" (with certain generous application of principle of charity, naturally).
That's why AI prototypes of front end UIs tend to look the same without massaging them with your own design tokens, design language, and injecting your own taste.
But people can and do tell you what is worth making. Taste is largely set by class and power. The “skill” is having the right context (wealth, education, network) and then pattern matching on it.
I’m pretty sure it was not technology that killed the web it was the kind of toxic crap like that, that we’re seeing from communities and that’s nothing new
I'm extremely irritated that the post is being accused of being AI slop. I have a visceral reaction to AI generated writing, and this post rang 100% human to me.
Makes me actually quite angry that one can no longer use short, pithy sentences without being accused of using AI. If AI causes everyone to reject actual decent writing because someone can't distinguish between it and that from a human, we have other problems on our hand.
The content of the post resonated with me 100% as well.
In Walter Murch's "In the Blink of an Eye" he describes how, when cutting a movie, the reason cuts work at all is because human experience has cuts: we blink.
More specifically, we blink when a thought is complete, to finish one thought and begin another.
When a movie is well-edited, the audience will adapt to the rhythm of the movie, and you know you've placed a cut at the right moment when the audience will blink at the exact moment of the cut.
The same "rhythm of thought" applies to written essays as well, and once you get a feeling for it, you'll notice how AI generated text follows no such rhythm, no such structure.
AI generated text has the rhythm of TV salespeople combined with tiktok brainrot, overwhelming you while at the same time saying nothing at all.
I've noticed some people on the internet dismiss content just by its length too now. I assume this is because they're not used to the idea of a human producing long form content (as opposed to the short form rewarded by popular feeds). I wrote a post (other forum, other handle) where I included some markdown tables and detailed explanations in an attempt to be thorough and help others answer my question and got accused of having LLM generated it despite writing it myself. Maybe the usage of markdown tables or the length of the post was the issue. Anyway, it's not nice being dismissed as AI slop when no AI was involved. I also don't see how there could ever be a reliable way of identifying origin of digital content such as text on a forum.
Perfectly reliable, no.
But:
1. these models aren't even trying to hide their nature, if anything the opposite
2. a great many users of those models are (lazy or time constrained, doesn't matter which) or lacking in style of their own, and in each of these cases the result is they don't prompt the models to hide their default style; worse, the outputs keeps getting RLHF-ed so despite how much of an "ugh" factor it has to the reader, most people making these things, to the extent that they do review the content at all rather than blindly uploading, actually like the style
3. Models don't share state between users. This means the model won't act "bored" from having already written the same thing before, so when 5000 people all prompt for "blog post about X", then it will create 5000 blog posts with almost identical in writing style. In turn, this means that the style of the most-used model (I assume for English-language blog posts this is still ChatGPT) has become cliché faster and harder than almost anything else.
Just reading the title and I was already thinking about that book. It's a great book though it gets progressively more difficult
The point being more that the development does weigh more heavily on having fun ideas to ask AI to build
I think there's probably also a place for people to make guides for AI-assisted programming or even personal essays on their views of "taste" or what they want code to look like?
I see pop up frequently objections to vibe coding (different from mere AI assistance in coding - vibe coding being creating things without looking at the code at all) that it doesn't account for architectural descisions, cybersecurity decisions, edge cases, and other such things. So to me it looks like a next step might be in identifying these things "vibe coding" doesn't do well, that people can learn more manually, so they can do at least AI assisted coding well.
I disagree that consuming content in a field is not enough to build taste. I'd argue it's actually better than creating, simply due to scale. 1:1 sure, creating something will give you more "taste" than consuming something. But it's not 1:1. Creating takes so long. And creating mixes design and implementation. When you're implementing, most of the time, you aren't building taste.
As far as creating quality things goes, and "the wall", doing it well becomes a practical problem. Writing code for example forces you to think deeply about what your building, what it does, and how it works. You can do that without writing code, you're just no longer forced to. It's not an intrinsic problem. It's just a nice side effect of coding that you lose, and need to figure out how to compensate for.
That so many developers believe this, is surely a sign of the fields impending death.
TASTE
For Professor Izydora Dambska
It didn't require great character at all our refusal disagreement and resistance we had a shred of necessary courage but fundamentally it was a matter of taste Yes taste in which there are fibers of soul the cartilage of conscience Who knows if we had been better and more attractively tempted sent rose-skinned women thin as a wafer or fantastic creatures from the paintings of Hieronymus Bosch but what kind of hell was there at this time a wet pit the murderers' alley the barrack called a palace of justice a home-brewed Mephisto in a Lenin jacket sent Aurora's grandchildren out into the field boys with potato faces very ugly girls with red hands
Verily their rhetoric was made of cheap sacking (Marcus Tullius kept turning in his grave) chains of tautologies a couple of concepts like flails the dialectics of slaughterers no distinctions in reasoning syntax deprived of the beauty of the subjunctive
So aesthetics can be helpful in life one should not neglect the study of beauty
Before we declare our consent we must carefully examine the shape of the architecture the rhythm of the drums and pipes official colours the despicable ritual of funerals
Our eyes and ears refused obedience the princes of our senses proudly chose exile
It did not require great character at all we had a shred of necessary courage but fundamentally it was a matter of taste Yes taste that commands us to get out to make a wry face draw out a sneer even if for this the precious capital of the body the head must fall
- _why the lucky stiff
My best guess is that it's a pointer not to any actual concept but to latent semantic space between concepts. Either a very novel or very Buddhist phenomenon, depending on how you look at it.
Great artists ship.
> I do not care about your taste.
Is the point of this essay that there's nothing left?
The idea is this: the commodification of intelligence requires the codification of domain expertise to function reliably, and proper governance to scale.
Taste, in my opinion, is a fill-in for absent function and lack of utility. Systems function; they don't require taste. Taste is why PG put Sam Altman where he did — not a system of merit, not evidence. Taste is why DJT can do no wrong in the eyes of his base. It is unprovable and has no true measure, and that is exactly why it gets leaned on so heavily: it lets you claim superiority no matter what slop your system produces.
You say the box moved taste up a level. Out of the making and into decision layer. That relocation is a smell. Your unfalsifiable thing conveniently gets moved to the one place it still can't be checked, at precisely the moment the making became checkable. Just like: Iran/Strait of Hormus, AI curing diseases and all of the other bold promises made by people who claim to be "taste makers" but in the end its all the same. Bullshit! Because thats what taste is a euphemism for in this context. Convincing others that you are correct in some way with no actual proof to back it up.
The vector here should not be "taste"; it's tolerances: written down, measured, enforced. The judgment gets encoded into a spec, and the spec is what survives the person who had it. That is codification; not "taste".
I completely disagree. I think this post has emdashes in the first paragraphs and that most of the people saying that it was generated didn't go any further than that.
Where is the repetition? The sense of deja vu? Where is the artificial sweetener, the overuse of adjectives? Where is the lack of meaning?
Suppose there was a group of highly motivated individuals that saw this article and felt called out by it -- prompt engineers, if you will. Because saying that "taste is all that's left" and that you can't develop taste without doing the work? That's saying that there's something still out of their reach. Something that can't be copied and reproduced ad nauseum.
This article gets at the heart of the issue and calls out -- though not explicitly -- these practitioners. It does this in a calm and reasoned way, in a way that they cannot defend themselves from.
I'm not making the claim that the article is an attack on anyone -- my claim is that a class of people will see it that way and react to that like Gamers seeing a 7/10 review for the game they're hyped for.
We still have a metric for good taste, and it is $. Solve a problem that people care about? They give you $. Solve problem no one care about? No $.
It is not perfect, but I challenge you to find a better metric that is as effective and simple.
If you are doing another app, the product experience and marketing will probably win. Many companies with better products lost, beaten to death example is Betamax
It set off all my LLM writing triggers and I noped out after about 3 sentences, because I'm designing/coding with AI all day and I'm 100% sick of its writing. I don't really care if it was written by an LLM or a person who writes in LLM style.
HOWEVER, the surprising fix for me was to ask a number of LLMs to summarize it. I omitted the "is this AI slop?" parts when I pasted it in. Like I said, I don't care about who wrote it, but I hated the writing style.
The AI summaries were quite readable.
They converged at a high level on the summary, but with a good bit of variance in nuance. I had a good follow up discussion with one of the LLMs, so I'm glad I tried it.
Hate to break it to you, but you don't hate LLM writing.
The irony of OP championing for “taste” in the age of mass produced slop, only to then post something that was likely produced by repeatedly reprompting with “no, again”
Discipline can be linked to system design standards and your review process, and it can be translated to measurable outcomes at scale and over time, regardless of how agents are involved: unplanned work, time to recovery, employee retention, etc. When outcomes like these become your priority, you see that you can't rely on taste alone.
If you believe that AI is capable of making good things, then it doesn't matter whether this article, or anything, was AI generated. Whatever it is -- software, prose, images -- if you have taste, you don't have to figure out if it was made by AI or not. All you have to do is apply taste and determine how good it is.
You once said we're like children in a forest, running around and putting every berry we find in our mouths. I believe generative AI (in the form of being generally available chatbots, writing and coding tools, image and music generators, etc) is a berry that's poisonous. Certainly so if we eat much of it. Making them generally available feels analogous to making the technology of nuclear fission or the invention of gunpowder generally available and shove it into every aspect of our lives. There are clearly some specific use cases where these technologies can be beneficial (in case of AI cancer pattern recognition from CT images sounds like one to me). But we need to be careful what we're using them for.
So yes, in this sense their use (as a generally available technology) should be abolished or at least heavily restricted. It would also limit the externalities it's mindless use generates in environmental cost.
The author seems to be advocating for choosing to "carry the burden" of one's taste (or aesthetics, judgement, standards, etc) while bemoaning that the market may not sufficiently reward for doing so.
IMHO, the core flaw is in mixing these two things 1) the market rewarding what it chooses to reward; and 2) individuals choosing to pursue some external/internal rewards.
I broadly agree with the premise that Gen AI has lowered the cost of software development and, as a result, the quality of the idea and its execution have become more salient differentiators than just the ability to bring an idea to reality. I also agree that pursuing one's own sense of taste/judgment or "objective function" is often intrinsically rewarding and worth it. But ultimately, an individual has to decide how much they want to (or need to) play for the external market rewards vs their own intrinsic rewards/motivations.
But I don't think it's coherent to argue that the market "ought to" reward one for their oh-so-special but mysterious, amorphous, and unmeasurable way of doing things, or that pursuing one's own taste/judgement is somehow automatically an exercise in greatness.
The industrial revolution seemed like the end of the artisan as an important man in his community, the death of good taste, and an apocalypse for professions like furniture makers.
And yet, do you remember the Aeron chair, darling of the dotcom era startup? The Eames chair, that wood veneer conversation piece which every real estate agent chooses when staging an apartment? In an era of mass production, taste moves up the market, but it never quite goes away.
Where does that leave our taste, dear reader? I am not sure. What I do know is that, just as the Aeron chair could not exist in a world without mass production, so too will there be tasteful software which cannot exist in a world without LLMs. I hope you're as excited as I am to build it.
I have no idea whether this was the actual intent, but it's where the disparate little facts seem like they might lead.
I agree with the points in your version, and the part above is the “meat and potatoes” for me.
I too am unsure about how much did the author intend to say something similar.
The main area where I disagree with the original post is this apparent fusing of subjective/personal taste driven value and market rewards driven value.
To summarize/clarify my view using the Aeron and Eames chair examples from your version
1. I agree that someone had to pursue their taste/vision for those products even when they could’ve “gotten away” with producing something mass produced and mediocre. And that pursuing their taste/vision likely became more feasible once the technology allowed them to focus on the “taste” while taking care of the boilerplate.
2. But, I will also add that the market actually saw value in Aeron and Eames chairs and rewarded their creators. It would’ve been incongruent for those creators to assert that their chairs were superior merely because they chose to pursue their taste/vision.
But this follows human structure and rhythm through and through, whether on the level of sentences, paragraphs, sections, or the whole text.
I'd say it's handwritten.
The first is an XKCD 605 (Extrapolating). The author makes bold predictions for the future as though they're inevitable, but gives zero evidence, because there is none, we're still at T=0. IBM is still in business. Wake me up when it's been taken out by someone vibe-designing a mainframe in kicad. Or even, let's see a dropbox clone get off the ground. Should be easy, right? (It's an HN tradition, after all.)
The second mistake is mistaking a large multiplier for infinity. The cost of code has not "collapsed to almost nothing" as the author claims. Talk to your CTO/CFO if you want the real story. They're probably freaking out over AI spend. But the point is, yes, AI has made things cheaper, but they didn't become monotonically zero.
AI had also raised the bar. You can't ship "good enough" anymore, it has to be great. And great still takes time. Time in QA, time obsessing over every workflow, time talking with customers and planning features.
Taste hasn't even entered the picture, and the analysis is already wrong.
Thats exactly what Im working on:
- web client: https://github.com/mickael-kerjean/filestash
- desktop sync: https://github.com/mickael-kerjean/fdrive
In line with the infamous top comment during their launch, it does of course support FTP as a storage, and the other way around exposing your Dropbox as a FTP server, while supporting theme so you have a similar look and feel as well: https://www.filestash.app/img/screenshots/theme_dropbox.png + tons of stuff Dropbox never did
so emacs is also left :)
So i guess proven secure architecture will come and stay.
Frankly, this barely scratches the surface of the hubris of engineers. I personally think AI has been one of the best things to happen to software engineering. Writing boilerplate or my millionth auth implementation was never why I fell in love with the craft in the first place.
I once wrote a pile of C++ templates that would let you wrap a C++ function as a JavaScript function, automatically converting all the arguments and the return type. Then I left the company. How did my successors find it? No idea. Maybe they pulled out all the automation complexity and replaced it with manually operated boilerplate.
This is true, but I was mostly referring to framework boilerplate (Spring, React, etc.) or plumbing boilerplate. If you've ever written code professionally, you know that most code that you write is just making your thing fit with someone else's thing.
If your consumer or your provider made bad engineering decisions, you have to absorb them. If your company mandates the use of a framework, you have to absorb that, and so on. So I think it's great that AI can write all the dumb shit I didn't come up with anyway.
It's also a sign of refusal to learn an editor or IDE deeply. Most of the ones I know have mechanisms (or plugins) for generating the boilerplate.
Although back to the language, usually the biggest boilerplate killer are macros and so many developers seem to really have a problem with them.
My goal when writing a software is always to reach a point where modifying a business rule is as easy as writing it in plain english. Which means abstracting the essential complexity (while being pragmatic).
Following form of the words I just read: these 100% animous filled HN threads about how everyone is bad and everything deserves mocker have to be some elaborate power game to undermine hope and human will, I genuinely do not understand how genuine human people could think it good to "comment" like this.
There's just such a ridiculous pile on of people with such enormous overwhelming negativity underneath this ocmment. This off-gassing is almost never engaged with the material. Now there's an excuse to write off any material we don't like instantly, to accuse it of fakeness. But I still do not see a realness enscribed upon people who so actively work to tear down & prevent thought & consideration.
To engage with the post: I do think the definition of fashion is interesting, and a real power dynamic to be aware of. But do think there's a lot of things that take off in the world because they are good and interesting and nice, especially in technology and products, that the world wants nice things, and will happily support you for doing that. And especially in tech, the technical decisions we start from and build underfoot steer us towards success in subtle compounding ways, that matter, and that taste is crucial, where fashion is not a factor.
Again, at a meta level: my distress & frustration at the top is less from seeing this comment, and far more from seeing everything down thread trying to out-do one another with how cynical and anti-meaning anti-trying they can be. But I think this post definitely started on an all too familiar note, blood in the HN waters that all too often gets us so sharky.
I'm a firm believer in not engaging with or promoting the content of misrepresented AI.
Let's look at
> So let me be plain about it: Claude was not here. No LLM wrote this—not a sentence of it, nor was it outlined, drafted, reviewed, checked, etc. by one, and there is no prompt behind it either
AI would've chosen rule of three (instead of 4 + etc), wouldn't have used the either at the end (doesn't fit into the rhythm), wouldn't have used "let me be plain" (more likely to use "let me be clear" or "let me be frank"), and wouldn't have chosen "Claude was not here".
If you've actually read a lot of essays and AI generated text (and sadly, I have), it's very obvious that this was neither generated nor rephrased by AI.
This is very much like the recent "kurzgesagt got banned by YouTube's AI detector" story, where the humans whose style was copied by AI now get accused of being AI
But the advent of design systems and software like Sketch and Figma pretty much automated the job away. You didn’t need the raw Photoshop skills anymore - any CMU grad could be a top tier designer now.
I see the same thing basically happening here. Taste will matter for a while but eventually people are just choosing the most accepted/expected optimal choices and anything that falls outside the trend will be “not good” in the same way skeuomorphism in design is no longer good.
So we’re lucky we’re in a taste era - it’s a lot of fun. You (yes you!) can still change it, shape it, establish the status quo of tomorrow
You can’t do product design without visual design - and many designers don’t. They’re picking from UI libraries like Tailwind or MUI, which is really something any developer could do, and many do. That’s why the job mostly died.
Even the most abstract of painters, fine artists, and so-on should have good fundamentals. They’ve gone through the discipline and developed taste, they don’t choose it from a library.
The CMU grad (using this as a stand-in now for any so-called educated hack, sorry CMU) is skipping all that and asserting personal authority without proving or living anything. And that shows IMO.
My probably unpopular opinion is that using AI can be very creative and you can get into flow states, and the quality of outputs vary by skill of the user.
I'm not sure I agree. I spent a good chunk of those years converting designer's PS sketches into CSS. Bootstrap and friends were a godsend, because even if standard design systems over-optimize for mobile, they are still far more functional than most designers's mediocre and incomplete views of user experience.
"Taste" is just knowledge. Advanced knowledge. Knowledge that is not easily put into words.
This is another restatement that knowledge, in a human head, is the determining factor of production, over land, labor and capital. This a post-capitalist argument that's been made for over 30 years (Peter Drucker in his 1993 book is my favorite), and it's been at least somewhat true even back to the 70s, just increasingly so as AI takes off.
The author's sidebar of AI or even cloud computing "taking ownership of the means of production away from workers" is entirely misunderstanding how the modern economy operates and shows how badly we need a new Marx (and Keynes, Schumpeter, or Drucker) since his analysis doesn't seem to provide the same analytical value in late capitalism. Renting vs. owning the means of production is now entirely a function of knowledge of the entrepreneurs (and their team).
Capital is ubiquitous now and is desperate for return - it remains powerful but is not all-powerful. We've had years of near-low interest rates and even after COVID inflation, they're still historically low. It is far more accessible to entrepreneurs than it has ever been in history, between grants, loans, subsidies, private equity, angels, crowdfunding, donations, etc. It's practically a cliche that billions in capital can be wasted on an initiative because the people involved had no idea what they were doing. I don't think AI changes that.
We don't need to rent our tokens, we can run open models on our local rigs (which still requires capital). We don't need to rent our servers, we can buy, rack and stack them on our own. Which we choose is fentirely dependent on the knowledge we have. If we don't know how to run an AI rig, we must rent it. If we don't know how to run a server, we must rent it. etc.
There are several walls driven by taste - Design - Testing - Production - Security - Scalability
In particular, the author seems confused on what "production" is. Production is still the wall. There was a joke on X the other day:
"I vibe coded my dream app! Try it out here: http://localhost:8080/coolapp"
Software running in production is not tokens. I'm sure properly prompted AI can deploy and run simple software in production but this requires a lot of knowledge to prompt to constrain it to run in a secure, scalable, adaptable way as complexity, scale, and capability grows.