LIVE CLIPS
EpisodeĀ 11-18-2026
What's your thought process? Yeah, building stuff yourself has its own set of issues. To your point. I mean, I think the, I think being very thoughtful about what kind of data you're sharing with vendors, it's not just here are all the vendors that I have, it's like, okay, which ones are getting customer data? Those have to be absolutely, absolutely patched down. Which ones are getting. There's just like different levels of obviously trust and diligence that you want to go and do, depending on what you're doing. And I think there's actually a lot more 80, 20 that folks can be doing even on just thinking about, okay, like this particular kind of like thing that you're working on, does it have to have customer sensitive data? Like, are there ways that you can go and anonymize or whatever you need to go do that makes all of that safer? I would say I don't. Despite us being building Devin and all the things, I don't think that is the case, that we're at the kind of full SaaS apocalypse, build all software in house thing. And a lot of that is actually because to your point, it's like there are a lot of details involved in going and managing software still. And I think the reality is making it 10x easier to go and build software is amazing. It gives you a lot of leverage to go do a lot of the things that you want to go do. It doesn't actually change the math of what is your core competency that you really care about versus what are all the other things. I mean, something like Salesforce, which people have probably, I don't know, somebody can do the back of the envelope calculation of how many hours of software engineering were put into that. Maybe it's like, I don't know, 10 million hours or something. You probably don't want to spend 1 million hours going and doing it. You could, but the purpose of software, I would say is to kind of like to do the replication that frees you from a lot of those things. And so I think there's still obviously a lot of that that should happen, even as this gets more and more efficient.
Of course. Oh, and by the way, that introduction was happen happened before there were any export controls in the first place. Come on. Yeah, yeah, yeah. So how do you fight back against an op? I mean you, you, you put out a post with some detailed information. I was just get the print out. Maybe I should just pull it. I'll pull it up. I could, I could tell you little pearls of wisdom on each of them. Hold on a second, guys. Let's dig through it. Is it your pin tweet? Lightning round, Op defense, Lightning round. Let's find it. Hold on, I'm pulling. I've done a lot of tweets. This had a little time on my hands this morning to do some writing. Send along to someone who, you know, who may benefit. Practical principles. This is literally, by the way, this is super interesting because a modern day struggle. I have it right here if you want to read it. It's like, I need to read my own stuff. It's so weird. Number one, own what you did. But fiercely resist accommodating the mob. Resist owning half truths or actions slash behaviors you didn't do. So, so what happens is these ops are. It's about mob mentality. So what happens is a large mob of people basically is brainwashed into thinking you're a bad person and did incredibly bad things. Now there's usually some thread of truth, but it's a fabrication in sort of the nature of what occurred, et cetera. Right. And the truth here was the affairs, for instance. Yeah. And then you're like, okay, well the problem can happen if you're a human and you're like empathetic generally you're very susceptible to just taking on what the mob thinks. That truth no longer is what is true or objective. It's only what the mob thinks. And you've got to avoid that at all costs. And you need to own the part, you're part in it. But you need to fiercely resist the psychological need to. Or it's not a psychological vulnerability of taking on what other people think is true. Because if you don't resist that, you're done. Two, the OP is not about.
Out. Good call. So yesterday we just released Devin bots. Okay, good. It's live, so we can talk about that now. But yeah, we had a nice launch on Twitter. Okay. Obviously all that, I think in one line. Basically it's these persistent agents that can actually own outcomes instead of tasks. I think it's basically taking Devin one step closer. I mean, the whole vision, even two, three years ago was, you know, building the AI software engineer, the virtual teammate and so on. And I think it's taking it one step closer to that, where it has memory, it can take on a full project, it can really, really delegate and run things on mass. You can own a goal. So let's separate the technical from the functional. What, what, at what level of abstraction are we prompting at this point? Are we just saying, like, build the website, make me money, like, make me happy. The Ebitda machine. Right. You know, it'd be nice if we had some more revenue. Yeah, because. Because we're, we're going up the abstraction layers, I think, and we're closer to the top. But I think with engineering tasks specifically, it's like, I want to build this application and then we're going to get to a point where you guys just give them a price and you hit confirm. So I think that's right. And I think it is already going, like, much closer. I mean, a good example of this. So obviously, Devin has a mobile app. We've had an iOS app for some time. We have an Android app now. There was not a single human who worked on that. So there is just one Devin bot whose job is basically like, look, look at the iOS app. Whenever there's new changes that come in, build the whole thing, test it out, make sure you make it mirror the behavior of the iOS app. It just works. Okay. It's kind of prompt is basically like, Android app, please. That's right. Okay, yeah, yeah. Similarly, it's like, you know, we run a lot of obviously, like inference kernels and things like that. We have this always on dev and that's just like, okay, just go optimize. You know, it's actually a very nice use case, I would say, for bots. It makes you feel the RSI at least like a little bit, because it's like you have a very clear, you know, exactly what the token output is supposed to be. You can run all the benchmarks in terms of, like, what your GPU throughput is and so on. And it's just like as you're finding optimizations for your specific, you know, set of prompts you can go and do that. Yeah. And improve your. So then under the hood, how much rapid.
With my friends, because, like, I'll. I'll just get roasted otherwise. Yeah, of course. It's a real thing. It works. It's a real thing. This last couple weeks had to have been like, PTSD for you. No, not ptsd. Just like there's wisdom that was gathered over time. I mean, I went through it. Yeah, for sure. And there's a friend who was going through it. And for me, it's so clear what it is. I was probably one of the early people to be like, all right, guys, here's the 12 principles of how to fend off an op. Yeah, but that was like Monday of last week. That was like. That was Monday of last week. How did you identify that it was an op? What triggers that for you? You know what I mean? Because for a lot of people, it's just like, oh, there's a bunch of news articles, something's happening. No one's behind this. It's just. Just me. It's like, you know, it's a sixth sense, you know? I don't know, it's like the. It's like when you see those murder mystery things or those true crime things, and there's like this woman who basically knows where the crime happened and all the details, but she's not connected anyway. She's a psychic. That was. That's my psychic. Psychic for corporate ops. I'm a psychic for these types of things because I've seen a lot of them Mar. For. For me, it was six months of ops. Yeah. One a week. Yep. Steady as she goes. Sunday night, every Sunday night, it would hit. You're, like sitting there literally, like, Sunday afternoon, you're like this. You're like, oh, what's going to happen today? Wow. Six months. Yeah. Beat down. Beat down. Right. Well, the craziest thing with this time.
Given the situation, the tightness of memory across really multiple years now we're majorly focused in expansion across the globe, certainly especially in the US with more than 250 billion of investment coming. A massive facility underway in Boise, Idaho right now. Congratulations. Thank you. I saw the news. I was very excited. Yeah, we're really excited about that. And even bigger facilities underway in Clay, New York and expansion in Virginia also. So just a number of the biggest projects we've ever done, some of the biggest industrial projects the US has ever seen. And bringing more memory to the market. Three American cities. Is that just because you're purely patriotic or is the United States uniquely good at building huge manufacturing centers? Now it seems risky, it seems contrarian to not go to the cheapest location where the labor's cheapest. I'm, I'm a bald eagle and I applaud you for building an American. I love it. But why, why, why is it, why is it a good strategy? We're, it's a good strategy for a number of reasons. But also I'll add we are, we have to expansion projects in a number of other countries as well, across, across Asia. And it's just a lot of focus, uniquely in the US now because of, primarily because of the customer base in the US they're here. And certainly the, you know, the aspects of having more US supply to match up with those customers, really important in today's world. And so it's really balancing our, our output across, across the globe. But, but definitely the opportunities in the US are RDs, you know, in a number of countries, but our base is in, in the US and you know, more and more customer partnership becoming important in how we build our products. So it's great to have manufacturing in the US close to those customers. When you build a manufacturer.
Suits. I promise you that's not the best version of Jensen today. Okay. I promise. Yeah, we, we. We've been debating going into the earnings call yesterday. I mean, the, the team obviously did the absolute best they could given all the chaos, but it was like. It just immediately was like. It wasn't. It was a different company. Like, right away. Yeah. Take me deeper on the pitfalls of letting a company go to the suits, because I can imagine, you know, a Tesla without Elon, it just collapses. It doesn't work. But then I go to an Apple post Jobs, where, yes, you could say the innovation slowed down, there were product misses. But financially, that company continued to perform, arguably because of all the work Steve Jobs did. But is there no chance for Nvidia under suits? Here's the thing. Yeah. First, the Apple transition was a planned one. Yep. Okay. And it was an optimistic one. Totally. What I mean is, the day after Steve passed, they weren't talking about him. They weren't like. They weren't like, we need to rid the ranks of all people that are for Steve. They didn't. Totally not at all. They celebrated. Yeah. Him and what he built. They also had Apple University where they were training everyone in the Steve Jobs mindset, in the methodology, obviously you end up in a different place. What can happen when a new person comes in and it's done by a. There's a board element to it, like there is here, is that the board, of course, wants to look smart and not stupid, that certain decisions were made that they approved or didn't approve, whatever it is. Right. So, okay, they brought the new person in. They need to look smart. So they need. They need the new guy. They need that decision to look good. That new guy, his number one KPI. You guys want to guess? Keep my job. Yeah. Keep his job. Like, no chaos. Keep my job. Like, the idea of, like, when the new guy ultimately finally get a CEO, that person, his or her job will be keep my. The number one KPI is keep my job. Which means that is a natural resistance to Jensen coming back. Yeah. And so the, you know, ideally you can get an executive that comes in that is also empathetic and open to Jensen coming back. Because if that person is not really gnarly, then you got to go. Then you go. Annual meeting, sort of proxy votes for. For board members, that whole thing. Yeah. Which is still a thing. I think that's going to happen in June. There's some chance you could do it earlier. Okay. Yeah. So are you.
Like, I'm. Right now. I do think that there was some. I do think there was clearly some. You know, I don't know. I don't know. Jensen heard him talk, obviously, a bunch of hours, but I do think there was some kind of denial going on because you hired the crisis comms firm last year, and you had every opportunity to lead from the front and potentially, like, take a leave of absence, which still would have sent the stock down, but you wouldn't be in the situation where you resigned. Yeah. And then now you have to get other people to kind of rally and say, hey, we. We actually want this guy back. Yeah. Look, I think, you know, this gets into the personal side, but, like, Jensen is a very, very good person. He's so good that. That, you know, when there are personal failings, it's, like, devastating. And I think it just. It probably. And again, this will be a little bit of speculation on that, but, like, it's. It just took a little time for. To work through that, I think. Yeah. And again, there's no shirking of responsibility. But if you. If you get affected to such a degree that you can't, then go to, you know, point two and point three here. Point three is, no matter how bad it gets, nothing is as bad as it seems. I'm happy to talk about that as well. But, like, you can't get to the other points if you don't first go. I accept my truth. I take responsibility for it. I did things that. Not me. I'm just saying. Jeopardized, you know, Then you go and you say, what. What is the best version of me today? Yeah. And it's not, by the way. It's not letting Nvidia go to the suits. I promise you that's not the best version of Jensen today. Okay. I promise. Yeah. Going into the earnings call yesterday, the team obviously did the absolute best they could given all the chaos, but it just immediately was like,
Of the op, too. He may not even know it, but, like, somebody said, hey, check this out. Okay. Yeah. You know? Yeah. Yeah. That's how this stuff happens. Yeah. So the so on number two, look again. If you do number one, and you own your truth, you own what happened and what didn't happen. Don't own what didn't happen. You need to realize you need to clearly identify your enemies and move forward. But do you need to go public with an attack counterattack on your enemies, or should you sort of turtle shell and keep your mind ready? Guys, I did the turtle shell thing. I don't. I wouldn't recommend. Okay, I think you get. Look, the bottom line is you need to get a war room up and, like, strategically handle it. Some things you go, you know, we don't need to do this. Yeah. Some things you go lean forward and it's a strategic response and not just one at a time, which is where I was sure. But you're playing defense and reaction. No, Sunday night, dude, and you get the. You get the text from your comms person. It's like, hey, we need to talk. Yeah. And you're like. You literally bend over. You're like, oh, no. The pain begins. And it's almost like a physical response because it's a Pavlovian physical response because the pain you went through the four the week before that, 10 weeks before. They're just training you that Sunday night. Pain time. Pain, it's. It's really. It's crazy. But. Yeah, that's why it's crazy. I don't have ptsd. Given that. Yeah. Yeah. But if today anybody texts me and says, hey, dude, give me a call. I'll respond. I'll go jump scare. I'll just respond. I want to talk about. Can you put this on a scale of 1 to 10? Like, I'm right now. I do think that there was some. I do think there was clearly some. You know, I don't know. I don't know. Jensen heard.