The Future of Software Development - Vibe Coding, Prompt Engineering & AI Assistants

21 Jul 2025 · 44 min

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

Podcast Notes: The Future of Software Development - Vibe Coding, Prompt Engineering & AI Assistants

Overview This episode of the a16z Podcast discusses the evolving landscape of software development in the age of AI. Erik Torenberg interviews Martin Casado, Jennifer Li, and Matt Bornstein from a16z's InfraTeam, exploring the integration of AI into infrastructure and the resulting shifts in developer behavior, investment strategies, and the nature of technical users.

Key Themes

  • Emergence of AI as a Fourth Pillar of Infrastructure: AI is positioned as a foundational layer alongside compute, storage, and networking.
  • Evolution of Infrastructure: Infrastructure continually layers rather than disappearing, with AI adding complexity and new dynamics to software development.
  • Disruption of Software Development: The AI wave is fundamentally changing how software is developed and consumed, challenging traditional programming paradigms.

Detailed Notes

  1. Introduction to AI in Infrastructure
  2. Discussion of how AI integrates into the traditional pillars (compute, storage, networking).
  3. AI's role as a "fourth pillar" emphasizes the demand for advanced models and data processing capabilities.
  1. Historical Context
  2. Overview of past infrastructure developments from cloud computing to AI.
  3. Insights into how different waves (e.g., cloud, COVID) have reshaped industry practices and investment approaches.
  1. Impact on Software Development
  2. Traditional programming logic is being outsourced to AI models, challenging the role of programmers.
  3. Discussion on how AI models change the programming paradigm, requiring new ways of thinking about software logic.
  1. Investment Strategies and Market Dynamics
  2. AI is expanding total addressable market (TAM), attracting new behaviors and users.
  3. New business models are emerging; companies that previously thrived during past tech waves may not adapt to the new dynamics orchestrated by AI.
  1. Developer Tools and AI Integration
  2. The rise of tools aimed at improving developer efficiency and integrating AI capabilities.
  3. Introduction of "context engineering," emphasizing the importance of how prompts and data are structured for AI systems.
  1. Defensibility in the AI Landscape
  2. Discuss what makes AI companies defensible in a crowded market.
  3. Comparison of AI's current state to traditional infrastructure markets, identifying both opportunities and challenges.
  1. The Role of Founders and Industry Progress
  2. Founders need to adapt to new paradigms, leveraging AI effectively to stay competitive.
  3. Historical perspectives on the evolution of infrastructure highlight the importance of understanding past lessons.
  1. Phases of Expansion and Contraction
  2. Industry cycles of growth and consolidation influence market dynamics.
  3. Discussion on how investment strategies should adapt to different phases of the market.
  1. Future Trends in AI Models and Specialization
  2. Predictions about the evolution of AI models and the trend toward more specialized applications.
  3. Exploration of the "Decade of AI Agents" and the implications of this trend for software development.
  1. Horizontal vs. Vertical Integration in AI
  2. Analysis of which strategy might be more effective in the current landscape, with examples of companies successfully employing both strategies.

Conclusion The podcast concludes with a reflection on the transformative nature of AI in software development. The discussion emphasizes the need for professionals in the industry to adapt to these changes while remaining cognizant of the foundational principles of software creation.

Key Takeaways

  • AI is reshaping the infrastructure landscape, acting as a new foundational layer.
  • Traditional roles of software developers will evolve as AI takes on more logic-driven tasks.
  • The investment landscape is changing, requiring a fresh understanding of market dynamics and customer behaviors.
  • The future will see a blend of horizontal and vertical integration strategies as companies navigate the new AI-driven landscape.

