Episode summary
The Future of Software Development - Vibe Coding, Prompt Engineering & AI Assistants
The a16z Show
· · Hosts: Erik Torenberg · Guests: Martin Casado, Jennifer Li, Matt Bornstein
Summary
The conversation frames AI as a fourth foundational layer of infrastructure, alongside compute, storage, and networking. The speakers argue that models are not just another application feature: they change how software is built, how systems are architected, and even what it means to program, because developers are increasingly asking models to generate answers rather than just supply resources.
A central theme is that infrastructure never disappears, it gets layered. The speakers connect past waves like the cloud, mobile, and COVID-era tooling shifts to today’s AI cycle, arguing that each wave expands the market, creates new user behavior, and opens room for new companies. They also stress that developers are becoming a larger and more consumer-like buying audience, which changes distribution, product design, and go-to-market.
The discussion is skeptical of simplistic narratives around defensibility, agents, and generalization. The speakers say models will likely remain heterogeneous, with strong systems for specific tasks rather than one universal model. They also argue that agents are already useful in constrained, well-instrumented environments like coding, while broader autonomy still suffers from error propagation. Overall, they see AI as a major software disruption that increases demand for technical professionals rather than eliminating them.
Key takeaways
- The speakers say AI models are a fourth infrastructure layer because they change programming, latency, data, and system design, not just application behavior.
- The host and guests argue that AI is expanding the TAM for infrastructure and developer tools, creating new user behavior and new categories of startups.
- The speakers say defensibility still exists in infrastructure, but in AI the bigger prize is distribution and developer attention rather than simple technical moats.
- The guests think agents are working best in environments like coding where errors can be corrected in the loop, but remain weak in open-ended tasks.
- The speakers expect more developers, not fewer, because AI tools raise productivity and make software creation more accessible.
- The guests argue that future models will likely be specialized across tasks, making “one model for everything” an unreliable assumption.
Notable quotes
“infrastructure never goes away. It just gets layered”
“From an application standpoint, we've abdicated logic. This is a pretty big deal”
“Software was always the disruptor. One of the most exciting thing about the AI wave is like software is being disrupted”
“I think the best way to think about this is simply that we're going to have more developers”
How the episode opens
Infrastructure never goes away. It just gets layered. A new piece of infrastructure changes the way that you program computers and it changes the stack that's around it.
We're building systems to build other systems. Developers are making a lot of the decisions and a lot of the like marketing and sales to developers looks more like consumer these days than it used to. Who is going to earn the distribution and earn sort of the developer attention is going to be a different game.
From an application standpoint, we've abdicated logic. This is a pretty big deal. It's by far the biggest thing that I've seen happen sort of in my life.
Software was always the disruptor. One of the most exciting thing about the AI wave is like software is being disrupted. Like we're being disrupted, right?
And so we're like disrupting software is eating software. I know. I know.
We're like, hey guys, we're here today to discuss the state of Infra. We've done a consumer podcast. We we've done a consumer team.
We've done it with AD team. Now we're excited to do it with the infra team. First, can we get a definition of of infra?
Where does infra differ from enterprise? How do we think about it internally? I would say infra is basically what makes software work, right?
We'll probably get pretty deep into a set of technical definitions. You mentioned sort of networking, storage, compute. Where does AI fit into that?
But I I think at the simplest possible level if you want software, infra is what engineers are using behind the scenes to to make all this possible. And our formal definition internally is technical buyer, right? So it's the stuff you use to build the stuff, the stuff you use to build apps.
From the episode’s captions: roughly the first two minutes, lightly cleaned. Keep watching on YouTube →
Topics
- ai infrastructure
- vibe coding
- prompt engineering
- ai developer tools
- synthetic data
Companies and tickers mentioned
- MSFT
- OpenAI
Watch the episode
Summary, takeaways and quote selection by Octagon. Quotes are short excerpts; the full conversation is in the episode.
More from The a16z Show
-
How AI Could Bring Halo and Other Classic Games Back to Life -
Mike Volpi on Why AI Infrastructure Will Outlast the Hype Cycle -
Why HubSpot’s Co-Founder Is Betting Against the SaaSpocalypse -
Inside Salesforce’s Acquisition Strategy for the AI Era -
How AI Is Turning Figma’s Finance Team Into Builders -
The New AI Agents That Shop, Plan, and Gossip
The a16z Show, this episode and its artwork belong to Andreessen Horowitz. Octagon is not affiliated with the show; this page is an independent summary.
