alt Hacker NewsYou made my day with this line =P.
tbh I have been struggling with the state of software in the agentic era. I'm pro LLM, there's undeniable leverage in its coding abilities. I do want to write this post! I'll start with hopefully this distillation:
In the agentic era, if shipping code is a commodity, then why ship more code? we can say this for the entire concept of "build" - we've commoditized building anything software related, i don't understand how this translates to therefore BUILD MORE.
So then the more nuanced conversation is that taste and judgement is the leverage. i agree with this. But its hand wavy in that we can't agree on what taste is. and also accelerationists hold true that all can be encoded. more agents. i don't even disagree with this entirely.
What I'm missing is that AI-native software engineers are going to brute force their way to PMF, to judgment, taste, enlightenment, consciousness.
But why is this a straight line? Just add more agents. add a "designer", a "sales" and "user researcher" agent. just add more agents.
You don't know what you don't know, is my retort. It's surreal to me that we're living through the equivalent of the smartest software engineers effectively giddily prompting, with full conviction mind you, "add more pop!" to make their thing better.
Just needs more pop!
Replies
Man, I completely agree with your thinking here. I've been trying to be more active in online communities, to try to discuss this exact idea.
LLM code can be leveraged, but pretending that tokens are just going to turn into money printers at some point is not productive. The primary source of software's value to an end user is the thought that was placed into it. Where does that go for the AI-natives? As you say, they are seemingly brute forcing software engineering, at least so far.
One thing I have been considering is how LLMs primarily change the "build vs buy" calculus for a fair number of software niches, particularly things like developer tooling and small libraries and packages. Partially due to a projected increase in supply chain attacks, and partially due to the changing standards of engineers. There's no longer anything stopping someone from working with an ugly or clunky syntax, presuming it's a well documented standard. So many "developer experience" tools are going to hit this - Tailwind primarily comes to mind.
It's a sort of "erosion" of niches in the current landscape - although to me this does not really work out for the worse in the long term, since again, the thinking in the process will need to just go somewhere else.
You’re welcome! At least I did something productive with my day :-)