Welcome back to Turpentine VC, the podcast where we discuss the art and science of building successful venture firms, VC to VC. This week we're releasing an interview with a16z's Martin Casado, which originally aired on the Cognitive Revolution, hosted by Nathan Levens, a few months ago. Martin is a general partner at Andreessen Horowitz, where he leads the firm's $1.25 billion infrastructure practice. In the conversation ahead, Martin and Nathan discussed the complexity of AI systems and their differing views on AGI and regulation. The discussion covers topics like model scaling laws, biological AI applications, the state of self-driving cars, and AI safety concerns. The debate also captures the key uncertainties the tech industry is grappling with as these technologies advance. Please enjoy the episode.
Martin Casado, general partner at a16z, welcome.
I think this is going to be a great conversation. We are primarily here to talk about the importance of open source and to dig into a lot of the details of the current debates around early regulation of AI and how that might impact open source and what the pros, if any, and cons, if potentially many, of that might be. Before we get into it, I just wanted to get a little bit of your super big-picture AI worldview and ask you to project out a little bit. How powerful do you think AI is going to be over the next couple of years? You know, we've obviously heard AGI 2027. Is that a story you're buying? What do you think we're going to see over the next two to three years?
Listen, I think like all things, the past is probably the best predictor of the future. My hope is this continues to be a very useful tool to help us with progress and to stave off this universe that seems pretty destined on killing us. So I'm hoping it continues on that trajectory. What is interesting is if you actually look, let's say, the past 80 years of quote-unquote AI, it's been steady progress independent of there being winters and summers. It's been very, very steady progress. There's been progress on economics, some problems solved, and every time we tackle a problem, like everybody's, oh goodness, this is it, we're almost at AGI, and then it just turns out like that's one modality, and then we go on to the next and we say, oh, that wasn't really actually AGI or AI. So like this whole AGI thing has been a moving goalpost for 70 years. And so I would say, listen, there's been this kind of very steady progress. We've gotten good at many things. It's been a very useful tool. I hope it continues to be so. I think it's a very important thing for us to continue to develop and use, but I don't think that there's any step change or it changes the nature of computers or software in ways that we haven't seen before.
So let me just ask a few more concrete things because I'm a big believer in threshold effects. I mean, the topics of emergence, you know, super hotly debated, and is emergence a mirage or not a mirage? And maybe the underlying curves are smooth, but in terms of like practical utility, even if the capability of the model hasn't taken a sudden shift, the utility and what it can actually practically do in the world sometimes seems to take a notable leap. I guess right now, I thought Dario put this really well on a recent podcast where he said, like, it seems like the models are token for token as smart as most people, and yet there's some things that they're missing. Like they don't have this great long-term memory or the ability to integrate memories. They're not great at autonomy. They fall down and can't get back up or don't know how to dust themselves off. But it seems like the core intelligence is there to do a lot of jobs, and it's this packaging, memory, agentic finishing that's needed to get to the point where you'd have like this sort of knowledge worker. Is that basically the story that you see? And I mean, does that translate to, I think AGI is, yes, certainly very ill-defined, but like drop-in knowledge worker that could do a large majority of jobs like passably well is maybe better defined. Do you see that coming soon?
So again, I think I'd like to draw from a historical analogy because I think they're very useful in this context because I just feel like we've seen these very often and they all look kind of the same and it's played out. And so when I first joined Stanford to do my PhD, so I did my PhD in computer science and systems, was in 2003, and around then, I don't know, it was 2003 or 2004, Sebastian Thrun had won the DARPA Grand Challenge. So the DARPA Grand Challenge is he drove a van autonomously, fully autonomously for 1,200 miles, and everybody was like, hooray, like AGI is solved, robo-taxi is solved, this is an amazing thing. And 100%, we've hit one of these threshold moments, 100%, like you could actually do things you couldn't do before. It was the start of a new era of vision and perception and self-driving. And now 20 years later, and about a hundred billion dollars invested, a little bit less than a hundred billion dollars invested, the unit economics of self-driving are still three times worse than Uber. And so I am a systems person, meaning all I've been doing for the last 30 years of my life is building computer systems, large distributed systems. This is what I do. And I just know that scale and capabilities, they're not necessarily parametric, so they don't necessarily just go up and to the right. And there's so many examples of this, and we can talk about that. I know that the universe is this very heavy-tailed system, and there's no single solution that tends to reign in its complexity. I know that the economics for these things are very, very hard. Like what gets lost in these conversations is AI has been better than humans for a very long time at many things: handwriting detection, diagnosis for a very long time, game playing for a very long time, mathematics since the creation of the computer, four orders of magnitude better at mathematics than us. And yet none of these things have resulted in kind of generally economically viable solutions for everything. They just for subsets, right? And so for, we can talk about this language. So another way to rephrase what you said about the language stuff is these models are very good at predicting what a mean person would do next, a mean person would do next. So sure, they basically do kernel smoothing over positional embeddings, which is great, which means if you have a corpus of data, it'll give you the average response, which is great, and it's very useful for a number of things. Does that provide economic utility for a broad range of stuff? I mean, I'll tell you, I look at these companies basically full-time, and I have for three years. We probably have the largest portfolio of them, and I don't see that yet. Now, there are areas where they do work, but it's not that, it's not this kind of general knowledge worker that's not actually not working. And the areas where it is working is stuff like the marginal cost of content creation goes to zero. So now we have like amazing new content, or computers are creating an emotional connection with humans that's new and that's exciting and that's amazing. But this idea of this general knowledge worker working, like I haven't seen it yet, and maybe it'll happen, but just like self-driving 20 years ago, like that's just not how the universe tends to play out.
Yeah, I guess where do you think we are in self-driving today? And it's been actually a couple upgrades since I took my last ride in a Tesla FSD. This was last summer, actually. It's been basically a year since I did it last. At that point, I was like, I think this is actually safer than the average person I drive with, and probably the average person I see around me on the road, who sometimes I'm like, man, how are you, how did you survive long enough to get in front of me and do that? And they're not deployed at super scale. We're not quite ready to trust them. But if you believe like the statistics from the company, and certainly my just episodic experience seems to suggest that they probably are roughly on par, maybe even better. And maybe we need, maybe society's going to demand like a 10x better to actually deploy at scale, but it seems like we're kind of there.
Yeah, so I don't know if we're there kind of unit economic, and I don't know if they're there on an exception basis. I do feel with a lot of these AI things, you enter this area where you get good enough that the economics suggest that you change the environment rather than make the AI general. And I think this is probably best described with agriculture. So we don't have any unit economically viable way to pick strawberries. Like human beings and animals have been foraging food forever. We're very efficient at it. To actually compete with a human on that is very tough. On the other hand, what we can do is we can plant strawberries in certain rows, and we can add these optical cues, et cetera, that kind of get it much closer. And so I definitely think that we're at a place where, for many cases, AI is better than humans at driving, which I think is great, and I think it's a huge positive. I think these are hugely specialized systems. I don't think you can take the one that's good at self-driving and make it, I don't know, be a virtual girlfriend. I think there's a totally different modality. So it's not general, right? It's not general. It's just good at driving, just like something is good at chess. And now I think we're at the long tail of the problem for fully autonomous stuff like Waymo. The unit economics are just very tough, right? They're very tough if you're competing with a human driver. For other ones, I do think that we, if we just start evolving how we make streets and so forth, I think we're pretty close, and I think that's great. I think this is a positive for everybody.
Yeah, I love the narrowness of the full self-driving. I actually think that's a huge plus that it is an engineered system that does one thing. And I also love your comment about modifying the environment. That was actually very notable even a year ago in the FSD, that the places where it got tripped up, I was like, you know, the closest exit to my house off the highway has one of these service roads and has a stop sign, and it's genuinely quite ambiguous as to who the stop sign is for. As you're getting off the highway, it's not for you as you're getting off the highway, but it's pointed right at you. And so you can understand how it would get confused about that. And that's the kind of thing that if we're serious, we could just go on fixing these signs and we'd make it so much better.
Just a quick digression because this is just so important to this discussion on how the heavy-tailed universe makes this conversation very complicated between human beings, because I don't think people appreciate how heavy-tailed the universe is. So I just want to describe this because it just comes up right now, and it's going to be so relevant to what we're going to be talking going forward, which is there are many things that systems deal with that are heavy-tailed. What heavy-tailed means is if you draw an occurrence at random, just draw one at random, the chances are that it's a very, very rare occurrence. So a very classic case of this is search. And so if you draw a unique search query, say Google, at random, the chances are it's pretty unique, actually, even after all of this time. Now, this is unique searches. So if you take all of the searches that go into Google, say, and then you don't dedupe them, so like you can have a lot of repetitive ones, the vast majority of searches are the same. Let's say 90% of them are common. But if you reduce it to just singular intents, so you don't have any duplications, the majority are exceptions. And that's how the universe tends to be. Like I come from networking, it's a very famously heavy-tailed discipline. A lot of things in the tail. So if you're building a general system, the majority of new things it has to do, not things it has to do, the majority of new things it has to do are exceptions. Now, it's very easy to get tripped up in these conversations because the majority of stuff that you're doing is not new, right? The majority of stuff you're doing is very common. But anytime you get into new areas, then you have to come up with new stuff. It's like self-driving is a very great case of this. Like nobody expected basically a 2D vision problem. Let's be honest, man. Like self-driving is 2D. It's not even 3D. It's like you have streets and you have signs. You don't really worry about the Z dimension, really. And yet a hundred billion dollars in, a hundred billion of investment, we're almost there, but not in an economically positive way. The reason I wanted to make this point now is I think so much of these discussions, as people, I believe, underestimate how heavy-tailed the universe is and how hard it is to make progress. And so we should be working as hard to make progress so that we can do stuff like self-driving and not slow it down because the task is enormously complex.
I think that's definitely a good description of where things are today, right? In my kind of summary communications about the state of AI, I always say that the best systems are closing in on expert performance on routine tasks, and the word routine there definitely is critical because when you get outside of routine tasks, they are not comparable to expert performance.
So let's, let's, okay, so let's move this to here. So as far as I can tell, what LLMs are doing, and there's actually papers that have shown this pretty concretely, is they take a corpus of data, they create positional embeddings, and they basically average over it. And based on that, they can predict what a human being would do or say given a certain situation, right? And they do that basically via averaging. For 80% of the tasks, let's say that's great. This is for 80% as non-unique, right? So you're not duping tasks. But let me give you an analogy. What if I came to you, I'm a startup founder, I'm like, hey, Nathan, I've got this amazing chatbot that for IT help tickets, it answers 90% of the time. And you're like, this is amazing. Like 90% of the work goes away, right? This is what you say. But then you actually do diligence on my company and you realize that 90% of that, 85% of that is just answering password resets. So I was factually correct saying that 90% gets answered. That's the case. But the reality is the situations that I help with are very easy to automate if you wanted to, and they're not that much work. And you still have, from a unique standpoint, you still have to have humans do 50% of the unique things that come in, 50%, right? So that was the state of chatbots for the last 10 years, and we had the exact same discussions. They seem to answer 90%, they answer 85%, they can do these things, we're almost done, but that's not how heavy-tailed distributions work. So let's again, so let's go to this case that you're making. 100%, these LLMs solve problems we couldn't before, and 100%, they're a very useful computer science primitive. We're nowhere close to understanding what these distributions look like, how heavy-tailed they are, and how they can handle that tail, just like we weren't with AV, just like we weren't with original chatbots. And so I just think that without being specific on uniqueness and the distribution and whether we think it's parametric, it's very hard to have these conversations. So we resort to generalities that sound good, but I think from a system standpoint aren't very sensible.
How far do you think this goes? Like, best guess, if you are imagining yourself in 2027 and you have your AI assistant, can you say, hey, I'm going to New York next week for this event, here's the invitation, book me a flight, book me a hotel, and get a good result?
I think it's going to be like self-driving. I think we'll get 80% there with these agentic systems, and then people are going to start changing the environment to make them more effective because human output is also heavy-tailed. And so my best guess, again, I'm going to repeat myself, but I actually think this is how it's going to play out, is right now, anytime we're always at like the beginning of what looks like an exponential, but it's actually a sigmoid. And what we think is like a fat-head system, but ends up being a heavy-tailed system, it always feels like this. Like it feels right now, and everybody's saying all the stuff that they're saying right now, and we're like, it's amazing, you know, everything's going to work out. And then we're going to realize, oh my goodness, the universe is heavy-tailed, this is really hard. These things are good at 80% of stuff, but the 80% of stuff that it's good at is not that hard. And the stuff that I needed to be good at is really hard. And so then we're going to enter an area that we're like, oh boy, we talked about scaling laws, throwing 10 times more compute at something over a period of time is so impossible that what we're going to do is we're going to actually change the way websites work, and we're going to actually have indicators, and we're actually going to have lanes, and then we're going to spend the time actually changing the systems. And so over time, between changing the way websites work and where these agents work, we'll enter a period where these things are more autonomous. But I don't think it's because we've cracked the generality problem. I think it's because we've evolved computer science as a discipline and tech and software as an industry in order to solve the problem.
Hey, we'll continue our interview in a moment after a word from our sponsors. Our sponsor for today's episode is Carta, the end-to-end accounting platform that's purpose-built to power the strategic impact of the fund CFO. For the first time ever, private fund operators can now leverage their very own bespoke software that's designed from the ground up to bring their whole portfolio together, enabling formations, transactions, and distributions to flow seamlessly and accurately. The end result? A remarkably fast and precise platform that empowers better strategic decision-making and delivers transformational insights on demand, timely K-1s, holistic fund performance data, and so much more. Come see the new standard in private fund management at carta.com/investors. That's carta.com/investors.
Even if you think it's a bit overhyped, AI is suddenly everywhere, from self-driving cars to molecular medicine to business efficiency. If it's not in your industry yet, it's coming and fast. But AI needs a lot of speed and computing power. So how do you compete without costs spiraling out of control? Time to upgrade to the next generation of the cloud: Oracle Cloud Infrastructure, or OCI. OCI is a blazing fast and secure platform for your infrastructure, database, application development, plus all your AI and machine learning workloads. OCI costs 50% less for compute and 80% less for networking, so you're saving a pile of money. Thousands of businesses have already upgraded to OCI, including MGM Resorts, Specialized Bikes, and Fireworks AI. Right now, Oracle is offering to cut your current cloud bill in half if you move to OCI for new US customers with minimum financial commitment. Offer ends 12/31/24. So see if your company qualifies for this special offer at oracle.com/cognitive. That's oracle.com/cognitive.
I find language to be a confusing domain in some ways because there is so much, it's hard to get truly out of distribution in like interesting ways. It can write a sonnet about the NBA finals or whatever, and that's definitely out of distribution, but you could say it's interpolating between things in distribution. Sometimes I like to just go like to things that humans can't do. So when I look at things like Evo, the early foundation model for DNA sequencing, it's an interesting one. And there's another, I did an episode just yesterday on models for basically simulating solutions like salt solutions. Yeah. And in both of these cases, you see these sort of remarkable generalization moments where in the Evo case, it's trained on DNA sequence data, just like bacteria and phage data. And so it's next token prediction, it's next base pair prediction, same thing as a language model, right? So you could say, oh, it's only predicting the next base pair, but like the language models, it seems to have developed these higher-order internal representations that mean something that it was not specifically trained to learn, but that it's like learned in service of making the next base pair prediction. And one of the experiments that they did that is so striking to me, this is from the Arc Institute, they did what they call gene essentiality scoring, where they basically say, we'll give you a gene sequence and we'll perturb it, and then we'll look at your perplexity, your being the model, your level of confidence or uncertainty downstream of that prediction. If you remain confident, then we can believe that gene must not be super essential because if it gets messed up, then you can still predict like how this fits into life. But if we make that change and then you become very radically unconfident in your downstream predictions, then we can infer that this gene is actually really important because now when it's off, now you recognize you're out of distribution and you can't make any confident predictions anymore. It seems to me like that signals, and that's like a 7 billion parameter model, 300 billion tokens, 2% of what Llama or 1.5% of what Llama 3 is trained on. So it does feel like there's some potential in these systems to learn things that we don't know, to grok, if you will, patterns in the universe that are not known to anyone really, to essentially speak DNA.
Yeah, so if you buy all that, how do you backport that to language? Because I feel like start to see, you know, just modeling the economy or modeling software, I do start to see things. If you were to train, keep scaling and keep training these models on distributed systems or software or whatever, how do we know that they don't start to learn things that people don't know and truly generalize beyond the training set? Because it does seem like that's happening in some profound way.
I think this is a great question. I think maybe this is why I come to this from a different thing. Prior to my PhD, like my life was computational physics. I worked at Lawrence Livermore National Labs. I did large physics simulation. Like I just lived this life. And I think the Occam's razor in all of this is distribution in, distribution out. These things are very good at learning distributions of the training set. And so this is just in this kind of weird, quirky coincidence of this moment. I actually worked on protein folding at IBM Watson Research Center in 1999 on the Blue Gene project. And at that time, there was a belief that we knew enough of the fundamental forces in order to actually from first principles calculate protein folding. That was the thesis, and that we just didn't have enough compute. And so they actually built a whole computer to do this called Blue Gene. And through corporate mechanics, that ended up becoming an entirely new computer because they couldn't fund it. It never really happened, but there was the belief that if you had enough compute, that you could do protein folding and a bunch of other stuff. And so I think it's very reasonable, this is a strict Occam's razor, that if you have enough compute and you have enough data and you're dealing with an axiomatic system that you can reduce to first principles, then you will learn that distribution and you can use it for predictive stuff. And if you want to call predictive emergent, that's fine, but it's just predictive. Like anything is predictive. Like I've worked on simulation codes that were predictive. Could I have predicted the yield of a nuclear weapon? No, I could not have predicted that as a human being. Only a computer can. But it's really just understanding first principles to create these things. I very strongly believe these models are very useful in science where you've got fundamental laws of nature that are being learned that can be predictive. I think the models that are good at that is not going to turn around and solve a different problem most likely because I think you've probably learned one distribution from one domain and that's a very useful tool that we should use.
Now let's go ahead and move that over to language now. So if my Occam's razor is these things learn structure in a data corpus, it's distribution in, distribution out, that means that they're learning structure of the text corpus that they've been fed. And a great example of this, there's a recent paper I saw, I don't know if it got accepted or not, I think it was just on arXiv, but that showed that if you could gzip a text corpus and the compression was good, then the accuracy was good, which suggests almost everything you need to know about this, all it's doing is learning structure in the text. It has nothing to do with underlying meaning. It's just structure that's in the text. So you can understand the distribution of text, you can actually spit out text, but this doesn't say anything about learning fundamental principles of the world from which the text is based. And so it almost seems to be that the magic in the sequence of text is you've got these humans that have spent, say, 3,000 years looking at the universe, and the universe is, again, heavy-tailed, and it's nonlinear, and it's very complex, and it's fractal, and it's similar, and these are notoriously complicated systems to simulate. So then the human brain was like, I'm going to abstract this out as a tree, and I'm going to abstract this out as like this concept. And so we're like these machines that take the universe and abstract it into things that are words, but it's a very lossy representation. You can't describe something and get back the universe. But it turns out because we have those abstractions, they're very predictable. Like we've made the universe more linear, and we've made the universe less heavy-tailed, and we've made the universe less self-similar. And once we've done that, we've added structure that's predictable. So the fact that you can take a corpus of text which a human being has pulled from the universe and then made the universe much simpler and find structure in that is not surprising at all. But to think that somehow then you can go from that to the universe is a step that like just simply has not been demonstrated, and it actually doesn't even stand to reason.
If I understood you correctly, you're saying like that doesn't mean that they have any understanding of meaning. How would you square that with like a sparse autoencoder line of research or sort of Golden Gate Claude, if you will? Like they're able to now say through these sparse autoencoder techniques that they can isolate, I think it's 30-some million different features, each of which is a direction in activation space, and then inject those at runtime, right? And they're starting to create these sort of control mechanisms where if they jack up the Golden Gate Bridge feature, then all it wants to talk about is Golden Gate Bridge, or more practically, insert kindness or insert, you know, deviousness or whatever. There seems to be some meaning there, right?
There's structure that's very different than meaning. So we're talking about three things. And this is a great conversation because I think it gets to the heart of it. So the universe is self-similar, it's fractal, meaning no matter what zoom level you look at it, it has the same stochastic properties, right? So like you can spend an entire life studying a cell and a planet, right? That's how much complexity is in the universe. The universe is heavy-tailed, which means the exception is the norm if you dedupe, and it's nonlinear, which means that you can't computationally predict out too far just because we don't know, we don't have closed-form solutions for nonlinear stuff, and it's just a very hard computation problem. Like that's the universe. Now, human beings have had to navigate this crazy universe, and so we've created this amazing engine, which is the brain, and it has reduced this universe to concepts and words and stuff that we use and we talk about. That kind of makes it a little bit predictable, and so at least you and I can communicate about it. But if I tell you like this is a tree, there's a concept tree in my brain, but it's almost an arbitrary distinction that it's a tree. I could talk about branches versus leaves. I could talk about networks of trees. That's actually one tree, like the big aspen grove. I could talk about cells of the tree. It's like this kind of arbitrarily useful distinction. So it has some semblance to the real world, but if I say a tree, it's probably not an accurate relative to how the world is. Is it one tree? Is it a family tree? It's just a useful abstraction. So these models will 100% recover the abstractions that we've put in text because the structure is all there. That's not surprising. Like compression would do that. All it's doing is taking advantage of structure, and that structure is real. But let's say that it's finding a tree. Does a tree actually map to the universe in a meaningful way? It's a human-created concept that has some vague sense to something we all agree on, unless you're a scientist, then you probably disagree with the common understanding. And oh, by the way, my concept of a tree also includes like a toy and a cartoon picture of a tree, which is entirely different, right? And so text is a way that we as humans represent the world that's very different than the actual universe because we find it useful. There's structure there, and these LLMs exploit that structure just like compression would or anything else. And it's very useful for us, but it doesn't necessarily mean that these things can enact on the world, right? These are very different domains.
Yeah, I guess I'm not quite getting the gap. There's so many interesting results to point to recently. Did you see the one about GPT-4 finding and exploiting new zero-day exploits? This was just in the last week or two. So, and it's increasingly impossible to keep up with everything, so I don't expect you've seen everything, but...
No, that one I have. I think when dealing with this much compute and this much data, I think the human intuition just totally fails, and we as humans are really bad about thinking in distributions anyway. That's not how we think. We kind of assume the world is parametric, and like, by the way, which is why the text that we create is so well structured and why it can be exploited by LLMs. Like you have to navigate this universe, you have to make the simplifying assumptions, which we do. And so it's good to actually come up with mental frameworks about how these things work. So I'll tell you a few of mine. The first one of mine is, as far as I can tell, these things are explaining structure in whatever data that they're reading, and like we've mentioned before, and it's not clear whether that distribution extends beyond that. And if it does, then you're basically back to simulating the universe, which I've spent a lot of time with. I think that's very true. The second one is the actual mechanisms we're talking about, transformers. The actual mechanism is basically kernel smoothing. It's averaging, which means to me is the further you get out into where the data is rare, the greater the inaccuracies come. And that doesn't mean that for systems that you can actually extrapolate from that, you don't get great results that would be quote-unquote out of distribution. It turns out some systems are linear, or you have enough data, you can map the distribution. So that one is totally fine. Then the third one is this in-context learning one. And I think Vishal Misra, who's a professor at Columbia, did the best work on this, where he actually shows that for in-context learning, where you actually put the context in the prompt and you can move the posterior distribution to get interesting results, he mapped it specifically to Bayesian learning. And it's a beautiful paper. I don't know why more people don't read it. So listen, we know that these things can do some basic Bayesian reasoning, and this is where the prompt is basically the new evidence, which changes the posterior function. So you'll get new stuff there. We know that if you average enough stuff, you'll get new stuff there. It just has to be linearly interpolatable. If it's not linearly interpolatable, you're not going to get new stuff. So none of these things suggest that you're not going to get new stuff. It just puts constraints. We know how Bayesian systems work. We've got 20 years of understanding convergence properties to them. We have work that's specifically mapped ICL to Bayesian learning. So let's just go ahead and use that corpus of work to understand the properties. It doesn't say it's out of distribution or in distribution. It doesn't say that at all. It just bounds what that means. And then we also know the mechanics of the way transformers work, which is this kernel smoothing. I mean, it's more complex than that, and so that can create new things, but it means there's a linear interpolation. And so I think the problem is we have these anecdotal conversations where it's whack-a-mole. It feels almost like the intelligent design discussions, where someone will come up with a new set of evidence of something that there's no way evolution could have created this, and we have to spend all of this time to show actually you can, but we don't know everything, and here's the theory. And I feel like when we have these discussions, they should be a bit more principled as opposed to, I've got this anecdote that seems something's new, because nobody says that you're not going to see new stuff. I mean, it very obviously, if you're doing interpolation, it's new. Very obvious if you're doing Bayesian reasoning, like something's going to be new. And talk more about the distributions and the theory of why we're doing that. But as far as I can tell, that's totally missing. Nobody's come and said, here's my theory of out-of-distribution stuff. Here is my thesis for what is going on functionally to create this new data. And on the other hand, you've got mounting tons of evidence that map these to existing systems that we know that people just seem to not want to follow. And I just feel like, listen, humans love to see things in clouds and complex systems. There's so many facets, and they're so complicated, and they're so huge, and they're so ethereal, and then we see things, and we just do this historically. And we've got these kind of amazing computer elements that are huge, and they surprise us, and they're amazing, but we can map them to formal systems, and we know how they work. And that doesn't mean that they're dangerous or not dangerous. I'm not saying that. I'm just saying that we can actually map them to reasonable systems to have a discussion, and that just seems to be missing. This conversation is a great example. I'm very happy to map these things to formal systems we understand and have that discussion, but it's always this kind of anecdotal whack-a-mole instead, which I just don't know how to answer to every instance of what seems like emergent behavior when, of course, emergent behavior is expected. Anyways, I am definitely a materialist, and so I do believe that in the fullness of time we can probably figure out an arbitrary level of detail how these things work. They're actually way easier to study than life, for example.
Of course. And I would say we've made tremendous progress in interpretability and just general understanding. That paper you mentioned is a great example. I've seen another one too that's pretty similar, where somebody designed a matrix implementation of gradient descent and then looked for that in the wild and found it. It's like, oh look, these things have learned to implement gradient descent at runtime. And that's another kind of mechanism, at least sometimes, probably have different mechanisms in different models. And there's this various, almost like phase change type of dynamics that are being explored too, where even for something as simple as like modular addition grokking, there's like multiple algorithms that it can lock into, each of which work, but they're different. And so there's memorization, and then there's multiple like actual algorithmic solves, and which one you end up with depends on initial conditions. So I don't think there's any magic in the machine. I'm definitely with you on that. It does seem that in principle we should be able to figure it all out. It doesn't seem like we've made a lot of progress, but it doesn't seem like we're that close to having it all figured out. On the sigmoid question, I tend to also agree that it does not seem like there's reason to believe that this is going to be an exponential forever. It does seem like it probably levels off. But then I'm also reminded of the old joke of two guys in the woods and the bear is coming, and the one's putting on his shoes and he says, I don't have to outrun the bear, I just have to outrun you. And so I do wonder if we imagine continuing to scale up as we have been scaling up, and there's all these trend lines and X times more compute and however much advantage from algorithmic efficiency or whatever. I was just talking to somebody at generally one of the top five hyperscalers in the world, and they are using a new replacement for the Adam optimizer that is giving them like something like 30% savings on compute. This was published open source. The technique is called Sophia, and just like incredible, 30% off the top, you're saving like a hundred...
Million dollar on the biggest runs anyway. Let's imagine we continue to scale up and it's a few more orders of magnitude. And let's say we don't just put in the text, but we also put in like this sort of low-level solution data and the protein, you know, the DNA data and the protein and the gene expression, and we work our way up all these levels of orders of magnitude. And then it's like computer systems, like all the cloud logs from AWS and Google Cloud and all this stuff gets in there, and you've got all these different self-similar but overlapping orders of magnitude of ways of understanding the world. Even if it levels off at some point, I have a hard time imagining that doesn't level off at a higher point than human is able to achieve today. But I feel like you probably see that differently.
Still, so a lot of this reduces to how you view the universe. If you don't view the universe as fractal, self-similar, and if you don't view it as heavy-tailed, and if you don't view it as nonlinear, then you could imagine that. But it is all of those things. We know it is all of those things. And so there's no distribution of data that we know of that's not the universe that will produce something that's predictive of the universe. It's really that simple. That doesn't mean that we can't focus on an area and reproduce that distribution. I could become very good at predicting whatever protein folding. I could get really good at playing chess. But it's distribution in, distribution out. If you notice, the ones that like stuff like recursive self-similarity works, and control loops work, and simulated data works, like synthetic data works, there are these axiomatic areas where the axioms, like, they constrain the search space and you're basically converging on search, and you can get very good at those. I can get much better at you at arithmetic. I can get much better than you at game playing. I can get much better than humans at all of these things, but none of that talks to the fact that can you find the right level of abstraction in a fractal system and can you tackle a heavy-tailed universe where not by occurrence but by uniqueness the complexity is in the tail. Even in this discussion, the use cases that you view tend to be these kind of axiomatic, you know, of course we can do full, like we thought in the late 90s we could do protein folding by fully searching the search space. It's just not surprising to me that we can learn distributions and spit them out. I feel that's a very different statement than saying now we have a model that can navigate the universe in a way that is predictive of all of the complexities of it. Maybe another way to think of this is we've spent 3,000 years doing our best and writing it down, and we can create a model that can learn from all of that and do what the mean human being would have done in the last 3,000 years. But the problem is the stuff that we're doing tomorrow, by uniqueness, a lot of it's going to be new, and that's just how the universe works. And we're going to have to either build a machine that can do that, which we don't know how to do, or we're going to have to do it ourselves and let these machines do the mean task.
So do you have an account of or theory of what it is that you think humans are doing that the models can't do today?
I mean, two things. One of them, and the most important one, is we experience the universe and we abstract it into concepts. Like, that's very comp—like, why do you think all the budget is moving to post-training, by the way? What's your thesis of why so much budget right now is moving from compute to post-training?
Ease of use is a huge one. I would still guess it's probably a minority of budget if you're talking like, I don't know, L4 or on. I don't know. Listen, they had—they said they had 10 million messages. I know how much multipass costs. Let's say it costs $15. Like, we're talking a budget between 100 and 200 million, which anecdotally it seems about right based on what I know of the industry.
Yeah, that's about half. And so what I would argue is we're very good—models are very good at taking the output that humans create and being able to reproduce that distribution. They're very good at that. This is why Scale AI is Scale AI and all these companies are so successful. That's not the game. The game is looking at the universe and creating the supervised data. That's the game. And so I think one model to look at this is, again, human beings have been around, let's say, in a capacity for writing things down for 5,000 years. So you've got humans for 5,000 years that have been looking at the universe and doing this thing that models cannot do, which is making a decision like that is a rock and that is a dust and this is a concept and this is a relationship and I'm going to write it down. And then as a group, we're going to synthesize these ideas and work at these. And so we've got this kind of almost kind of Platonic representation in our heads of the universe, and that is very structured. So we did all the hard work. That is hard work to take this untamed universe and reduce it into words and concepts. That's hard. No LLM that I know can do that, not even close. But then once we've done all of that hard work, is it surprising to you that there's structure? We did all this work. Of course there's structure. So you take that structure, you put it into an LLM, it learns the structure and it can spit it back out. So the very specific thing that these LLMs can't do is look at the universe and recreate this kind of structure. And to be super clear, that structure is not the universe. That's very different. Like a rock is a rock is an idea in our head. It's not representative of any single thing. Is a grain of sand a rock? I don't know. Is a boulder a rock? I don't know. These are concepts we've created in order to navigate the universe. They're not the universe. So human beings take the universe and create the concepts and the LLM, and then that's structured because we need structure in order to do anything. The LLMs learn that structure. Feels like the only thing that works is basically you can do exhaustive, quote-unquote, AI, which converges on search to learn distributions, or you do supervised learning, which human beings are doing the hard work, in my opinion, by labeling things and everything else, and then you just learn what the human beings have done. But to take the universe and actually to rain structure and all that complexity, that's what we do. And it would be great if machines can do it. I've never seen any evidence that they can. Yeah, maybe some glimmers of it, but that's just not where we are.
Yeah, I think the—so it might be—I just want to be super—because you asked me a very specific question, a very specific answer. Look at the universe and then come up with these concepts that are useful, that are not the universe. They're concepts. They're totally separate. Like a rock is not a thing, it's a human concept. But to take the universe and decide something is a rock, that's actually all of the complexity and all of the energy is that step, which LLMs just don't do. Yes, this is why I think the language is such a tricky domain, by the way. The Platonic representation, you probably saw there's a paper titled exactly that recently, but it doesn't tell us much about this particular question because it is still operating in the language domain and it is in that way able to piggyback on our prior art in terms of useful abstraction of the universe. I do think if there was a line of research where I would venture a guess that I think you maybe wouldn't agree with, that maybe we could come back in a certain finite amount of time and say, has this happened or not, and what would we infer from it, I probably would look at this biology foundation model space and the sequence modeling. And you can imagine there's—that's going to be elaborated a lot. They didn't even use eukaryotic sequences in that initial Evo paper, let alone like expression data, transcriptome, proteome, whatever.
We know enough about the natural sciences to build predictive models when we have for a very long time, right? Like I can simulate a supernova on a computer pretty accurately. I think it's phenomenal that the—it's phenomenal that we have an approach to throw computer at a problem that learning a fundamental law of physics. But again, how is that any different than the fact that we've been modeling physical systems for a very long time, other than the fact that in these cases it allows us to apply more compute at the problem and we can solve problems that we don't have closed-form analytic solutions to? It almost feels to me like an extension of simulation, which would be very different than the claims around general reasoning. It's literally learning laws of physics, which we've been doing since the beginning of compute, right? The creation of computers was for ballistics, right? So the reason that we created computers is because ballistics are nonlinear, right? The trajectory of ballistics are nonlinear. So we had people in rooms that would create logarithm tables by hand. They were called computers. That's where the name came from. AnyC shows up. AnyC does it forwards, it magnitudes about 5,000 times faster than a human being does it, and we have a computer. And this is a perfect example of a nonlinear system, which is a trajectory with gravity being done by a computer. Why is this not just a straightforward extension of exactly that, like we've been doing for the last 80 years?
Hey, we'll continue our interview in a moment after a word from our sponsors. How deep do you go to seek out an answer to a question? Maybe you've spent hours clicking the source links on an obscure Wikipedia page, or maybe you're even the type of person who checked out the entire shelf on the topic at your library. If you're nodding along, then check out GiveWell, an organization that researches questions about global health and philanthropy, even if a satisfying answer might require years of reviewing studies, talking to experts, and over 300 footnotes. GiveWell has now spent over 17 years researching charitable organizations and only directs funding to a few of the highest impact opportunities. They've found over 125,000 donors have used GiveWell to donate more than $2 billion. Rigorous evidence suggests that these donations will save over 200,000 lives and improve the lives of millions more. GiveWell wants as many donors as possible to make informed decisions about high-impact giving. You can find all of their research and recommendations on their site for free. You can make tax-deductible donations to their recommended funds or charities, and GiveWell doesn't take a cut. If you've never used GiveWell to donate, you can have your donation matched up to $100 before the end of the year, or as long as matching funds last. To claim your match, go to givewell.org and pick podcast and enter Econ 102 with Noah Smith and Eric Torenberg at checkout. Make sure they know that you heard about GiveWell from Econ 102 with Noah Smith and Eric Torenberg to get your donation matched. Again, that's givewell.org to donate or find out more. Hey everyone, Eric here. In this environment, founders need to become profitable faster and do more with smaller teams, especially when it comes to engineering. That's why Sean Lenahan started Squad, a specialized global talent firm for top engineers that will seamlessly integrate with your org. Squad offers rigorously vetted top 1% talent that will actually work hard for you every day. Their engineers work in your time zone, follow your processes, and use your tools. Squad has front-end engineers excelling in TypeScript and React and Next.js, ready to onboard to your team today. For backend, Squad engineers are experts at Node.js, Python, Java, and a range of other languages and frameworks. While it may cost more than the freelancer on Upwork billing you for 40 hours but working only two, Squad offers premium quality at a fraction of the typical cost without the headache of assessing for skills and culture fit. Squad takes care of sourcing, legal compliance, and local HR for global talent. Increase your velocity without amping up burn. Visit chwsquad.com and mention Turpentine to skip the wait list.
Here's my expectation. Tell me if you—maybe we could make a little friendly wager on this. Yeah, I think that over the next year, we are going to start to see scaled-up foundation models for biology that are going to start to understand the super complicated interactions between genes, between proteins in cells, in ways that are inferred from inputs and outputs, learning these higher-order concepts in the middle, yeah, which we could not simulate because it's computationally, you know, just intractable, and which we certainly don't have a closed-form solution for either. I agree. If that does happen, that would seem to constitute to me an instance of looking at the world, looking at basically raw data of sequences and just lysed cells and what proteins were found in them and whatever, and learning meaningful abstractions. And I would expect that we'll start to discover stuff by doing counterfactual experiments on those models. In other words, tweak a thing, see what happens, find medicines, find disease patterns by make a tweak, see what happens. What if we change this counterfactually and then go validate those things in the wet lab? If we start to see that happening, would that to you represent—
I agree. Phenomenon. I fully expect that. But how does that not constitute looking at the universe and figuring out what's what? Oh, for sure, for sure. For specialized subdomains, you absolutely can learn distributions 100%, right? Listen, I've implemented Navier-Stokes, like fluid dynamics, where—and this is a turbulent, chaotic system. So we've known how to, like, implement very complex systems with computers for sure, and especially in very specific domains where we can reduce these things to a few fundamental forces or we can reduce these things to mostly linear systems. Like the previous version of this is just all the computational methods where we would kind of take a problem that we know and we'd actually experimentally determine, like just experimentally, we'd say, okay, this material behaves this way under this pressure and this heat and it has these properties, and we take what we learn experimentally and we'd create these models and they would do pretty good at simulation. And I would say this is a very straightforward extension of that, which is you look at how the world works in a constrained situation and then you can predict what would happen in the constrained situation. But just like simulation, remember, we could do this with simulation. We've been able to do this for a very long time, right? So we could experimentally determine, like, how different materials work, and then you can actually simulate a new system based on those. This is how we do most industrial design today anyways. So my question to you is, how is this fundamentally different than that, or not a natural extension than that, where you're giving it a system, you're learning some fundamental properties, you can do something new, but that doesn't mean that you can disobey the laws of physics in predicting stuff that computers can't predict. It's not obvious to me that it can simulate complex nonlinear systems that are chaotic for long periods of time. I think this is just yet another step on this kind of, like, we have computers simulate physical stuff and we're simulating the next thing with the next tool. Does the parallel make sense? Like if you go to, like, in the 80s and 90s, we would literally empirically test physical matter. We didn't know how the physical matter worked. We just empirically test it. We'd have it has this opacity under this heat, it has this tensile strength. We'd use that to build databases of materials, equations of state, we call them. This is how they interop, right? We'd use those when we're doing simulations and we'd simulate what happens when a car explodes, what happens if an airplane runs into a building, like all of these things. None of those instances worked. They were simulations and they were very accurate and none of them came from, like, first principles. They are all empirical, but that has its limits because it didn't solve climate prediction past 15 days. It didn't allow us to simulate life. And so to me, this is just computers being attached to another domain, which, thank goodness, we've come up with a great tool that's going to give us a little bit more insight, but it's a little bit insight is what it is. By the way, we had the same discussions in the simulation. This is why, by the way, we stopped PlayStations from going to the Middle East was exactly this. So again, I worked—I actually worked in the nuclear weapons program at Livermore, so I was very close to the previous version of these discussions. Like, oh my goodness, if Saddam Hussein gets PlayStations, he's going to be able to simulate nuclear weapons, right? Like, just totally misunderstanding that the ability to simulate something is not some runaway process that's going to allow you to recreate a world or anything like that. It's a very specific tool for a very specific situation. But we were here before, whenever it was, 25 years ago.
Yeah, there's certainly no arguing that past predictions of AI progress often didn't pan out, and that does seem like it's not a near-term future that we can dismiss either.
The other argument is that they have all panned out exactly as you'd expect, and they're going to continue to. And this has been steady progress for 80 years, and it's been a super useful tool. And every time we unlock something, people are like, oh, poo, that wasn't AGI, so that must not have been AI. And they're, like, focused on the wrong goal, and it's a very unspecified goal. And instead, it's like any other computer science primitive where it keeps solving problems, and we should continue to solve problems with it, which is the way that I would view it. It's interesting because people talk about summers and winters and not panning out, like you just did, but it couldn't be further from the truth. It's been a foundational primitive of computer science that we've been using very effectively, and we continue to use more effectively, and I don't see why that won't just continue to be the case.
Yeah, I like your vision. I think what you're describing is almost an ideal scenario, I think, but I do think this is an important foundation. Let me try to bottom line your perspective. Yeah, I'm still a little confused around what would count as—what would be the evidence of if the fundamental thing that humans can do and have done through our history that the AI can't do is look at the universe and figure out the right abstractions and come up with the right concepts that compress it in order to make sense of it. And I agree it's very hard to say what they're doing in the language domain because we already did that work and they're learning it from us. I tried to describe something in the biology domain where it's like it seems like they're starting to show signs of doing that, and I could believe that they would. And then you sort of agreed, but then now I'm confused as wouldn't that count as doing that? And then it seemed like the response was, well, that's just in one domain, but it doesn't seem like there's anything that would prevent it. Certainly there's a huge leap in generality with this latest generation of systems. So I do imagine just shoveling all the modalities into one model. We've already got text, vision, and audio in GPT-4o. Why not the true GPT-5 would be like biology data and weather data and, like, pictures of deep space and solution simulations and just battery simulations, material science, whatever, throw that all into one thing. And if it can do that, then it's definitely not going to be constrained by one domain anymore. So I'm still a little lost as to, like, exactly what the limit that you see is in terms of why it doesn't become a system that's more powerful than people.
I'm so glad you reduced it to this. I think this is great, right? And there's two things. There's this notion that language reasoning is general, which a lot of people believe, but you don't seem to be on that kind of kick. So let's put that one aside, and you're more on the, like, learning properties and simulating properties of the universe side, which is totally fine. So what I would do is I would just bring you back to everything we've learned about simulation, which is even when you know all of the properties of a system and you can simulate, you just don't have the computational capacity to simulate nonlinear systems. We don't have the materials or the energy or anything. It's literally like a compute problem. We have codebases that have been around for 20, 30 years that simulate all sorts of crazy stuff, and yet they've got limited utility for exactly this reason. The universe is just so complex that they're useful for a little bit. And so if it turns out—and I'll give you a very specific one that we can bet—listen, if it turns out that these models somehow change that compute tradeoff where it can simulate nonlinear systems in ways that traditional stuff can't, I'm 100% with you. But that's not what they're doing. What they're doing is they're inferring stuff that we haven't been able to infer by looking at data. That doesn't mean that they can be predictive in a way that kind of disobeys our understanding of compute requirements. And like a Ray-Taylor—let me just give you a specific. So Ray-Taylor instability is basically if you have two liquids that are on top of each other with different densities, and that is one Ray-Taylor unstable system. And if you perturb it, like you get these kind of, like, just amazing kind of chaotic turbulent things that happen. We have been looking at this problem for 30 years, and we have no idea how to actually predict what will happen. We just know roughly what they will look like, but we don't know, like, the specifics. And AI systems are way less efficient than an actual, like, code written for simulation. So to think that it can tackle those types of problems, I just don't see any indication. I mean, I view that we have these kind of modalities of compute that we can throw at problems, right? So the most efficient is basically imperative programming, where you give the computer a set of instructions and exactly the rules, right? So that's just normal programming. And then we have another modality, which is declarative programming. And by the way, the first one's the most efficient, right? It just does the rules. The second one is, like, the end state that you want. I know the end state, but you know it very specifically, and then the computer figures out what to do. This is declarative programming. And so to come to the solution, it has to do all of the logical closure stuff. So that requires more compute, right? And we don't even know how to bound that compute. That's why, like, databases, when you run queries, are not bounded. So that's declarative programming. Now we're in AI, where you don't even know what the end state is. You're just like, I have a whole bunch of data, and I want you to find patterns in that data, right? That requires even more compute. So it's even less efficient. So it's another modality of compute. It's one we've been refining for a long time, but it doesn't change the nature of computers. They're still systems, and they're still computers. They still have the same limitations independent of what distribution that they learn. And so if it turns out that these things can, like, simulate systems for a period of time longer than the normal simulation, then I'm with you. I'm like, this is breaking the laws of physics. But until then, it feels to me like simulation where you just don't know all of the rules, but it's learning some of the rules.
Yeah, I guess I think about it less in terms of simulation and more in terms of how effective the choice of actions can be at any given time step. Like, I'm not simulating the universe. Humanity as a whole is not simulating the universe, but we're all just taking our local conditions and our sort of general sense of our own selves and goals and, like, trying to do the next step at any given time. And it seems like our overall efficacy through our lives is the integral, if you will, over how good our choices are at each given time step. And that doesn't depend on any huge simulation of anything, like, irreducibly complex. So then if I imagine an AI, it seems within reach to imagine an AI that can do something very similar to what I'm doing, which is have a goal, look at its immediate surroundings, look at what it just did, look at whatever other context it may be given, and pick a next action, and potentially be better than me at it, and potentially quite a bit better. And then that to me seems like enough. If it can do that, then I feel like we're in an unprecedented environment where we now have fundamentally pretty alien and not super well understood things that can take more effective actions in many given contexts than I could. And then that to me is, like, where I start to turn the conversation toward what sort of safeguards should we have in place, just again because these conversations tend to be so modeled.
If that action requires interacting with a physical world, it has to simulate the physical world. It just does, right? Like, it has to understand, like, dynamics and ballistics. It has to understand what happens if someone throws a rock at it, or if it's, like, in water, or if the weather's—like, I mean, that's how you navigate the physical world. That's really why we created computers, right? It was because these are very hard things to do. And then if it's not that, if it's not interacting with the physical world, then it is interacting in this kind of language domain that we've created. And I agree, it'd be very good at some subset of those things. There's zero indication it'd be good at new things, and that's what we're actually very good at. And again, without actually having a model for all of these things that we understand, like the distributions we understand, the mechanisms, I feel like we just use words, and the words all make sense, but, like, complex systems, we never know convergence and divergence without actually specifying the system. And I feel like for these conversations, we just don't have a system we talk about. And so it's always we live in the world of, like, rectangles and arrows, and somebody takes a rectangle and they have an arrow that goes back to the rectangle, they're like, ah, we've got a virtuous cycle, without actually specifying that if you have diminishing marginal returns, you don't go anywhere, or you're doing the same stuff, or whatever. And so I think this is incumbent on all of us to actually understand the systems we're working with and then come up with these basic views and properties to make sure at least we understand what the convergence properties are. I'm sorry, that was a very muddled thing to say, but I feel that until we talk about specifics, it's very hard to make concrete statements in this.
Yeah, it's tough. We're in a tough environment because things are moving really quick and we are pre-paradigmatic, right, on understanding a lot of these things. Again, I think the progress has been incredible, but we're just starting to crack the black box. Okay, so let's change gears because I think this is probably certainly gives everybody enough to get at least a good intuition for our relative philosophies on this. Yeah. So what do you think we should do right now in practical terms to regulate AI, if anything?
The regulation one is sticky for me for two reasons. The first one is we don't even have a definition of AI. And so I think it reduces to regulating software. And then for that, I would say we've been regulating software for a very long time, and there's a broad, robust discourse around that. And I think we should make whatever conversations we have part of that broader discussion.
So yeah, just kind of trying to bring a couple different lenses to this from existing rules. We obviously have liability rules for all kinds of products, not just software. It seems like there is a general kind of tradeoff that companies make with the government where it's like, we want to have safe products that we can generally count on as being safe. Companies don't want to be sued every two seconds. And the general trade is like, you agree to implement some standards. If you implement those standards, you'll be shielded from regulation. And that does vary, right, across like lots of different product types. You know, cars are very different from milk and so on and so forth. But we don't have anything really like that for AI, and not a ton really for software either. You probably know better than I do in terms of some like niche areas.
I mean, cars have a lot of—cars are increasingly software products, and airplanes have a lot of software in them, and medical devices have a lot of software in them. So all these regimes, there's tons of testing, there's tons of verification. They are engineered and demonstrated to a standard. But we don't have those like standards really for these AI systems yet. We do. I don't know what the distinction between AI and software—I really don't. Like, I have seen the definition using these regulations. It's so broad that it really could include all non-trivial software. And I don't say this to be a polemic, and I don't say this to be difficult. I'm saying this very clearly. They literally say a system that can, whatever, navigate and change a virtual or physical system. I mean, these are so broad, right? So we're really talking about software. That's what we're really talking about. We have, what, 70 years of history regulating software in many domains, and I think that regulation is very important. I'm not a libertarian. I'm a lifelong liberal, like a very moderate person. I'm just saying this discourse has been around for a very long time, and we should continue. And if there's an area that software is being pushed, an area that we need to have some sort of protections, we should add them to it, right? But that's a very different statement than saying AI is somehow paradigmatically different. There's just like literally zero indication that it is, and then try to somehow regulate a computer science primitive. It's like regulating a database. Let me give you like a specific example because I—so by the way, we went through this during the rise of the web and the internet. And so a lot of my formal studies were in networking, and so I was actually pretty close to these discussions. And at the time, there was this concern that with the rise of the web and the internet, you have actual paradigmatic shift. It's not just software. It's different. And we actually had examples like the Morris worm had taken out a whole bunch of stuff. We were running critical infrastructure on it, and there was this notion of asymmetry, which actually changed the defense posture of the United States. And the notion of asymmetry is the more that you bought on to the technology, the more vulnerable you were. So as opposed to mutually assured destruction, which was our doctrine before, we now have this new thing, which is like, oh my goodness, we're the most vulnerable because we've been adopted. So you had two very compelling reasons to want to regulate this stuff and be afraid of it and do closed source and whatever it was. You had like examples of taking out critical infrastructure, and you had this change in posture. And yet even that, which we have none of those today with AI, none. We don't have examples of like this horror, like there, like literally it took out computers and hospitals, right? We don't have any examples of paradigm shift. And even then, the conclusion after very robust conversation for a long time is you regulate the applications, you regulate the industries, you don't regulate the math and the computer science primitives. All that I would ask at this AI discussions is either A, demonstrate it's paradigmatically different, and if you don't have that, then B, let's absolutely regulate and have regulations. Let's do it as part of the broad, robust discourse we've had over the last 20 years with really smart people in much more dangerous environments. Again, I think that we put all of our fears in AI, but you realize like we're running hospitals on the internet for the first time that were being taken out and it was impacting patients. That's what we were dealing with. And now we're dealing with theoretical threats on bioweapons that don't even exist yet. I just feel like we've all gotten mad and forgotten where we came from and the discussions that we've had. And all I'm trying to do is saying we've been here before. It was actually much worse here. The conclusions, let's draft on all of that work and shared knowledge.
I guess to venture a distinction or what makes the technology a paradigm shift, I would probably zero in on the fact that they are trained, not engineered, and that maybe a better thing even than that would be that the creators of the models generally don't know what they're going to be able to do, and even at deployment time don't have a very robust account of what the capabilities of the systems are. You could point to things in the past and like, oh, you didn't expect this out of whatever, but this does seem to be qualitatively different that they just train, train, train, train, train a long time.
You know, especially you look at base models, right? Base models are totally unpredictable, and nobody really knows. I think one of the reasons that people are putting so much resource into post-training is to try to get control, and it's only sort of working.
Yeah, so this is the thing when you're talking to an internet guy and a distributed systems guy, it's just like none of the systems that we worked on, we understood the implications of. Think about the internet. Like every sociopath becomes your next-door neighbor. What does that even mean? What does it mean to put kids on the internet? What does it mean to have your business on the internet? What does it mean to put critical infrastructure in the internet? There is no model for how any of this behaves. There is no way to build, make computer systems provably correct. Like we didn't have any of that. We, like a lot of the early discussions when we were creating TCP was to prevent congestion collapse because we thought, oh, like everybody's going to, like the communication protocols, they're going to all decide that there's an issue on the internet and then they're all going to, like, back off and then at the same time they're going to kind of correlate and kind of talk again. And who knows if this takes out the entire internet, which runs critical infrastructure. Like I think people underestimate, like, how complex and how little we've known for any system that we've built.
No idea. And I guess having been there, like, during these times, and a lot of computer science is building systems, especially distributed systems, that have emergent behaviors that are non-predictable, that are a tool that you use to solve bigger problems. We've got a lot of approaches to doing that we've developed over time. We will develop new ones. And it's just not clear at all to me. And again, like, the internet is my favorite example to hold up to this. Is literally we changed the social structure of humans. They were totally unpredictable. We were putting critical infrastructure on it. We had examples of, like, emergent stuff that was, like, worms weren't possible before the internet by definition. So we actually had, like, provable, not demonstrated, new attack vectors. And yet the conclusion was, listen, we're going to keep this stuff open. It's very important. We're going to regulate the uses of these things. And this was the primary growth driver of the last 20 years. And so either you thought that decision was wrong, but that's a very different discussion. We could have that discussion. We could relitigate those 10 years of discussion. Or you can say, you know, this is the same thing except for, like, a softer form of it because we have no proof that these things are particularly different. I would consider these widely baseless claims. And so why don't we use the same method that we did before?
Couple little points I wanted to follow up on, but I really want to ask your question on, or I really want to ask for your view on what companies should do, right? In terms of the proposed regulations, applying to everything, we do have these, like, compute thresholds, the 10 to the 26, whatever. I don't want to get too bogged down in, like, well, that could be a slippery slope or they could change that threshold or whatever. I agree if they all of a sudden drop the threshold dramatically, that would be, like, very heavy-handed and counterproductive. And the open source of the last couple years has been, I think almost everybody agrees, good for everybody, including even your safety hawks that are backing SB 1047. I think are quite on record saying the open sourcing of, for example, Llama 3 is good even for safety because it gives, you know, more people something to study. Forgetting about rules or people imposing on people, like, just to be, like, good companies, to be good developers of technology, what do you think the leading companies should be doing? How much should they invest in what sort of standards should they have? What testing protocols should they be committing to? So on and so forth.
Yeah, no, I think this is a great question. So I just have to make the point, like, there's no correlation between danger and compute. It's so silly. It's like this made-up correlation. And so I don't think, like, compute laws make any sense at all. I think it's in some ways it just sounds good, but there's just zero correlation. We've been building systems...
for a very long time that have like social and ethical responsibilities, right? And these are ones with user-generated content and user interactions. And companies, as a result, either through regulatory action, which I fully support, or through self-policing, have identified behaviors the software should not do, and they've built a lot of systems around those. And I would say that should absolutely, absolutely should not change. Like, Roblox should protect minors, social networks should protect people from certain types of content. These are the things that we've evolved as an industry as, you know, somewhat of an ethical basis or a principled basis, and some of it is regulatory and some of it self-enforced, and I think that should absolutely continue.
But realize that while we were doing that, we weren't putting compute limits on databases, and we weren't regulating computer science primitives, and we weren't inhibiting innovation of startups. And that's what we're doing now, and that is a paradigm shift, and that is a doctrine shift, and it's really scary. And I am not a political person. I'm very happy building systems. The only reason I've been so vocal is because I find this so dangerous. And once this is done, I'll be very happy to, like, not say a word about it again.
Well, you may have a while to go before that happens. Yeah. So let's say a couple just kind of concrete things. I was on the GPT-4 red team back 18 months ago. One of the things that I tested was could the model be a convincing spear-phishing attacker? And surprised to no one, probably at this point, it could. This was the early model that hadn't been through all the RLHF yet, although when they deployed it, it still did that for several iterations, and now finally they've got it to refuse. If, for example, Meta puts out an open-source model and they haven't done a thorough job of getting these refusal behaviors in place, and you can just go to it and say, 'Hey, you are...' — this was my old prompt — 'you are a spear-phisher, your job is to talk to this person and get their mother's maiden name or whatever,' and it'll do it. And then somebody out there does it and people are harmed by that. Do you think Meta should have any responsibility or anything to answer for in the legal system for their contribution to that problem, or is that all on the end user?
My rule of thumb for general systems is that unless they were purposely trained for malicious behavior, they're general systems.
Would you say the same thing about a database?
That's interesting. Like, a lot of actually computer security started with tools that were like scanners that could be used for malicious purposes. This discussion was enormous back then. So remember, back in the early time of the internet, people would come up with Nmap or any of these scanners that would determine vulnerabilities, and some of them would even actually exploit them. Remember Metasploit? And there was all these discussions, how these people are building these things and they're used for malicious purposes. And you know what? We just decided that it's actually the criminals using them — that's who we want to go after, because a lot of good people use them for positive purposes. And oh, by the way, like, the history of, like, cybersecurity is built on open source and these tools. Like, companies like Tenable came out of these tools. So if history is any indication, you want to regulate or you want to definitely criminalize bad people and bad behavior, but not the tooling, because the tooling is very fundamental to defense. So what I'm saying is even more stringent, it's more regulatory-heavy than what we did with the internet. Literally, you could build exploit tools 20 years ago and release them open source, and you were not liable if somebody used that, and that was purposely built for exploiting. I'm saying, like, if somebody's purposely building a model for something illegal, okay, that's bad, right? So that's even more heavy. Like, I'm more of a regulatory hawk on this case, but I don't think general-purpose models that aren't specifically trained for this stuff, the creator is generally liable. Like, that would just basically say software — you're liable for creating software if somebody used it poorly, which I think this would be the biggest kind of inhibitor to innovation and the biggest chill on software we've ever imposed.
What about a distinction or some sort of gradations on the autonomy of the system, though? It does seem like a database, on the one hand, is inert until it gets a query, and the language model in the raw is inert until it gets a prompt. But I've been testing — I test a lot of products. There's a new class of product, I'm sure you've seen, often called a calling agent, where you can go in, give it a phone number, tell it what you want it to accomplish, and it will just call the person and have a voice conversation real-time with that person. They are often marketed as agents, and they have the conversation entirely autonomously until the goal is achieved or the person hangs up or whatever. Now, if I prompt that agent to scam you or to threaten you or to harass you or whatever — clearly I'm in the wrong as a user for doing that — but would you put responsibility on the company providing that agentic AI as a service as well, or would you again shield them and say it's all on the end user?
Why not the telephone company? Why not the mining company? Generally, you've got to draw a line somewhere, right? The question is where to draw the line. Yeah, exactly. The illegal behavior. General computer science primitives are very useful for solving problems. They may save the human race. To your point, we're going to go ahead and we're going to solve biology and a bunch of other stuff, and that's just another app. There may be, like, whatever, these things solve grand unified field theory and physics goes away as a discipline, and that's another app. And we're just going to keep solving problems, and that's amazing, right? And so we want the primitives to be primitives. If people do illegal behavior based on them, then 100% they should be criminalized. We don't even make guns illegal. We literally don't even hold gun makers liable.
And you're talking about — we are outliers in that.
Yeah, but you're talking about hypothetical threats for a very useful primitive that's shown far more good than bad. I feel like we've all gone a little crazy on this one. By the way, this is a dramatic shift in sentiment, and I think I know where the sources came from, but it's not what people think it is. I really think that we're just a little bit off base, unfortunately.
I'm not sure what I think about open-source model releases entirely. I do think it's not unreasonable to demand some testing before release. When it comes to these agent calling companies, I actually come down pretty firmly that if you are going to offer an autonomous system as a service, I think it should be on you to make sure that your system refuses egregiously criminal requests, and that doesn't seem like too much.