I feel like this isn't adequately accounting for the fact that existing software is becoming easier to refactor as well. If someone wants a 3d modelling program but is unsatisfied with the performance of some operation in Blender, are they going to vibe code a new modelling program or are they going to just vibe refactor the operation in Blender.
> I debated with Claude endlessly about this selection model, and Claude made me discard a bunch of interesting but less defensible claims. But in the end, I was able to convince Claude it’s a good model
This is one of those instances where bullshit takes more effort to debunk than it does to create.
We already went over how Stack Overflow was in decline before LLMs.
SaaS is not about build vs. buy, it's about having someone else babysit it for you. Before LLMs, if you wanted shitty software for cheap, you could try hiring a cheap freelancer on Fiverr or something. Paying for LLM tokens instead of giving it to someone in a developing country doesn't really change anything. PagerDuty's value isn't that it has an API that will call someone if there's an error, you could write a proof of concept of that by hand in any web framework in a day. The point is that PagerDuty is up even if your service isn't. You're paying for maintenance and whatever SLA you negotiate.
Steve Yegge's detachment from reality is sad to watch.
> Friction_cost is the energy lost to errors, retries, and misunderstandings when actually using the tool. [...] if the tool is very low friction, agents will revel in it like panthers in catnip, as I’ll discuss in the Desire Paths section.
This is why I think Ruby is such a great language for LLMs. Yeah, it's token-efficient, but that's not my point [0]. The DWIM/TIMTOWTDI [1] culture of Ruby libraries is incredible for LLMs. And LLMs help to compound exactly that.
For example, I recently published a library, RatatuiRuby [2], that feeds event objects to your application. It includes predicates like `event.a?` for the "a" key, and `event.enter?` for the Enter key. When I was implementing using the library, I saw the LLM try `event.tilde?`, which didn't exist. So... I added it! And dozens more [3]. It's great for humans and LLMs, because the friction of using it just disappears.
EDIT: I see that this was his later point exactly! FTA:
> What I did was make their hallucinations real, over and over, by implementing whatever I saw the agents trying to do [...]
[0]: Incidentally, Matz's static typing design, RBS, keeps it even more token-efficient as it adds type annotations. The types are in different files than the source code, which means they don't have to be loaded into context. Instead, only static analysis errors get added to context, which saves a lot of tokens compared to inline static types.
[1]: Do What I Mean / There Is More Than One Way To Do It
Holy fuck is this guy blowing smoke up his own ass.
He needs an editor, I’m sure he can afford one.
I look forward to him confronting his existence as he gets to be as old as his neighbor. It will be a fun spectacle. He can tell us all about how he was right all along as to the meaning of life. For decades, no less.
I'm frankly exhausted from AI takes from both pessimists and optimists--people are applying a vast variety of mental models to predict the future during what could be a paradigm shift. A lot of the content I see on here is often only marginally more insightful than the slop on LinkedIn. Unfortunately the most intelligent people are most susceptible to projecting their intelligence on these LLMs and not seeing it: LLMs mirror back a person's strengths and flaws.
I've used these tools on-and-off an awful lot, and I decided last month to entirely stop using LLMs for programming (my one exception is if I'm stuck on a problem longer than 2-3 hours). I think there is little cost to not getting acquainted with these tools, but there is a heavy cognitive cost to offloading critical thinking work that I'm not willing to pay yet. Writing a design document is usually just a small part of the work. I tend to prototype and work within the code as a living document, and LLMs separate me from incurring the cost of incorrect decisions fully.
I will continue to use LLMs for my weird interests. I still use them to engage on spiritual questions since they just act as mirrors on my own thinking and there is no right answer (my side project this past year was looking through the Christian Gospels and some of the Nag Hammadi collection from a mystical / non-dual lens).
where these tools really shine is in the hand of someone who knows what they want soup-to-nuts, knows what is correct and what is not, but just doesn't want type it all out and set it all up. For those people, these tools are a breath of fresh air.
I remember reading a comment a few days ago where someone said coding with an agent (claude code) made them excited to code again. After spending some time with these things i see their point. You can bypass the hours and hours of typing and fixing syntax and just go directly to what you want to do.
Too many people are running a LLM or Opus in a code cycle or new set of Markdown specs (sorry Agents) and getting some cool results and then writing thought-pieces on what is happening to tech.. its just silly and far to immediate news cycle driven (moltbot, gastown etc really?)
Reminds me of how current news cycle in politics has devolved into hour by hour introspection and no long view or clear headed analyis -we lose attention before we even digest that last story - oh the nurse had a gun, no he spit at ICE, masks on ICE, look at this new angle on the shooting etc.. just endless tweet level thoughts turned into youtube videos and 'in-depth' but shallow thought-pieces..
its impossible to separate the hype from baseline chatter let alone what the real innovation cycle is and where it is really heading.
Sadly this has more momentum then the actual tech trends and serves to guide them chaotically in terms of business decisions -then when confused C suite leaders who follow the hype make stupid decisons we blame them..all while pushing their own stock picks...
Don't get me started on the secondary Linkedin posts that come out of these cycles - I hate the low barrier to entry in connected media sometimes.. it feels like we need to go back to newspapers and print magazines. </end rant>
I've been using Claude and it's a game changer in my day to day. The caveat being of course that my tasks at a small "feature" level and all interactions are supervised. I see no evidence that this is going to change soon...
My other thought, that I can't articulate that well is....what about testing? Sure LLMs can generate tons of code but so what? If your two sentence prompt is for a tiny feature that's one thing. If you ask Claude to "build me a todo system" the results will likely rapidly diverge from what you're expecting. The specification for the system is the code, right? I just don't see how this can scale.
Some interesting long-term, directional ideas about the future of software dev here but the implied near-termness of SaaS being disintermediated ignores how management in large orgs evaluates build vs buy Saas decisions. 'Build' getting 10x cheaper/easier is revolutionary to developers and quite possibly irrelevant or only 'nice-to-have' to senior management.
Even if 10x cheaper, internally built Saas tools don't come with service level agreements, a vendor to blame/cancel if it goes wrong or a built-in defense of "But we picked the Gartner top quadrant tool".
Isn’t this a form of what he labels the “human coefficient”?
Some businesses prefer tools built by other businesses for some tasks. The author advocates pretty plainly to identify and target those opportunities if that’s your strength.
I think his point is to recognize that’s moving toward a niche rather than the norm (on the spectrum of all software to be built).
Steve Yegge used to be a decent engineer with a clear head and an ability to precisely describe problems he was seeing. His "Gooogle Platform Rant" [1] is still required reading IMO.
Now his bloviated blogposts only speak of a man extremely high on his own supply. Long, pointless, meandering, self-aggrandising. It really is easier to dump this dump into an LLM to try to summarize it than spend time trying to understand what he means.
And he means very little.
The gist: I am great and amazing and predicted the inevitable orchestration of agents. I also call the hundreds of thousands of lines of extremely low quality AI slop "I spent the last year programming". Also here are some impressive sounding terms that I pretend I didn't pull out of my ass to sound like I am a great philosopher with a lot of untapped knowledge. Read my book. Participate in my meme coin pump and dump schemes. The future is futuring now and in the future.
>I debated with Claude endlessly about this selection model, and Claude made me discard a bunch of interesting but less defensible claims. But in the end, I was able to convince Claude it’s a good model
Convinced an LLM to agree with you? What a feat!
Yegge's latest posts are not exactly half AI slop - half marketing same (for Beads and co), but close enough.
I'm not convinced of this post's hopeful argument near the end. If you are doing SaaS as a way of making money and don't have a deep moat aside from the code itself, it will probably be dead in a few years. The AI agents of the future will choose free alternatives as a default over your paid software, and by the way said free alternatives are probably made using reliable AI agents and are high-quality and feature complete. AI agents also don't need your paid support or add-on services from your SaaS companies, and if everyone uses agents, nobody will be left to give you money.
As a technical person today, I wouldn't pay a $10/month SaaS subscription if I can login to my VPS and tell claude to install [alternate free software] self-hosted on it. The thing is, everyone is going to have access to this in a few years (if nothing else it will be through the next generation of ChatGPT/Claude artifacts), and the free options are going to get much better to fit any needs common enough to have a significant market size.
You probably need another moat like network effects or unique content to actually survive.
He spends a lot of words talking about how saving cognition is equivalent to saving resources, but seems to gloss over that saving money is also saving resources.
Given the token/$ exchange rates is likely only going to get better for actual money over time...
If his predictions come true it seems clear that if your software isn't free, it won't get used. Nothing introduces friction like having to open up a wallet and pay. It's somewhat telling that all of his examples of things that will survive don't cost money - although I don't think it's the argument he meant to be making given the "hope-ium" style argument he's pushing.
---
Arguably, this is good long term. I personally think SaaS style recurring subscriptions are out of control, and most times a bad deal. But I also think it leaves a spot where I'm not sure what sort of career will exist in this space.
I'm not a business dude but even I can see one problem in his argument: He tacitly equates "agents use your software" with "your software survives". But having your software invoked by an agent doesn't magically enrich you. Up to now, human users have made software success by one of:
1. Paying money for the software or access to it.
2. Allowing a fraction of the attention to be siphoned off and sold to advertisers while they use the software.
I don't think advertisers want to pay much for the "mindshare" of mindless bots. And I'm not sure that agents have wallets they can use to pony up cash with. Hopefully someone will figure out a business model here, but Yegge's article certainly doesn't posit one.
Microsoft CEO said in a podcast they are preparing for the moment the biggest paying customers for Windows, Office and their cloud products will be agents, not humans.
In big orgs, 'agents can build it' rarely changes the buy vs build decision. The pragmatic moat I see isn’t the code, it’s turning AI work into something finance and security can trust. If you can’t measure and control failure-cost at the workflow level, you don’t have software.
> First let’s talk about my credentials and qualifications for this post. My next-door neighbor Marv has a fat squirrel that runs up to his sliding-glass door every morning, waiting to be fed.
Some of the writings here feels a little incoherent. The article implies progress will be exponential as matter of fact but we will be lucky to maintain linear progress or even avoid regressing.
Here's what I don't get about the "AI can build all software" scenario. It extrapolates AI capabilities up to a certain, very advanced point, and then, inexplicably, it stops.
If AI is capable enough to "build pretty much anything", why is it not capable enough to also use what it builds (instead of people using it) or, for that matter, to decide what to build?
If AI can, say, build air traffic control software as well as humans, why can't it also be the controller as well as humans? If it can build medical diagnosis software and healtchare management software, why can't it offer the diagnosis and prescribe treatment? Is the argument that there's something special about writing software that AI can do as well as people, but not other things? Why is that?
I don't know how soon AI will be able to "build pretty much anything", but when it does, Yegge's point that "all software sectors are threatened" seems to be unimaginative. Why not all sectors full stop?
"If you believe the AI researchers–who have been spot-on accurate for literally"
I do not understand what has happened to him here... there was an entire "AI winter" in the 90's to 2000's because of how wrong researchers were. Has he gone completely delusional? My PhD supervisor has been in AI for 30 years and talks about how it was impossible to get any grant money then because of catastrophically wrong predictions had been.
Like, honest question. I know he's super smart, but this reads like the kind of ramblings you get from religious zealots or scientologists, just complete revisions of known, documented history, and bizarre beliefs in the inevitably of their vision.
It really makes me wonder what such heavy LLM coding use does to one's brain. Is this going to be like the 90's crack wave?
"These systems are, in a meaningful sense, crystallized cognition, a financial asset, very much like (as Brendan Hopper has observed) money is crystallized human labor."
The latter part of this sentence is basically the labor theory of value. Capital Vol. 1 by Karl Marx discusses this at length deriving the origin of money, though I believe others like Ricardo and Smith also had their own versions of this theory.
43 comments
[ 6.0 ms ] story [ 62.2 ms ] threadI'd recommend starting with Stratechery's articles on on Platforms and Aggregators[0], and a semester long course on Porter's Five Forces[1].
[0]https://stratechery.com/2019/shopify-and-the-power-of-platfo...
[1]https://en.wikipedia.org/wiki/Porter%27s_five_forces_analysi...
This is not a good way to do anything. The models are sychophantic, all you need to do in order to get them to agree with you is keep prompting: https://www.sfgate.com/tech/article/calif-teen-chatgpt-drug-...
We already went over how Stack Overflow was in decline before LLMs.
SaaS is not about build vs. buy, it's about having someone else babysit it for you. Before LLMs, if you wanted shitty software for cheap, you could try hiring a cheap freelancer on Fiverr or something. Paying for LLM tokens instead of giving it to someone in a developing country doesn't really change anything. PagerDuty's value isn't that it has an API that will call someone if there's an error, you could write a proof of concept of that by hand in any web framework in a day. The point is that PagerDuty is up even if your service isn't. You're paying for maintenance and whatever SLA you negotiate.
Steve Yegge's detachment from reality is sad to watch.
This is why I think Ruby is such a great language for LLMs. Yeah, it's token-efficient, but that's not my point [0]. The DWIM/TIMTOWTDI [1] culture of Ruby libraries is incredible for LLMs. And LLMs help to compound exactly that.
For example, I recently published a library, RatatuiRuby [2], that feeds event objects to your application. It includes predicates like `event.a?` for the "a" key, and `event.enter?` for the Enter key. When I was implementing using the library, I saw the LLM try `event.tilde?`, which didn't exist. So... I added it! And dozens more [3]. It's great for humans and LLMs, because the friction of using it just disappears.
EDIT: I see that this was his later point exactly! FTA:
> What I did was make their hallucinations real, over and over, by implementing whatever I saw the agents trying to do [...]
[0]: Incidentally, Matz's static typing design, RBS, keeps it even more token-efficient as it adds type annotations. The types are in different files than the source code, which means they don't have to be loaded into context. Instead, only static analysis errors get added to context, which saves a lot of tokens compared to inline static types.
[1]: Do What I Mean / There Is More Than One Way To Do It
[2]: https://www.ratatui-ruby.dev
[3]: https://git.sr.ht/~kerrick/ratatui_ruby/commit/1eebe98063080...
We are entering the absurd phase where we are beginning to turn all of earth into paperclips.
All software is gonna be agents orchestrating agents?
Oh how I wish I would have learned a useful skill.
That sounds pretty hyperbolic. Everyone? Next “wave”?
He needs an editor, I’m sure he can afford one.
I look forward to him confronting his existence as he gets to be as old as his neighbor. It will be a fun spectacle. He can tell us all about how he was right all along as to the meaning of life. For decades, no less.
I've used these tools on-and-off an awful lot, and I decided last month to entirely stop using LLMs for programming (my one exception is if I'm stuck on a problem longer than 2-3 hours). I think there is little cost to not getting acquainted with these tools, but there is a heavy cognitive cost to offloading critical thinking work that I'm not willing to pay yet. Writing a design document is usually just a small part of the work. I tend to prototype and work within the code as a living document, and LLMs separate me from incurring the cost of incorrect decisions fully.
I will continue to use LLMs for my weird interests. I still use them to engage on spiritual questions since they just act as mirrors on my own thinking and there is no right answer (my side project this past year was looking through the Christian Gospels and some of the Nag Hammadi collection from a mystical / non-dual lens).
I remember reading a comment a few days ago where someone said coding with an agent (claude code) made them excited to code again. After spending some time with these things i see their point. You can bypass the hours and hours of typing and fixing syntax and just go directly to what you want to do.
Too many people are running a LLM or Opus in a code cycle or new set of Markdown specs (sorry Agents) and getting some cool results and then writing thought-pieces on what is happening to tech.. its just silly and far to immediate news cycle driven (moltbot, gastown etc really?)
Reminds me of how current news cycle in politics has devolved into hour by hour introspection and no long view or clear headed analyis -we lose attention before we even digest that last story - oh the nurse had a gun, no he spit at ICE, masks on ICE, look at this new angle on the shooting etc.. just endless tweet level thoughts turned into youtube videos and 'in-depth' but shallow thought-pieces..
its impossible to separate the hype from baseline chatter let alone what the real innovation cycle is and where it is really heading.
Sadly this has more momentum then the actual tech trends and serves to guide them chaotically in terms of business decisions -then when confused C suite leaders who follow the hype make stupid decisons we blame them..all while pushing their own stock picks...
Don't get me started on the secondary Linkedin posts that come out of these cycles - I hate the low barrier to entry in connected media sometimes.. it feels like we need to go back to newspapers and print magazines. </end rant>
My other thought, that I can't articulate that well is....what about testing? Sure LLMs can generate tons of code but so what? If your two sentence prompt is for a tiny feature that's one thing. If you ask Claude to "build me a todo system" the results will likely rapidly diverge from what you're expecting. The specification for the system is the code, right? I just don't see how this can scale.
Even if 10x cheaper, internally built Saas tools don't come with service level agreements, a vendor to blame/cancel if it goes wrong or a built-in defense of "But we picked the Gartner top quadrant tool".
Some businesses prefer tools built by other businesses for some tasks. The author advocates pretty plainly to identify and target those opportunities if that’s your strength.
I think his point is to recognize that’s moving toward a niche rather than the norm (on the spectrum of all software to be built).
Now his bloviated blogposts only speak of a man extremely high on his own supply. Long, pointless, meandering, self-aggrandising. It really is easier to dump this dump into an LLM to try to summarize it than spend time trying to understand what he means.
And he means very little.
The gist: I am great and amazing and predicted the inevitable orchestration of agents. I also call the hundreds of thousands of lines of extremely low quality AI slop "I spent the last year programming". Also here are some impressive sounding terms that I pretend I didn't pull out of my ass to sound like I am a great philosopher with a lot of untapped knowledge. Read my book. Participate in my meme coin pump and dump schemes. The future is futuring now and in the future.
[1] https://gist.github.com/chitchcock/1281611
Steve Yegge has always read a bit "eccentric" to me, to say the least. But I still quote some of his older blog posts because he often had a point.
Now... his blog posts seem to show, to quote another commenter here, "a man's slow descent into madness".
Convinced an LLM to agree with you? What a feat!
Yegge's latest posts are not exactly half AI slop - half marketing same (for Beads and co), but close enough.
As a technical person today, I wouldn't pay a $10/month SaaS subscription if I can login to my VPS and tell claude to install [alternate free software] self-hosted on it. The thing is, everyone is going to have access to this in a few years (if nothing else it will be through the next generation of ChatGPT/Claude artifacts), and the free options are going to get much better to fit any needs common enough to have a significant market size.
You probably need another moat like network effects or unique content to actually survive.
He spends a lot of words talking about how saving cognition is equivalent to saving resources, but seems to gloss over that saving money is also saving resources.
Given the token/$ exchange rates is likely only going to get better for actual money over time...
If his predictions come true it seems clear that if your software isn't free, it won't get used. Nothing introduces friction like having to open up a wallet and pay. It's somewhat telling that all of his examples of things that will survive don't cost money - although I don't think it's the argument he meant to be making given the "hope-ium" style argument he's pushing.
---
Arguably, this is good long term. I personally think SaaS style recurring subscriptions are out of control, and most times a bad deal. But I also think it leaves a spot where I'm not sure what sort of career will exist in this space.
LOLWUT?
Counter-factual much?
1. Paying money for the software or access to it.
2. Allowing a fraction of the attention to be siphoned off and sold to advertisers while they use the software.
I don't think advertisers want to pay much for the "mindshare" of mindless bots. And I'm not sure that agents have wallets they can use to pony up cash with. Hopefully someone will figure out a business model here, but Yegge's article certainly doesn't posit one.
Some of the writings here feels a little incoherent. The article implies progress will be exponential as matter of fact but we will be lucky to maintain linear progress or even avoid regressing.
If AI is capable enough to "build pretty much anything", why is it not capable enough to also use what it builds (instead of people using it) or, for that matter, to decide what to build?
If AI can, say, build air traffic control software as well as humans, why can't it also be the controller as well as humans? If it can build medical diagnosis software and healtchare management software, why can't it offer the diagnosis and prescribe treatment? Is the argument that there's something special about writing software that AI can do as well as people, but not other things? Why is that?
I don't know how soon AI will be able to "build pretty much anything", but when it does, Yegge's point that "all software sectors are threatened" seems to be unimaginative. Why not all sectors full stop?
Operational excellence survives, no matter the origin.
I do not understand what has happened to him here... there was an entire "AI winter" in the 90's to 2000's because of how wrong researchers were. Has he gone completely delusional? My PhD supervisor has been in AI for 30 years and talks about how it was impossible to get any grant money then because of catastrophically wrong predictions had been.
Like, honest question. I know he's super smart, but this reads like the kind of ramblings you get from religious zealots or scientologists, just complete revisions of known, documented history, and bizarre beliefs in the inevitably of their vision.
It really makes me wonder what such heavy LLM coding use does to one's brain. Is this going to be like the 90's crack wave?
I know this doesn't 'contribute to the discussion.' But seriously this guy's latest contribution to the world was a meme coin backed project...
The latter part of this sentence is basically the labor theory of value. Capital Vol. 1 by Karl Marx discusses this at length deriving the origin of money, though I believe others like Ricardo and Smith also had their own versions of this theory.