Resources

  • Follow Martin Casado on [X](https://x.com/martin_casado)
  • Follow Jennifer Li on [X](https://x.com/JenniferHli)
  • Follow Matt Bornstein on [X](https://x.com/BornsteinMatt)
  • Stay updated with a16z via [Twitter](https://twitter.com/a16z) and [LinkedIn](https://www.linkedin.com/company/a16z).

---

These notes encapsulate the main points of the podcast episode, providing insights into the intersection of AI and software development, while highlighting the evolving nature of infrastructure and investment strategies in the technology sector.

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:00It's like faster than light speed travel has just been invented. For many of the developers and programmers I talked to today, they're like going to Disneyland just because how many great tools there are to help them move faster. We do spend a lot of time just trying to be very honest with ourselves or what has the new behavior been created where is this stuff getting used. Infrastructure never goes away, just gets layered. In this case, it's definitely all the infrastructure that we've been using and leveraging in the past are still very relevant, but it's definitely getting layered by having this fourth pillar.

0:28Software was always the destructor. One of the most exciting things about the AI wave is like, Software is being destructed. Like, we're being destructed. This is a pretty big deal. It's by far the biggest thing that I've seen happen sort of in my life. Is AI the fourth pillar of infrastructure? Today on the podcast, we're joined by Martin Casado, Jennifer Lee, and Matt Bordstein from A16Z's InfraTeam to unpack how infrastructure is evolving in the age of AI, from compute, storage, and networking to models, developer tools, and agents. We get into what info actually means today, how it differs from enterprise and why software itself is being disrupted.

1:03We also talk through the rise of technical users as buyers, what makes an infra company defensible, and how past info waves from cloud to covid to the current AI boom have shaped how we invest in build. Let's get into it. As a reminder, the content here is for informational purposes only. should not be taken as legal business, tax, or investment advice, or be used to evaluate any investment or security and is not directed at any investors or potential investors in any A16Z fund. Please note that A16Z and its affiliates may also maintain investments in the company's discussed in this podcast. For more details, including a link to our investments, please see A16Z .com forward slash disclosures.

1:49We're here today to discuss the state of Infra. First, can we get a definition 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. 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 think of the simplest possible level if you want software. Infra is what engineers are using behind the scenes 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.

2:21And if it's used by a technical user, we consider an infrastructure, whereas something like let's say vertical SaaS could be used by a flooring company or by a marketer or by sales, that would not be considered infrastructure. And technical user for the record is developer, data scientist, analyst, cybersecurity, professional. Yeah, right. There's a DevOps, right? there's a wide range of people. These are our people, right? Like the kind of nerds behind the scenes. And in the system terms, I think about it as compute, networking, storage, but also all the tooling that goes around the developer's day of what you're using to build software and what are the tools and products that are operating.

2:59These are growing in more complex software as well, all the way to semi -techno users that may want to either prototype or tinker with beauty applications. where we're very interested in anything in the technical domain and used by technical people. So you mentioned compute, networking, storage. How should we think about models? This is the fourth layer of info out of the interface. How should we think about that? I certainly think of it as a fourth layer of infrastructure. It's certainly leverage and build on top of all the three pillars we're talking about. It has a lot of demand of compute and of course it's trained and also producing a large amount of data.

3:33and to leverage and use these models for our purposes, latency and networking capabilities is also very important. But it's going to be as prevalent as any piece of infrastructure software. I don't know, like the analogy these days anymore. Is it a database? Is it sort of like a new form of a compute? So really to me, it's like a fourth pillar that incorporates everything, but also provides intelligence for the software we're using and doing today. Yeah. So I think this is exactly right. I think it's probably worth asking why a piece of infrastructure is a piece of infrastructure. And generally, a new piece of infrastructure changes the way that you program computers and it changes the stack that's around it.

4:11It's got different memory requirements. It's got different lanes and see requirements. So it just requires rethinking how we build software and how we build infrastructure. I would say in addition to compute networking storage, I would say distributed systems would also be included just because things like state consistency required to think about like proximity and guarantees. I would say databases probably did too because it changed our programming model. We have different guarantees. And these models very much fit in that for a couple of reasons. I think Jennifer is exactly right. Like you just build different data centers and different chips if you want to build these models.

4:43So it has that impact. But programming them is like non -obvious. Like we're just still trying to grapple like how you program them. Like they don't really listen to you. Sometimes they do the coding themselves. And if I were to try and to still like, what is the one biggest difference that these models provide to infrastructure? It's the following. I don't remember ever in the history of computer science where we've, from an application standpoint, we've abdicated logic. Like in the past, we've abdicated resources. Like you're like, give me compute, give me swords. Like these abstracted resources put the logic, the yes or no, like the what it's doing, always came from the programmer.

5:19But in these ones, we're like, come up with the answer for me. And so it's requiring us to rethink what does it mean to be a programmer? What does that mean to be software, et cetera? So it's clearly very fundamental to computer science. And I would say, again, to Jennifer's point, it's very, very much a new piece of infrastructure. And I think a lot of people are trying to reason by analogy. You sort of alluded to this, Jennifer. It's like, oh, is it like a database because it can answer queries? Or is it like a network? Because it's sort of non -deterministic. And we need to handle retries and weird edge cases.

5:48But I think people are really just trying to figure out how to program these things, which you sort of some, right, team. but like we've got a star from a blank sheet of paper, which is what makes our jobs like really exciting right now because there's a lot of people trying to figure it out and coming up with the ideas. Many of us have been in computer science for a long time, right? We've been in our schools and in our operating lives and in our investing lives. And like software was always the disruptor, right? Like we've disrupted taxis and we've disrupt like sales, we've disrupted the back office or we disrupt everything.

6:17Like one of the most exciting thing about the AI wave is like software is being disrupted. Like we're being disrupted, right? I just don't like that. I just don't like that. I just don't like that. I just don't like that. I don't like that. I don't like that. So we have to think of ourselves eating as we're right. Honestly, I think this is the first time I could honestly say that like the profession that I've dedicated my entire life to is being disruptive and it's very exciting because it's eating itself in a way. Yeah. And it's tempting to be a cramudge in, right? Because we've all been doing this.

6:44Oh, it's like really being open to and embracing the new stuff is like the key thing. What still applies is infrastructure never goes away. just gets layered. In this case, it's definitely all the infrastructure that we've been using and leveraging in the past are still very relevant, but it's definitely getting layered by having the support pillar, which is AI models. What's different from past super cycles? First of all, what can we learn as we enter this new one? So there's two things that happen. So one of them is often when you bring the marginal cost of something down, like with compute, we did it for computation and for the internet, we did it with distribution.

7:18it increases the tam a whole bunch. So for one, you almost always see this massive tam expansion. And part of that tends to be because the tam is bigger, you've got new users. And because you have new users, like there's normally like a new behavior that happens, right? This is very much the case with the internet, which is like people weren't used to going to a computer and talking to everybody around the world on top of the internet. And existing companies don't know really how to think about new behaviors. like they've built these sales motions and operating things around like the old behavior.

7:50And so you see Tam expansion, you see new behaviors, those new behaviors provide white space for challengers, new like startup companies to come and to go ahead and fill those models. And I think we're seeing exactly that happen with this one as well. Like clearly this market is massive. If you look at how successful these model companies are. But also you're seeing use cases that like computers just never really have done before and you're seeing that too. And so in that way, I think it rhymes very much with, say, the internet rhymes very much with probably even the microchip. Maybe I'll answer that question just from my personal experience.

8:20I'm always like sort of a tools person and also wanting to like having tools for filling certain creativity because I came to Codian Computer Science as a late bloomer after my 20s and really enjoyed all the tools available for me at that point of just building software and like learning computer science as well. Now we just have massive and massive leverage in trying to create anything as long as you have a good idea. Martín laughs at me about this. I was a bigger like local, no -co -chenthin for let's say the last five, ten years because again these are tools for people who have good ideas but may not be like educated in the computer science term but the retools of the world, the Wix and Squarespace's like you can build applications can be a software easily with these tools but now you're given like the next level of thought partners tools to really as any role in the company prototype, solve our interfaces for your end customer for end user as well as your knowledge they need or they want to see.

9:15Like you can really realize these ideas really quickly in like, your fingertips. So low code's finally happening. It just takes a lot of code. And it just turns out the code is natural language. And it was so funny because when Jennifer joined the team she was very excited about low code, but for my view, low code is like Python. I think it's like this. It's like going to be a violent, like, an anti -M is low -coated. You're right. So we kind of had to bridge that gap. And it was in a way like a bit irreconcilable until AI came out and it's very, very clearly. Like what the promise of low -code was.

9:45And so you're right, it really is disrupting software. So when I was a kid, right, the internet was sort of a new thing. I just remember really vividly, there was this movie with Sandra Bullock called the Net. And she orders a pizza from her computer. Yeah. And this is like completely mind -blowing. And like now, actually, this is a common user behavior. But like, what we're dealing with now is just so much bigger than that. Right? I just think it's really hard to, like I think some of these points about how will the infrastructure evolve, like how will the companies adapt and things like that are probably transferable.

10:14But this is a pretty big deal. It's by far the biggest thing that I've seen happen. So I'm going to slice. Let's zoom out and take this long view. And Martin, you're actually the perfect full circle because, where are you the first info investment ever as a portfolio founder? I think it was either me or Octa, but I will say Neon Todd were like the infreportful. One one LP days when they would trot us out in front of the LP's, it was like me and Todd from Octa. So for sure, I was one of the first two. At what point did we develop clear infrepractice at Aizenzea? So we always had strong infre people, right?

10:46So like Ben Horowitz is an infreq guy. And obviously I would say Mark is, like, he masquerades is a consumer guy, but he is actually I'm a revolutionized way we use computers in this deep infrastructure way. And by the way, many things came from that JavaScript, et cetera. We had Peter Levine, ZenSource, we had Scott Weiss. So there's always been deep infra. But when I joined the firm, we didn't think of it as ZenFra, we thought of it as enterprise, right? And so you're either in the consumer team, you're in the Fintech team, or you're in the Enterprise team. And the thing about just classifying the stuff as enterprise, the go -to -market motions for something that touches technology and being able to reason about that is so different than reaching to the go -to -market motion that's purely through like sales, right?

11:32And we've just learned over time that like, we do deep market diligence as a firm and we do deep diligence on companies before we invest in them and that the type of diligence we do if it was deep infrastructure just required a different type of junior partner and type of analysis. So over time we realized that companies where you can evaluate more by like the business model the market buyer, the unit economics, those kind of class of companies are just sufficiently distinct. So we decided to just pull them apart and then that's why we had the apps fun. And then of course, the InfraFun. If you think about enterprise, there is of course a horizontal piece of it, but also a lot of vertical enterprise where the applications buyers, sectors where infrastructure is almost always horizontal.

12:14And that's another thing we realize along the way if we still want to appeal to these technical audience and technical buyers, but we want to think about sort of this space in a horizontal fashion where these technology can be distributed to all these different sectors and verticals as well. And it impacts how we think about the stack, it impacts how we think about what is going to drive the form of like how the stacks integrate with each other, it's just like different from enterprise generally. Yeah, so it's actually very, very important distinction. I'm glad you brought it up. So like, technical buyers tend to be centralized buyers in a way, right?

12:46Like IT will buy compute network in storage. you've got the compute person, the networking person, but it kind of rolls up the IT. And developers are kind of a centralized buyer. So like you can understand IT, if you can understand the developers, but when I was looking at vertical SaaS apps, early in my investing career, to understand how to sell into a flooring company, you have to understand the flooring market. And that's entirely different than like the pet food market and that's entirely different than the construction market. And so I felt like there was no real central software buyer for these kind of verticals.

13:16So as you get further away from corner infrastructure, you get away from this notion of a centralized educated buyer, and just the level of analysis becomes very different. I think that's exactly right. And there's even sort of like the horseshoe theory of software buyers happening now, where you have like consumers over here, and then you kind of work up to like apps, and like you would think that Infra's way over here, but it's actually that doing back around, like 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 he is to.

13:43That's an incredibly important point. I was researching the stats the other day. When I first joined Venture, or maybe even just started thinking about infrastructure developers do like in the low tens of millions, and they're becoming like the next generation of consumers. Now they're definitely the next generation of consumers. It's going above 50 million on the way to even bigger than that now we're talking about natural language being a program in language for everybody. Like they are making decisions just as a consumer. So we're of course like turning ourselves to also understand how developers as individuals adopt tools, but also like IT buying centers as customers and enterprise organizations, like Evaluating Tools, so there's just a lot to learn and figure out given these are the technical audience we really care about.

14:24Yeah, I wanna get to how we think about our investible universe and what sort of subcategories are mature versus newer or sort of ripe, but before that, I want to better trace the evolution a little bit, so maybe more team we can start with you. If you had to categorize like since you've been investing, like the different waves of information, or like maybe the different inflection points at which it changed how we even thought about it. How would you characterize it? Let's just say for the lifecycle of the firm, so it was sort of 2009, and that was actually pre -cloud. And so a lot of the early investments were right in the cusp of cloud.

14:58And like, for example, my company, like, the cloud was out there, but it wasn't sufficiently deployed. You could use it as a core thesis. And a lot of the early investments were like this. And we talk about it in terms of tech, but it rips through the entire business model. like early software was on -prem with a perpetual license. That's just different economics and different analysis. The pre -cloud, installable software area was one, and then we saw the cloud transition. We went to recurring revenue, totally different deploying model, totally different operating model. During that time, we'd see things like net dollar retention being more important, expansion being more important, gross term being more important.

15:34It's margin. Gross margin being more important. Everything changed to that. By the way, meanwhile, of course, we saw consumer being disrupted by mobile, right, with the rise of the Ubers and the Lifts and the RB and Bs. And then again, we're seeing it happen again during this AI, which I would say, the AI transformation of the last three years has been the most dramatic. I've seen in the last 30 years of being in this industry. And there's one interesting blip along that path, which was COVID. We come from the realm of like enterprise sales and like being on the ground and the point things and like that totally evaporated.

16:07So like actually that was a dramatic shift as well, but it was driven by this kind of force measure as opposed to a secular technical wave like the other two did. I would say one of the benefit COVID brought is there was already the trend going of like developers buying and adopting tools like this bottom -up motion for infrastructure and for dev tools. It got accelerated during the COVID time where lots of people are just like tinkering, trying out products and tools and also more people building dev tools during that time. I feel like there was a flourishing ecosystem system just of these like PLG or product led DevTool companies that are giving birth to now we're seeing a lot of like AI DevTools are coming up.

16:45There's nothing developers like better than being forced to stay home, not attractive to other people. Right. This is like a real deal. That's new software. That's amazing. Okay. That's a good overview. Let's go deeper into the present a little bit. Can you guys share how we think about the different subcategories or landscape that kind to make up in from, we could also plug some examples of portfolio companies, spaces where we made some bets. Here's a few important categories. Developer tools, meaning anything developers use to make their lives better, easier, faster, more efficient. Cursor is probably our top developer tool company right now.

17:22And before that GitHub, right? Yeah, GitHub, we were in GitHub. So we've seen, very much. And Jennifer, you've actually backed a bunch of interesting DevTools companies in the last few years too. Yeah, from Lennie Fie, Stilis. There was a long time where the DevTools was written off by BC. Oh, yeah. The tam is too small. Yeah, it's here. I mean, at the time of GitHub, would you ever have imagined a repository who would be a huge company? Like, I was like, almost a joke, yeah. Right, and people are like, I'm like, business model, all these things. Small tam is the classic red flag for infra investing.

17:50If you're at home listening to this and someone tells you small tam, that they're not an infra investor. Infer creates tam. There's one takeaway from this thing, is tam creative. So yeah, so I think dev tools, you've got core infra, which is compute now, written storage, right? This is like, to IT. And then you tend to actually be quite a bit above the core infrastructure stacks. And maybe you talk through it, kind of the areas you focus on. I think about both like how developers are like easy and tools to improve their efficiency, but also how customers are getting a value out of that as well.

18:18So a lot of packaging, maybe depth tools into SaaS forms, like I mean, the industry is company called Pylon. It is a SaaS company that does customer support, but fundamentally is like doing a data pipeline. So that's like core infrastructure. That's very good at connecting with systems and providing contacts to a lot of like agents and AM models. So to me, that's infrastructure and we're spending a lot of time off course like the cutting -edge AI research So a lot of foundation modeling investing and we can probably numerate for the next 10 minutes of I will say the reason that we're a little bit skittish on this question is early in Supercycle, it's very hard to distinguish between an infrared company and the application companies and the reason is because the Tam is so small and so new the new technology becomes the app, right?

18:58Right, so let me refer to like the original super cycle that started the firm which is the internet like I remember when it came out, it was a consumer thing, or at least a student in school thing, right? And so this is one company, which everybody was downloading from an FTP server, Netscape, and using it as individuals. The enterprise didn't know what to think about it and banned it or whatever. And the same company that built JavaScript, that's building this core technology is also doing the browser. And over time it matures. And then of course you have all of these internet companies and all the applications show up.

19:31We're seeing the same thing in the AI wave. Like, is mid -journey, is that an infra company? They build a model or is that an app company? Well, it's both in this sense. And so I do think that at this stage, it's very hard to distinguish. It's exactly right. It's very hard to answer if OpenAI is an app company or is it an infra company. It already is building infrastructure. There's a cloud running these models for a different sector and different use cases. But at the same time, Build a consumer app that's TGPT. We think of Foundation Model Companies are similar. like 11 Labs, they're a voice app provider, and they have the creator application that can use the Studio2Crate voices.

20:07But at the same time, they're also supplying the voices to these large -scale enterprise use case that are fine -tuning, cloning, or own voice, and distributing that through API. So it's both. Yeah. Another area we've done a lot of work is data systems. And this goes all the way back to Databricks. And there's sort of been these two branches. One is this like kind of back -end data -enge driven, in big data systems, Spark, DUP sort of thing. And the other is this sort of data analyst, more tabular, snowflake kind of thing. And I think it's a firm, we've been super, super active and super aggressive, you know, on investing companies like Databricks, I mentioned five -trane, DBT, which you guys invested in together, Hex, which is doing really, really well, tabular, which was acquired by Databricks.

20:47So we're still, I think, really, really bullish on this. Unfortunately, hey, I had sucked the air out of the room for a lot of data companies from a bunch of different angles, but I think we'll continue to do more of this as well. How do we think about defensibility for AI companies, whether it's the app layer or the model layer, do they all have their respective areas of defensibility or how is it sort of a notion of defensibility evolved? So we once wrote a blog post that there was no defensibility anywhere in the stack. For anything, for anything. And yet people make lots of money. Yeah, and yet.

21:18You know, the argument at the time was like, okay, like Nvidia has sort of a moat because chip designs are hard to copy. But if you go sort of up or down, it's kind of like, okay, they're all sort of manufactured at the same place, right at TSMC. If you go down, if you go up, the cloud providers provide effectively the same product. Like the models are training on the same data and out of similar capabilities, the apps are all kind of like all using the same model. So to those sort of the naive theory, I think when we were just trying to understand this to be, any and I think maybe it was true at the time.

21:47Well, Martino is sort of alluding to a second ago is meanwhile, every company at every layer of the stack is doing like fantastically well right now. And during this initial phase of industry development, which we sometimes call the Brownian motion phase, I actually think it's really hard to make sort of pronouncements like this about what's gonna work, what's not gonna work, where's all you're gonna accrue, et cetera, et cetera. App companies are doing really, really well. And we're pretty clear past the sort of wrapper phase. I don't think there are any wrappers anymore. Building good products with AI is really hard.

22:16And the founders doing it now have really good intuition for how to do it. The models are clearly pushing the whole industry forward and they've built huge companies from that. So it's all working right now. And I think you could actually make a case for how defensibility will work. It's quite different from the way defensibilities work before. And maybe you guys want to add onto that. Yeah. And how defensibility work for infrared companies before largely, it's really hard to let's say, if you're building a new database, like a new framework, it just takes a lot of expertise in the domain of understanding what has happened in the past, where the field comes through, and what are the innovations that needs to happen to polish, let's say, a software into this new abstraction to provide to developers.

Read the full transcript

22:58Maybe one example I'm thinking of is like DuckDB. It's such a high performance, small, but really nimble database. It took four years for the team to write it. To replicate that is really hard. And that's generally what happened in the past in ProShactor Space. It takes these experts a lot of time to build a new piece of security software if it's UB keys or if it's, again, and like Databricks on Spark. But now as the AI infrastructure comes through, like I think a lot of those defensibility still stays and it's your true, because these are earned in the secrets of what are the downfalls and guarantees other software right into, where these founders know sort of the past and also looking into the future.

23:39But I do feel like the adoption phase is just like really massive, who is going to earn the distribution and earn sort of the developer attention is going to be a different game. Can I just do a quick mental model? What has suited me very well in thinking about this. I think the sloppyest thinking in our industry is around defensively. And I just were just so sloppy about it. And so maybe this is worth the price of listening to this podcast, like this mental model. So the industry tends to go through these expansion and contraction phases, thinking like the big bang or something, like it expands and then it contracts.

24:08So what happens when it expands? When it expands, zero sum thinking is deadly because you're just getting more market. We're clearly in an expands phase, right? Everybody is, oh, Nvidia can't like sell more chips, but they keep selling more chips. So like the hosting platforms can't continue to get margins, yet they keep continuing to get margins. I mean, that said it perfectly. I totally agree. So if you're in the expansion phase, then there's just more to sell. You should be aggressive investing. So what happens in the collapse phase? So look at any layer of the stack. So in the collapse phase, which things start to consolidate again, you have consolidation.

24:40But what is the end state of consolidation? The end state of consolidation will always be an oligopoly or a monopoly. It's not like the layers ever go away. If you have an oligopoly, say the clouds, then you have what's as effectively price fixing, but it's tacit, right? Which is everybody is like, we're gonna price it this, and we're gonna maintain a 30 % margins. So you still have value there, you have margins, or in the case of like a monopoly, you'll end up with say like an Intel at the time, then you can also maintain margins. So in none of this, do you lose margins, right? And I just think this is why people think so sloppy about this.

25:14Because people use the words like commoditization and no defense ability. That tends to be a battle between layers of the stack. But the only way you can do that is actually move down the stack and enter somebody else's layer, which is incredibly hard to do. And you do see it. So of course, Google is going to build their own chips and they start moving down the stack. But that's a very, very different layer than somehow Google playing the different layers off against each other. And so I would encourage anybody that does invest at least an infrastructure to not think zero sum and to realize that historically, every layer of the stack has maintained some level of value and margin.

25:50And if not, it was because a layer above them managed to verticalize themself, but then it's that one player against the rest of the world. Yeah, I mean, it's like faster than light speed travel has just been invented. Right. And we're sending all the spaceships out in all directions. And there's plenty of planets like in stars to claim for everybody. Like, you know, we're not even close enough to each other to like fight for the entire way. Yeah, for sure. Like, This is a shame. But it will, it will slow down and then the consolidation will happen. But I guarantee you'll just end up with these great companies that maintain margin.

26:19Like AWS still has great margins. Google still has great margins. I think you're growing at insane speed. Data bricks too is growing at an incredible speed for that. Let's go, let's go. I think people underestimate how hard these problems are in many cases. You're sort of applying consumer thinking because this is how we live most of our lives. It's like, oh, wouldn't it be relatively easy to move to a different part of the stack or take out your competitor or someone, a customer could just switch back and forth. And it's just different laws of physics, I think, and in front of. It just turns out in general, the switching cost of infrastructure piece is so much higher.

26:48Even with API business, if people tend to think you can just switch over to another API, there's so much logic embedded in calling the API in the software itself. There's a lot more switching costs compared to your regular SaaS software consumer. It's totally because you're actually integrating systems, right? It's not necessarily a person who can just have a preference for one thing or another you're sort of integrating. for sure. Sam Alman once had the advice to start up last year, he was like, if you're worried about us improving our models, you're in a tough spot. But if you get more excited about your business by us sort of improving our models, then you're in a good spot.

27:19Do you think that's a helpful framework? I think it's helpful for opening eye for you. You believe that? No, God. I'm sorry. I want to say that too. If you know, A16G, if you think us investing of this company isn't good for you, then. But if you want to buy from our company, That's our company, that's great. There's a very open question, that's actually a technical question, it isn't a business question, which is how much does general training generalize? So we know in the pre -training world, it generalized really well, so you create one model, and that model is just as good at code as it was at like writing a poem, right?

27:56So we know that it was very general, and in that world, sure, as the models get more powerful, then they can do all of the things, so they compete with all of the things, right? But it seems clear to me, and again, this is an observation, and it may not be correct, that as we get more into the RL world, that you make some trade -offs, and then let's say I RL something for code, it's not gonna be as good as something else, and like you're making these trade -offs, and in that world, then it's not the case that the model is gonna generally be good, so I think it's great to compete at the model layer.

28:26And so again, I think this is maybe a reasonable rubric, certainly for OpenEI to have people believe, Maybe a reasonable rubric if you believe that these models are going to be generally great, but I just don't think it holds up to how things are going to play out. This is a debate we had two years ago. I think whether the general model and the most capable model will rule or a lot of small medium -sized models that are very good at specific tasks that's going to be the future. It turns out both are true. Both, yeah. Well, we're talking about complex systems. You cannot just use one model that drives everything, at least not today, but you can compose very capable and powerful models to take certain tasks and also chain together processes from like processing document to like feeding in a model to have some reasoning and give you back, really clean and structure data to make decisions and put into your application to serve end users.

29:11Like that's a complex system. They invokes many model calls instead of just like one big models task. Did you guys have any reactions or is it worth talking at all about Carpothes talk? Did that framing resonate with you? Did you have any sort of differences of how you would frame certain things? One thing you mentioned is that he thinks it's not the year of agents, but the decade of agents, perhaps it's not as immediately upcoming as we might have thought. Probably should have talked about it more. There's something he said recently that I thought, and he's actually responding to somebody else that I thought is actually very insightful.

29:44I actually thought his talk was great, but I thought his talk was kind of an overview of what a lot of people know. I thought it was pretty good general overview. I saw the tweet today about who knows how old it was. So this idea of Prompt Engineering that people have talked about. And somebody, it wasn't Carpathy, but Carpathy piled on top is it's really not about prompt engineering as context engineering. So what is context engineering? So if you're going to call a model, you have to know what to put in the context in that prompt. And what tools do you have to do that? Well, you can use other models, but at some point you're probably going to use traditional computer science.

30:18You're going to use things like indexes, you're going to do prioritization, et cetera. And to really drive the best performance out of those models, you do want the context to be correct. And I do think it's probably the right framing of this problem. And the next step is in as much as we're going to provide formalism to how to use these models, to how to use existing tools, to how do you improve the performance, you should be thinking about what's the right way to get the right context into those models. And I bring this up because, like we said before, new infrastructure pieces create new patterns and new methods of software and building systems.

30:52And this is a great example of that kind of emerging before our eyes and people are raising about it. I truly believe in five years of look back will come up with a whole new set of formal ways to build software and they will have strong guarantees and will understand them and there will be all the tools for it, etc. The way I think that relates to our world is if you think about what is the new form factor of infrastructure that needs to become part of this context engineering. It goes back to a lot of what we're obsessed about it with data pipeline. How do you feed the right data and context into the models or into the context and how do do you have agencies use tools or an infrastructure that will provide a discovery and guarantees the observability of these tools as well?

31:30Like it's the classic infrastructure problem that's still unsolved, so it's very exciting time. There's a few different types of infra founders, right? There's this sort of infra -founder who loves solving really messy, long tail, like nasty problems, right? There's the type that kind of just gets fed up with a problem and they're like, I'm gonna solve this finally, I'm sick of this. And there's the type that just sees the world in a new way, right? and it's kind of like this is actually how we should marshal these resources. And like react is a great example of this. We had all these like kind of progression of front end development frameworks and finally react was like the way that stuck.

32:04And for years now it's been sort of the default front end. So like I think what Carpoth he's talking about is trying to figure that out, right? And I think it's talked about 2 .0 thing was really interesting. We were investing in a bunch of like traditional ML companies at the time. And I think Salvador 3 .0 I think he's sort of right about that too in sort of directionally. And my hope is it'll inspire a lot of new and profounders to do this work, see the world in a new way, and figure out how these primitives should really be arranged. One of the difficulties of having any conversation on AI is it just exploits this weakness in the human imagination to dump all of our fears and hopes and dreams into this anthropomorphic fallacy.

32:41And this goes all the way back to the Promethean legend. And so let's talk about even this context, right? We're building systems to build other systems, so systems have constraints, right? And so you can fail on either side of this when it comes to this anthropomorphic fallacy. On one side, you can be like, this stuff doesn't work. You shouldn't use it. You should only use traditional things, which, okay, that's clearly not the case. It seems very useful. But on the other side, you can like, believe they'll solve all of our problems and you don't need formalism and you just kind of, like go to the beach and you come back when HGI is done and it'll do it for you type thing.

33:14And so part of our job, and what we spend a lot of time talking about is trying to find that pragmatic, non -blinkered, non -pessimistic middle, despite all of the rhetoric. And then you hear all the rhetoric, right? The stuff is gonna like, no, we're not gonna have to work and we're all gonna be on the beach. Yeah. Right? Or, you know, I get a kill, it's like the whole thing. And I think where we've landed is, This is a real disruption. It's just changing all of software. It'll look something place different, but it is still going to require professionals. And I do think that the statement, it'll require professionals is a very meaningful one.

33:52It means that you actually still need people that understand the specifications of the systems. And not everybody agrees that some people are out there like, listen, you will never need a programmer again, because people are beginning to just say some high level thing and it'll show up. And the only one statement I'll say to that is formal systems came out of natural languages for a reason. And like, either you care about specifying what you're designing or you don't, and if you do, you need to be a professional. And that's why every professional disability, but they started with a natural language has ended up with a formal system.

34:23What is your mental model on coding specifically? Will there be like fewer engineers who are just higher powered? I think the best way to think about this is simply that we're going to have more developers. I think it's very unlikely that we're going to shrink development teams because we have amazing new tools. That's just not how these markets have worked in the past. I think exactly the opposite is going to happen. It's like we're going to be creating so much great software. It's going to be so accessible to so many people who may work at a big company or may just be sort of hacking on the weekend.

34:52I think that's by far the simplest way to think about it. It gets back to Martin's point of you can't answer for more files these models. A model is a file on a hard drive in a computer somewhere. When you run a Python script, you can transform one piece of data into another piece of like that's what this is. And programming is a fundamentally creative job, right? You are literally creating things in the most strict sense of the word, which is your creating software it doesn't exist before. And that's something only a person can actually do at some level of abstraction. So I personally think this is a huge boom for programmers and you have to change the way that you're working.

35:26And it's like a huge productivity boost. And I think that creates more not less. I cannot agree more. I feel like for many of the developers and program as I talk to today, they're like going to Disneyland, just because how many great tools there are to help them move faster, like build things they have always wanted to do on both set projects and also their main job. I do think it also changes the dynamic of like how people are picking up new languages, picking up new frameworks. And it is again a next level of iteration speed given what we're seeing with AI agents and also AI coding tools. Here's another I think useful mental model and this stuff.

36:01Like I think it's worth asking the question, why do people buy software? Like, why does someone buy some random SaaS tool? Is it because it's so hard to build it? No. Like, most SaaS tools are like crud. Like, they're just these basic kind of read -write databases. They're all the same. So, why do people buy them? And Aaron Levy, who's the CEO of Box, I think, said they're so beautifully, the reason people buy software is because somebody else made the decisions of what the workflow should be and what the operational logic should be and what data is important, how use that data is important. Like creating a product is a lot of understanding what is being used and guiding the user along that direction.

36:41So if not, I'll just give you a compiler, look you do whatever you want and I'll just give you a database and you do whatever you want. There's a reason that we have a proliferation of vertical SaaS and it is this kind of articulation or this transfer of domain understanding and that just doesn't go away independent of how you create the software. And so we will still need to design products based on whatever problem is being solved, guide people so that they're the most effective with them and they can understand the best. And we did this with assembly before and then we did it with high level languages and then we did it with high level frameworks and then we're going to do it with AI, but like the fundamental process of that articulation will not go away.

37:19And it's totally orthogonal to creating the software itself. It turns out to be a much harder problem to go out and collect requirements from an unknown set of users with an unknown set of needs. And figuring out what to build, that turns out to be much harder than actually building. So what do you think is the average number of lines changed in the PR in the industry? Two. Yeah. What it shows you to the point, like it literally is understanding the need from the business and the need from the user and making some minor tweak. That is the long tail that goes into software. By the way, it turns out it's two.

37:49Well, I think it's a median. It's the median is two. I've written a lot of like, GTRs of my life. Just for the record, by the way, Martin said, Crud, Crud is a technical term, right? Create, read, update, delete. We actually think, applications are great. We don't think they're crudgy. They just, they're just crudgy. Yeah, crudgy. Just hit a footnote. I'm sorry, good to know. Jennifer, you were mentioning earlier how two years ago we were having this debate on generalization. And what are the debates we're having now? Internally, or with your peers, or what are the main questions that we're asking that we can't wait to see how they're going to reveal themselves the next few months or next year that are going to impact our business.

38:24Gosh, every week is different. What are some of the recent ones? Definitely, how realistic are agents today, like, really producing production level software? That's more on the coding agent side, but also in general, like the agent evolution. Where are we going from demoware to producing real value, tangible value? What are some other ones? Synthetic data is when we talk about a lot. We've been talking about for 10 years. Yeah, this is so great about info. You can have the same debates, pretend, here's the number one. It's like just the background. It's like everything else. Yeah, consistency versus availability.

38:57Literally every system has this trade off. So this synthetic data thing, right? It's almost an information theory question. It's like, can you make models meaningfully better without introducing new information to the system? And I think it's now pretty clear you can do a little bit. But the question is, does this lead to sort of like a self -improving utopia of models or not? And I think we have some pretty strong opinions on the not side of that. Generalization, Martin mentioned, is a pretty interesting one. If you train a model to be really good at math, does that mean it's going to be really good at other things, or is it just like really good at math, which I get excited about.

39:25Not everybody gets excited about this. Another one that we talk a lot about is like what these things are actually good for, just because the path we came from used a lot of AI, pre -gen AI used a lot of AI. So there's a lot of AI -shaped holes in the enterprise, like chatbots and this and that. And that's very much on the brain. And it seems to sometimes confuse the discussions from the new use cases we're seeing. Like, if you look at the most common use cases of something like chat GPT, I think the top one is like companionship and therapy and then it's like managing my schedule. It's like the top of the pyramid of need stuff.

39:57And the number five is professional development, not like low -code development or whatever. And so I think what is happening is we have this idea of what we thought AI was gonna do and like just kind of distilted attempts previously. I mean, Jennifer actually ran product for a chat company prior. And then what it really is good for, and clearly there's some overlap in convergence, but it's not nearly as big as people say. And so we do spend a lot of time just trying to be very honest with ourselves, what has the new behavior been created, where does this stuff getting used? What is it just been trying to cram into places that's not actually quite good at?

40:30To that point, how do we think about agents right now? What are they good for, going to be good for soon enough, what is the state of them, how do we think about the broader conversation? Coding agents are awesome. They're amazing. It's really amazing. So I have a very simple way to think about this. And I'm like the anti -agent guy, by the way, I think it's kind of a marketing thing. This is the other thing about infrared people. We like are like allergic to marketing, which is not always a good thing. Which is a good thing you're here, Eric. That's all that's what you mean. Yeah, exactly. Yeah, can you explain?

40:57If you take the simplest definition that basically an agent is an LLM running in a loop, a very simple way to think about this is errors propagate throughout the loop. So if you have a small error, it gets worse and worse. And this is why a lot of agents doing, say, general web browsing don't perform very well yet. On the flip side, if you have a way to correct those errors in the loop, which is one thing that you have in code, right? You can land, you can interpret, you can try to compile and things like that. You actually do see good performance over time. So that's very simplistic and maybe not quite the right way to look at it.

41:28But like, if you can do this kind of correction, I think you're seeing a lot of sort of improvement from this iterative approach. I'm amazing, credible. I'm actually on the, like, get a male enlist of a lot of the companies that I work with just mostly for interest. And I have even in the last week seen a bunch of kind of cursor like agent commits. And like even in the last 24 hours, the slack integration, seeing it come from slack. And so I do think for kind of bite size tasks, you can articulate very well. We're starting to see them really work. So in the coding space, I would say I'm a convert.

42:01But to Matt's point, like the, you know, go wander out in the woods and bring back a bear. I think we're going to be wasted. There's a lot of air in the future. We see more vertical integration or more horizontal specialization. You know, historically we've seen both and what's interesting is we're already seeing both now, right? Apple, of course, has just been historically vertically integrated. Microsoft and Intel historically horizontally. And often companies will start horizontal and then go vertical. So Google is horizontal. I built on top of normal servers, but then they built their servers.

42:37And then they built their own chips. They built their own networking gear. And so I think you always get a mix of the two. What's interesting about now is we're actually really seeing both. I would say that OpenAI is very much a vertically integrated company now with ChatGPT driving a lot of it. I would say Anthropic. A lot of the usage really is more horizontal. And they're doing a great job of that. I think we're seeing this on the model layer too. A very interesting discussion we haven't had. But it's a very interesting one. It's like open source quote unquote really seems to work with these models just because you can't as a user recreate it.

43:06So we look at BFL. They've done a great job building like a horizontal layer for these models. But then you've got companies like Ideogram, which have built a great kind of vertical experience as well. And so say for AI, we've got already this early on great examples of both. And I don't see any reason that that will change. Yeah. I think from the business front, it just poses new interesting questions and challenges too of how do you capture the value? Of course, horizontal to capture the value through. Being able to address every single use case by providing that to developers or enterprises, but if you're working with an integrated kind of have to pick the lane of doing a focus on image model, say do I want to focus on graphic designers, do I want to focus on people who are generating photography, you have to understand the market and the user personeness use case is pretty well to capture the maximum value where you probably can take an easier path to just provide API so everybody can use it.

43:54I think it's a great place to wrap. Guys, thanks so much for coming one of the podcasts and then stay there for having us. Thank you. This is fun.

44:02Thanks for listening to the A16z podcast. If you enjoyed the episode, let us know by leaving a review at ratethispodcast .com slash A16z. We've got more great conversations coming your way. See you next time.

From the publisher

Is AI the Fourth Pillar of Infrastructure?

Infrastructure doesn’t go away — it layers. And today, AI is emerging as a new foundational layer alongside compute, storage, and networking.

Erik Torenberg interviews a16z’s Martin Casado, Jennifer Li, and Matt Bornstein breaking down how infrastructure is evolving in the age of AI — from models and agents to developer tools and shifting user behavior.

We dive into what infra actually means today, how it differs from enterprise, and why software itself is being disrupted. Plus, we explore the rise of technical users as buyers, what makes infra companies defensible, and how past waves — from the cloud to COVID to AI — are reshaping how we build and invest.

 

Timestamps: 

(00:00) Introduction 

(01:49) Defining Infrastructure in the AI Era

(03:15) The Fourth Pillar: AI's Role in Infrastructure

(06:01) Historical Context and Evolution of Infrastructure

(08:20) The Impact of AI on Software Development

(10:18) Investment Strategies and Market Dynamics

(17:02) Developer Tools and AI Integration

(20:57) Defensibility in the AI Landscape

(22:16) Founders' Intuition and Industry Progress

(22:26) Defensibility in AI Infrastructure

(24:00) Expansion and Contraction Phases in the Industry

(24:35) The Role of Layers in Market Consolidation

(27:43) The Future of AI Models and Specialization

(29:27) The Decade of AI Agents

(29:54) Context Engineering and New Infrastructure

(34:23) The Evolution of Software Development

(42:13) Horizontal vs. Vertical Integration in AI

(43:54) Conclusion and Final Thoughts

 

Resources: 

Find Martin on X: https://x.com/martin_casado

Find Jennifer on X: https://x.com/JenniferHli

Find Matt on X: https://x.com/BornsteinMatt

 

Stay Updated: 

Let us know what you think: https://ratethispodcast.com/a16z

Find a16z on Twitter: https://twitter.com/a16z

Find a16z on LinkedIn: https://www.linkedin.com/company/a16z

Subscribe on your favorite podcast app: https://a16z.simplecast.com/

Follow our host: https://x.com/eriktorenberg

Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.

Stay Updated:

Find a16z on X

Find a16z on LinkedIn

Listen to the a16z Podcast on Spotify

Listen to the a16z Podcast on Apple Podcasts

Follow our host: https://twitter.com/eriktorenberg

 

Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.


Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

More from The a16z Show

All 489 episodes
The Future of Software Development - Vibe Coding, Prompt Engineering & AI AssistantsThe a16z Show · 44 min
Listen in VO