I saw someone use the term "orchestration", which seems to be the word for building the software using LLM tools.
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.
I agree, and the corollary of this would be that the most senior engineers (who might be at a staff/principal level at a given company) who have the most amount of domain knowledge, deep understanding of various software architectures, and a product/customer oriented mindset may stand to benefit the most from AI-assisted coding, despite some narratives being peddled around by executives that they could do without senior engineers.
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.
This "orchestration" software is about people trying to increase productivity by running many instances of a coding agent on the same project, without stepping on each other too much. It doesn't seem to be fully baked yet. A "shared nothing" architecture where you work have each instance work on a distinct project seems simpler if you want to spin more plates.
> LLMs have made the musician part automated. They'll play whatever you want
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.
So then why did MIDI not replace musicians and conductors many decades ago? Why do we even bother thinking in terms of sheet music, or programs in terms of code?
It kinda sorta did. Decades ago, all music was played by live players. Today, there are lots of albums, lots of background music on television, radio, etc., that is made mostly or entirely using MIDI-controlled virtual instruments. No longer do you need to book an actual chamber orchestra for a little 30-second spot on some cooking show.
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.
Can't read this every paragraph ends with it's not x it's y. Just give me the prompt so I can read the real insights you have and not the generated fluff.
I randomly skipped to five different paragraphs and each one ended with a "!x but y" logical statement, just formatted differently most of the time. Crazy how you can't unsee it.
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.
The "barrier to entry for building software" has not collapsed, as it was never about "where engineering shifts from writing code to shaping systems". It has always been about understanding the problem to solve and doing so in a provably correct manner.
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.
We are all fashion designers now. LLM can code the cloth, do the seams, put in zippers, and sow buttons. You pick what creature you are designing for. You study how it moves, where the limits of movement lie, where it needs ventilation, flexibility, extra reinforced knees, fire resistance, a cape for flare (or no cape for safety). We are all Edna Mode. And the best of us can turn the problems we are working on into superheroes.
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.
In other words, yes we have CNC machines and electric saws and whatnot, reliable to a certain degree (you can still injure yourself badly), but it doesn't remove the need of a carpenter, because a carpenter also knows how to make a hammer from scratch even if he doesn't make one in his entire life.
When you pay for anything you basically exchange money so that someone else take care of a problem you have. Obviously if you are paying you expect the result to be of good quality. Software is no different, AI won't change that fact and engineering is about creating robust solution at the cheapest price. Just my 2 cents.
solving problem should be an obsession rather than building. AI have fueled way too many builders while edge cases and lifecycle maintainence of the code is more of an afterthought
If building is easy enough, it's often OK that it's not perfect because you can just as easily fix problems as they arise if it's just for your own personal use. And making software just for your own personal use can now actually make sense wheras it would more often be a complete waste of time to do by hand.
> People are increasingly building tools to solve a single, specific problem exactly once—and then discarding them. It is software as a disposable utility, designed for the immediate "now" rather than the distant "later."
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.
In a way it's good but as far as energy usage goes, it sucks.
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.
For the love of all that is holy, I cannot read another 5 page AI post that could've been like 200 words. Just make it a paragraph or two and write using your brain, people. Does everything have to be ran through an AI? I'm sure there's some decent ideas in here, but I'm not wasting my time reading this slop.
A title per paragraph (slight exaggeration), half of the form The X, The Y, The Z. Every section ends with "it's not x; it's y" contrast framing.
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.
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
Why would any big software company need to care? There are so many small businesses with unique problems with no current off-the-shelf software solutions because they've always been too niche to justify the time and expense of bespoke development. Now that door is open. Big software companies can keep servicing big businesses and mass markets, while opportunities abound for anyone else willing to innovate on smaller problems. Not everything needs to be built to scale.
What a random set of companies to choose. You'd probably need to think critically about each one of those when assessing the accuracy of your statements.
I saw someone use the term "orchestration", which seems to be the word for building the software using LLM tools.
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.
Vibecoding is the feeling of coding. It's the same feeling people have when they say they can see the picture in their head, but can't quite draw it.
But also the market for conductors is very small. There are 100 musicians but only one conductor in an orchestra.
So what you wrote does not bode well for the profession.
I agree, and the corollary of this would be that the most senior engineers (who might be at a staff/principal level at a given company) who have the most amount of domain knowledge, deep understanding of various software architectures, and a product/customer oriented mindset may stand to benefit the most from AI-assisted coding, despite some narratives being peddled around by executives that they could do without senior engineers.
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.
This "orchestration" software is about people trying to increase productivity by running many instances of a coding agent on the same project, without stepping on each other too much. It doesn't seem to be fully baked yet. A "shared nothing" architecture where you work have each instance work on a distinct project seems simpler if you want to spin more plates.
> LLMs have made the musician part automated. They'll play whatever you want
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.
So then why did MIDI not replace musicians and conductors many decades ago? Why do we even bother thinking in terms of sheet music, or programs in terms of code?
It kinda sorta did. Decades ago, all music was played by live players. Today, there are lots of albums, lots of background music on television, radio, etc., that is made mostly or entirely using MIDI-controlled virtual instruments. No longer do you need to book an actual chamber orchestra for a little 30-second spot on some cooking show.
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.
Can't read this every paragraph ends with it's not x it's y. Just give me the prompt so I can read the real insights you have and not the generated fluff.
I randomly skipped to five different paragraphs and each one ended with a "!x but y" logical statement, just formatted differently most of the time. Crazy how you can't unsee it.
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.
Now it is a tell but eventually people may natutally start speaking like this!!
This isn't mind control, just language evolution quiety nudged by AI. ;)
Yeah it's becoming increasingly obvious now. The moment I see this "contrast framing" I stop reading.
I read this as 'contrast farming' and like the term better.
That's not just contrast framing. It's contrast farming.
This made me think of:
- 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".
Thanks for saving me from reading it myself.
we just need to send the article back to the LLM to get it synthesized /s
The "barrier to entry for building software" has not collapsed, as it was never about "where engineering shifts from writing code to shaping systems". It has always been about understanding the problem to solve and doing so in a provably correct manner.
Another way to reify this is:
We are all fashion designers now. LLM can code the cloth, do the seams, put in zippers, and sow buttons. You pick what creature you are designing for. You study how it moves, where the limits of movement lie, where it needs ventilation, flexibility, extra reinforced knees, fire resistance, a cape for flare (or no cape for safety). We are all Edna Mode. And the best of us can turn the problems we are working on into superheroes.
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.
In other words, yes we have CNC machines and electric saws and whatnot, reliable to a certain degree (you can still injure yourself badly), but it doesn't remove the need of a carpenter, because a carpenter also knows how to make a hammer from scratch even if he doesn't make one in his entire life.
eh, rather, a carpenter knows to swing a hammer in a pinch, doing say framing, even if they mostly use a nailgun.
Man. This post reminded me I wanted a Firefox extension for switching between tabs using Q and E. I got it done in like 15 min and moved on.
So many nice blogs showing on HN, and no RSS feed. Seems like most are on github pages, that should be a feature over there.
When you pay for anything you basically exchange money so that someone else take care of a problem you have. Obviously if you are paying you expect the result to be of good quality. Software is no different, AI won't change that fact and engineering is about creating robust solution at the cheapest price. Just my 2 cents.
Turns out taste and judgement still matter. Weird.
solving problem should be an obsession rather than building. AI have fueled way too many builders while edge cases and lifecycle maintainence of the code is more of an afterthought
If building is easy enough, it's often OK that it's not perfect because you can just as easily fix problems as they arise if it's just for your own personal use. And making software just for your own personal use can now actually make sense wheras it would more often be a complete waste of time to do by hand.
If your job is to write code, you are being replaced. If your job is to use technology to solve problems, your job just got a lot more interesting.
And if you make this distinction, you don't understand the operations of the business.
> People are increasingly building tools to solve a single, specific problem exactly once—and then discarding them. It is software as a disposable utility, designed for the immediate "now" rather than the distant "later."
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.
In a way it's good but as far as energy usage goes, it sucks.
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.
For the love of all that is holy, I cannot read another 5 page AI post that could've been like 200 words. Just make it a paragraph or two and write using your brain, people. Does everything have to be ran through an AI? I'm sure there's some decent ideas in here, but I'm not wasting my time reading this slop.
you won't get clicks and you can't build brand with it. sad but true.
This post is AI generated slop.
I thought it seemed like an especially good read!
What makes you think it is?
A title per paragraph (slight exaggeration), half of the form The X, The Y, The Z. Every section ends with "it's not x; it's y" contrast framing.
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.
You're absolutely right!
> The barrier to entry has effectively collapsed.
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)
Why would any big software company need to care? There are so many small businesses with unique problems with no current off-the-shelf software solutions because they've always been too niche to justify the time and expense of bespoke development. Now that door is open. Big software companies can keep servicing big businesses and mass markets, while opportunities abound for anyone else willing to innovate on smaller problems. Not everything needs to be built to scale.
What a random set of companies to choose. You'd probably need to think critically about each one of those when assessing the accuracy of your statements.
> What a random set of companies to choose.
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.