A sibling [dead] comment to mine is a rebuttal to "just post the prompt", where it itself was expanded to several paragraphs that each say nearly nothing, including this gem:
> "That’s not a critique of the writing. It’s a diagnosis"
I miss when people just typed their thoughts concisely and hit send without passing it to an inflater. I'd maybe have a chance of understanding the sibling comment's point.
This isn't mind control, just language evolution quiety nudged by AI. ;)
We trained a model on human language which is now in the business of itself retaining human language.
- use an LLM to compress a blog article into a singular prompt
- Run it through against all the major LLMs to have them expand it back out again
- Diff the original against the generated versions in terms of content/ideas
- Spit out an "entropy ranking".
Maybe I need to stop reading AI posts and thinking that it's good writing? But will take the feedback on board and try not to over analyse each paragraph - it was a lot messier upon first draft but maybe ready better I guess.
Planning on writing a lot more this year.
It made me think of the conductor, seemingly the most skillless job in the orchestra. All you do is wave the batton, no need to ever play a instrument. If LLMs are doing the hard part (writing code) then we can be the conductor waving the batton.
But of course the visuals are misleading. Being conductor doesn't take the least skill, it takes the most. He hears every instrument individually, he knows the piece intimately, and through his conducting brings a unique expression to a familiar work.
LLMs have made the musician part automated. They'll play whatever you want. No doubt a powerful tool in the hands of a skilled conductor. And a incredible tool for someone who can't play to generate music for themselves.
There's no shortage of "I built it and they won't come" posts here on HN, predating LLMs by decades. Because code has never been the hard part of "software as a business ". LLMs have driven this point home. Code has never been cheaper. Business has never been harder.
But there are many ways to apply LLMs in the development flow.
Only specifying features broadly is like a product manager might is definitely highly luck dependent wrt how buggy it will turn out.
But understanding the feature and determining what needs to be done broadly, then ask the LLM to do so and verify after if the resulting change makes sense according to your mental model of the software is definitely not that.
Also, I disagree with your implied message. I frequently struggle to articulate solutions even if I know how they'd work
This should apply to art even more, because art is strongly supported by emotions - and people may know the feeling of the emotion (of the image), but not have an explicit framework for it yet
The OG definition of Vibe Coding is just playing a client who wants $thing, but doesn't need how to write a line of code.
https://x.com/karpathy/status/1886192184808149383?lang=en
He knows how to code, as such your personal definition does not agree with how the term was coined.
Now, 1 year later and people interpret a lot into the term.
in that context I could accept your perspective to that term, but it's certainly not the original meaning
I like your metaphor even as someone who can be a bit skeptical of the overly broad promises of LLM’s/AI. But I do think this statement is too generous. It implies way too much actual musical ability. It also means that everything I can imagine musically is possible which it just isn’t, as there are limitations just like with real musicians.
If we want to really make the metaphor work, it’s an orchestra full of very informed people who have read a lot about music and have an idea of what their instrument should sound like and can even make whatever they’re holding sound like the appropriate instrument most of the time sort of. With our direction, our “conducting,” their success goes up.
But ultimately: they aren’t real musicians, they aren’t holding the right instruments, and they haven’t actually been taught how to read music. They are just often good at sort of making it work in a way that approximates what we want.
But I think the analogy holds (from an output point of view), the musicians will continue to improve, and some sections play better than others. The overall effect is "pleasing" although perhaps not concert quality.
So what you wrote does not bode well for the profession.
So those musicians are no longer getting booked for that bit of music. Instead, one person produces it in their home studio. But, there’s now an industry for creating software tools that support that workflow, and there are a lot more opportunities for such music than there used to be. The amount of music used in background spots on television is astounding.
Things changed. Some jobs diminished (studio players?) or went away altogether (music copyists?). But new work came into existence.
Will there be new software like that? Maybe, but you'll never hear about it. Not only because it's throwaway code, but because the best interface is probably no code at all. The chatbot will instead spin up a VM behind the scenes and never even show the code it generated unless you dig for it.
I wonder if there’s any parallel to that in software?
It's a deeply unpopular opinion around here, but if a human has to interact with anything that's where most of the effort and budget is going to go. They're still the "rock stars".
That skill set is not merely writing code. It's more about collaboration with all the stakeholders and making a ton of deliberate decisions and compromises. It doesn't matter how "good" an LLM is at writing code for the web. That's subjective, and that's my point. We've had all kinds of no-code solutions for a very long time.
An experienced frontend dev is necessary when the project isn't just for other devs or internal use.
Unfortunately, for junior engineers the CS path has likely become more arduous, and we'd probably see something more of a doctor-like career path for CS students, where they specialize to obtain deeper architectural knowledge, before receiving employment.
I agree with the gist of your comment, but I have to push back on the above statement. Conducting an orchestra is a different skillset than playing virtuoso violin, but it is not more difficult or more important. Its just different. The same applies to any leadership or management position. A very skilled orchestra can in even hide the fact that the conductor is a bit crap. Same with a company or sports team performing so well that they overcome the weaknesses of a lackluster manager. Even though they will still often get the credit.
Really though? That seems completely wrong.
If a conductor's job can be reduced to a metronome, why hasn't it? I've had a credit card sized metronome in my instrument case for 15 years. Most professional musicians carry metronomes. We've had perfectly accurate metronomes for something like 500 years, so why is "conductor" a profession at all?
Google, Apple, Meta, X, Bluesky, Shopify, Stripe and all the big software companies must be really shaking in their boots for disruption against the army of vibe coders. /s
(They are actually laughing at all of them)
All of the mentioned named companies have network effects, distribution and trust.
Not quite easy to copy. Disposable LLM gen'd code without users is cheap, which is the point of the article.
Yes but not for the reason you think - more that those are the future customers. If you look closely most are pivoting slowly away from software and shifting more to AI + hardware. The slow layoffs and pivoting that capital to infra shows this. All that "vibed" software needs to run somewhere. Also the models that generate and also power all that software need compute which comes from somewhere.
If I can:
- Have large margin compute since GPU's, power, data centre, etc setup is expensive AND
- Models that outperform models you can have at home.
- Vibed software that derives a lot of functionality from the AI compute and wants to be hosted on compute.
The big companies are pivoting away from software to being more infrastructure like for the democratized software that is projected to be made. They will be fine but in 10 years they will be more cloud hyperscalers, AI compute agents, etc than software businesses. Any software they write will be more to package up their compute as higher margin products.
None of this IMV gives any hope to current SWE's.
Another way to reify this is:
When making software, remember that it is a snapshot of
your understanding of the problem. It states to all,
including your future-self, your approach, clarity, and
appropriateness of the solution for the problem at hand.
Choose your statements wisely.But really the only issue is it's monotone linkedin still insight fluff and you can't tell where the prompt ends and the LLM crap begins. I expect something interesting was put into the LLM, but the LLM has destroyed the author's ability to communicate it with me effectively. Everything is overinflated to the same level of importance and I can't tell what the author actually cared about expressing.
I had this in the old version of my site that I refreshed in the last 2 months and forgot to take the RSS feed with me, thanks for the reminder!
You model inference provider and any intermediaries get to watch what you’re designing from behind the curtain and copy, train on, or sell the insights if you’re not paying attention.
Even if, I would only trust local models.
Will the bubble pop and wipe out progress? Will this be a boon or bust for humanity? Who knows. In any case, the future's so bright, I gotta wear shades ;).
It looks like LLM-supported coding becomes the new SaaS. The more things change, the more they stay the same.
sublinear•3w ago
Yes! This is 100% it.
This is a net good for everyone because it brings basic programming literacy to the masses and culls a lot of junk projects that are littering github or SaaS scams.
It means people can focus on the problems that actually matter.
AI doesn't have any impact on the need for accountable humans to write code.
The scratchpad analogy is so good. Most mature business software is almost literally like a tome of legal documents that have to be edited carefully, but that doesn't have anything to do with the napkin in your pocket.
polishdude20•3w ago
Not only is it taking way more energy to write software now with LLMS than by "hand", now everyone is repeating work many times over to write the same tools.
From a freedom standpoint one could argue is gives the user the most freedom to have what they want and need. But its very bad from an energy efficiency point of view.