1% better

Databricks CEO: AGI Is Already Here, Why Companies Are Behind, and the Superintelligence Debate

How far are enterprises actually from using AI in meaningful ways, and what is standing in their way? Ali Ghodsi, CEO of Databricks, built the company from a...

1h 2m

Summary published by , updated .

All-In Podcast

Key Takeaway

Build an ontology of your organization before you try to automate it.

Start by connecting your meeting transcripts, Slack messages, and documents to a single system that maps who does what and how decisions actually flow. Even a rough version of this, covering one team or one workflow, will reveal gaps between your org chart and how work really moves.

Ali Ghodsi argues that most companies are still using AI as a glorified search engine because the AI has no context about the organization. Without that context, even a very capable model cannot help you, any more than a brilliant outside consultant could if they were never allowed into the building.

Episode Overview

How far are enterprises actually from using AI in meaningful ways, and what is standing in their way?

Ali Ghodsi, CEO of Databricks, built the company from a UC Berkeley AI research lab that could not get industry to pay attention, into a business now running at $7 billion in annual revenue. He argues that most organizations are stuck at the chatbot and coding-assistant stage, and walks through why closing that gap is harder than it looks.

The conversation covers three main areas:

  • The enterprise AI gap. Four specific problems, context, security, cost, and data sovereignty, explain why large organizations are not yet running fleets of autonomous agents.
  • How Databricks runs itself. Ghodsi shares his screen and shows Genie, an internal AI system built on a live organizational graph, being used to analyze HR survey data, org structure, and engineering output in real time.
  • Recursive self-improvement and the superintelligence debate. Ghodsi lays out four conditions that would need to be true simultaneously for RSI to produce the kind of runaway AI described in Nick Bostrom's 2014 book, and explains why he does not see those conditions being met.

Main Insights

1. Four problems block enterprise AI, and most companies have not solved the first one

Organizations stall at the chatbot stage not because the models are too weak, but because four distinct problems pile up before any serious automation can happen.

Ghodsi lists them in order:

  • Context. The AI is not in the meetings, and many large organizations, including major banks, refuse to record them for liability reasons. Without that context, the model cannot help.
  • Security. Connecting an agent to all your data multiplies the attack surface enormously for a 10,000-person company.
  • Cost. Token costs scale with usage, and few companies have seen revenue grow fast enough to match that curve, which eventually triggers a CFO intervention.
  • Data sovereignty. Using a closed external model risks your proprietary data being absorbed into the next version of that model.

Ghodsi's argument is that you have to solve all four before you see real productivity gains, and most organizations have not cleared even the first hurdle.

2. An organizational graph gives AI the context it needs to do useful work

The reason most AI deployments stay shallow is that the model has no picture of the organization: who reports to whom, what decisions were made last week, or which team owns a given problem.

Ghodsi's approach at Databricks is to build what he calls an ontology, a continuously updated graph of people, relationships, documents, meeting transcripts, and Slack conversations. During the conversation, he pulls up Genie and uses it live to find that work-life balance scores and action scores are not causally linked, to identify a manager whose team is working hard but feels heard, and to flag an engineering org with an unusually deep reporting chain.

The useful shift is from asking people what happened to querying a system that already knows. That removes the game of telephone between frontline employees and the CEO, and it makes it harder for a single person's framing to shape the whole picture.

3. The L-curve in engineering output points to who has automated and who has not

When Ghodsi looked at pull requests across Databricks' 2,000 engineers, the chart had an L-shape: a small group at the top committing far more code than everyone else.

The explanation turned out to be straightforward. The top performers were running automated pipelines; the rest were not. What made the finding more interesting is that the high-output engineers were not necessarily spending more on AI tokens. Some were spending less.

This suggests that the advantage in AI-assisted work comes from how you route tasks across models, not just from using more compute. Simpler questions can go to smaller, cheaper models, while harder ones get escalated. The engineers who figured that out early are pulling away from those who have not.

4. Recursive self-improvement needs four conditions to be true at once, and none are currently met

A lot of concern about runaway AI assumes that because models are writing most of the code, the loop has effectively started. Ghodsi thinks this reasoning skips several steps.

He lays out four conditions that would all have to hold simultaneously:

  1. Training runs get faster at a super-linear rate, not just incrementally.
  2. Each run requires less compute, not more.
  3. Accuracy improves broadly across tasks, not just in the reinforcement-learning domain.
  4. All three of the above repeat in a compounding loop, with training time and cost falling continuously.

Right now, he argues, training runs are taking longer, requiring more hardware, and still depend heavily on human data cleaning and domain-specific reinforcement learning. The flywheel described in Bostrom's 2014 book does not currently exist. He adds that even if all four conditions were met, that would be a precondition for dangerous superintelligence, not a guarantee of it.

5. AI-driven GDP growth will be slower than the labs predict

There is a gap between what AI can do in a well-prepared environment and what it can do inside a typical large organization, and Ghodsi thinks that gap will take longer to close than most AI companies expect.

His reasoning is concrete: a major bank CEO told him they will never record internal meetings. If the AI is not in the meeting, it cannot act on what was decided there. Getting even one large organization through all four of the blockers he described, context, security, cost, and data sovereignty, is a multi-year project.

He draws a parallel to the early internet, where a small group could see what was possible while the majority were on dial-up and could not yet imagine streaming video. His estimate is that meaningful GDP movement from AI is a decade or more away, not the two-year timeline he hears from the labs.

Frameworks or Models

Four conditions for recursive self-improvement

Ghodsi uses this framework to evaluate whether the kind of runaway AI described by Bostrom is actually approaching. All four conditions would need to hold simultaneously and compound over time.

  1. Training speed. Each new model trains faster than the previous one at a super-linear rate, not just incrementally.
  2. Resource efficiency. Each training run requires less compute, not more.
  3. Broad accuracy gains. The model improves across all tasks generally, not just in the specific domain where reinforcement learning was applied.
  4. Compounding loop. All three of the above repeat continuously, so that training time and cost keep falling while capability keeps rising.

Ghodsi's view is that none of these four conditions are currently being met, and that the absence of the loop means RSI as a near-term threat is not supported by what he observes in practice.

Organizational ontology

A continuously updated graph that maps the intelligence of an organization, used at Databricks as the foundation for their internal AI system Genie.

The ontology connects:

  • People and relationships. Org chart, reporting lines, and role definitions.
  • Communications. Meeting transcripts, Slack messages, and email threads.
  • Documents. Spreadsheets, presentations, and written decisions.
  • Metrics. Survey results, engineering output, and cost data.

Rather than searching live for answers, the system reasons from this pre-built graph, which means it can answer questions about culture, decision patterns, and organizational structure without requiring someone to compile the data manually. Ghodsi describes it as giving the AI the context it would have if it had been in every meeting.

Notable Quotes

"They're just using AI in very rudimentary ways. They're just using it as a glorified Google search."

Ali Ghodsi

"If it's not in the meeting, it's useless. It doesn't matter if you have Terry Tao or you have the greatest mathematician in the world. If they're in the cold and they don't know what decisions or what you're doing in your meeting with hundreds of thousands of employees, there's no way it can help you."

Ali Ghodsi

"I actually think we already have artificial general intelligence. I've been saying it since last year."

Ali Ghodsi

"I actually think GDP will move very slowly and it's gonna take decades."

Ali Ghodsi

Action Items

Suggested exercises inspired by the conversation.

  • 1
    Map where your organization's decisions actually happen

    Most leaders have an org chart but not a picture of where real decisions are made and by whom.

    1. Pick one workflow or team.
    2. List every decision point in that workflow from the past month.
    3. For each decision, note who initiated it, who was consulted, and how long it took to resolve.
    4. Look for decisions that required multiple meetings or escalations to close.

    This gives you a starting map of blockers before any AI tool is introduced, and it shows where context is currently being lost between people.

  • 2
    Find your own L-curve

    Ghodsi found that a small group of engineers were vastly outproducing the rest, and the difference was automation, not raw effort.

    1. Choose one measurable output in your team: code shipped, deals closed, articles published, or similar.
    2. Plot output per person over a recent period.
    3. Identify the top performers and interview them briefly about their workflow.
    4. Ask specifically whether they have automated any step that others are still doing manually.

    The goal is to find the practice that explains the gap, then share it.

  • 3
    Run a blocker audit on a current project

    Ghodsi tracks the number of human blockers across Databricks as an operational metric. You can do a lightweight version manually.

    1. Take one active project that is behind schedule.
    2. List every step where progress stopped and note why: waiting for approval, missing information, a meeting that has not happened yet.
    3. Categorize each blocker: legal, budget, internal alignment, or missing data.
    4. Count how many of those blockers required a human decision that the AI could not make.

    This reveals whether the bottleneck is the AI tools or the organizational structure around them.

  • 4
    Test whether your AI tool has context or is just searching

    There is a practical difference between an AI that searches for answers and one that already has an organizational picture it can reason about.

    1. Ask your current AI tool a question that requires knowing your organization's recent decisions, such as: what did we decide about X last month, or which team owns Y?
    2. Note whether it retrieves a document or reasons from connected context.
    3. If it fails or retrieves an irrelevant result, identify what context it is missing: meeting records, Slack history, org chart, or document ownership.

    This tells you where your context gap actually is.

Go deeper

Full Transcript

Read or copy the complete episode transcript.

So it was kind of out of despair that we started Databricks because no one else is listening to it. At that time, there was zero interest in AI. Now, I think we have all the intelligence we need to completely transform the planet. It's not possible to have a thousand agents doing stuff realistically, am I correct? They're just using AI in very rudimentary ways. They're just using it as a glorified Google search. We're actually getting into like management money ball, aren't we? So if the token cost is going up exponentially, is your revenue at your company going up exponentially? But I actually think GDP will move very slowly and it's gonna take decades. Are they a little drunk on their own success? Just because 98% of the code is being written by AI, we don't have RSI. If it automates the last 2%, who cares? When are you going public? ♪ I'm going all in ♪ If you were building a global financial system from first principles today, you wouldn't build it on 50 year old legacy rails. You'd build Airwallex, one AI native platform for global accounts, cards, and payments. Airwallex is designed to make the entire world feel like a local market. Others are bolting AI onto broken infrastructure, but Airwallex was built for the intelligent era from day one. Stop paying the legacy tax and start building the future at airwallex.com slash all in. Airwallex, built for the future. ♪ I'm going all in ♪ All right, everybody. Welcome back to the all in interview. We're so lucky because all of these amazing leaders in the world, CEOs, politicians, scientists, they watch the show. They're part of the community. And Ali Ghazi is one of those individuals. He, of course, is the CEO of Databricks, a private company that has been doing incredible. I don't know why it's not public yet. I think a lot of people are asking that question. We'll talk about it today. In 2015, they were doing 1.5 million in revenue. It's August, or the rumor I heard, August, 2026. Ali, $7 billion run rate growing 80% year over year. And obviously you've got a lot of competition, the snowflakes of the world, et cetera, but this is a tremendous business. And we're going to talk a lot about how you're using AI to run this incredible business. We're going to talk about recursive self-improvement, but welcome to the program. And then maybe you could tell the audience a little bit about what you do at Databricks and how it became so successful. Yeah, happy to do that. Thanks for having me on, excited for this. Yeah, so we started the business in 2013, but if you rewind a little bit before that, we were all at UC Berkeley, there were about 20 of us, and we were actually part of a lab called AMP Lab, which was, I think, the largest AI research lab in the world at that time. And we were trying to figure out how can we combine data processing with AI? And we came up with really interesting things, but the industry was just not ready for it. So we were trying to get the industry to adopt this technology, and they weren't. So it was kind of out of despair that we started Databricks because we thought, you know, if we don't start a company around this, no one else is listening to it. At that time, there was zero interest in AI. Actually, it was called machine learning at the time, and AI was just robotics. So that's kind of like the beginning of the story. And for people who don't use the product day in and day out, who aren't in the industry, what's the goal of the Databricks product suite? What do you do? I know you released some new products today, so happy to talk about those as well. But conceptually, you got there so early. Obviously, machine learning, Google was built on that, Facebook and their ad network, a lot of interesting services, Uber and their routing algorithms. Maybe you could talk a little bit about where Databricks started and what it's become and how it's generating billions of dollars in revenue. Yeah, so the first use case, actually, it was the first use case ever was at UC Berkeley when we wanted to help Netflix recommend better movies so that people would watch more movies. So it was like a recommendation algorithm, AI use case that started the whole thing. And then we thought, you know, more organizations probably, probably every organization will need a data science team that can do this kind of AI stuff. And it was kind of bold at the time. There was a lot of people that said, no, no, no, AI is just for ad tech, the ad companies need it. But we thought, no, no, this is going to be a bigger market. And actually we had a lot of debates internally. We weren't sure it was going to explode. So we got into it and then we realized when we started the company, we realized why they're not doing it, why it's so hard. Because basically all the organizations out there in the world are bogged down. They have legacy software that they've had for 30, 40, 50 years. And some of them, you know, companies have been around for a hundred years. You know, things are moving slow. They have a lot of processes. There's, you know, a lot of compliance, a lot of regulatory, a lot of security, but all these things have gotten worse with generative AI in the recent years. So basically what was missing from our research at UC Berkeley was that we didn't think about the security, the governance. So what we did the first bunch of years is that we figured out how do we take this technology that lets you process all your data in an enterprise. So, you know, organizations have a lot of data. The most important data they have, actually people don't talk about it. The most important data any company has is the data on the core product that they have. Like for you here, it's this podcast, you know, the data on that. Someone else might be selling insurance. Someone else might have, you know, a drug. It's the data that comes out of that. That data doesn't sit in CRM. It doesn't sit in human resource management. In fact, it probably wasn't even tracked. I remember in the early days of the internet, they'd be like, hey, would you like this log file? And I'd say, okay, yeah, keep everything. And they'd say, okay, well, you got an $8,000 storage bill a month. And I'd be like, okay, delete it. And they're like, well, we could roll it up and keep some of it. I'm like, well, who's ever using the open rate on our emails? Who cares about that? You know, we send the emails, that's it. But then that changed. And was storage and compute and cloud computing a major accelerant to this big data movement and then eventually machine learning? Those were kind of the waypoints in this movement. Yeah, before we started in 2013, basically people were running their own data centers. And when they're running their own data centers, you have to buy machines. And the machines came with storage and compute combined. So if you ran out of storage, you had to buy more machines. And the IT departments of every organization were busy with this. What the cloud enabled was to just completely decentralize this and separate compute and storage so that you could just imagine you have infinite storage and you just dump everything there, okay? And if it's gone cold, so the data is old, it knows how to archive it so that it becomes almost free to store it. And then you could get the illusion of as much compute as you wanted. And then of course, you could start running machine learning on it. And then eventually GPUs showed up. So it kind of transformed everything. We've had everything, the whole farm, on just being a cloud company. We bet everything on AI, the use cases of AI, and we bet on open and open source. And at the time, actually, all three of these bets were controversial. I had a standing bet with one of the most important analyst firms out there where they said, it's a strategic blunder. You're going to go under because you're betting on the cloud. And it turned out actually the only reason we succeeded was because of these bets, because they were contrarian, because other people did not agree with them. So we got a headstart for many, many years. And then eventually when we happened to be right, then we were so far along and we got too big that there's too much momentum to stop it. It's so funny you mentioned this Netflix algorithm. Netflix started obviously in the Bay Area as DVDs that were mailed to you in an envelope, and then you had this queue. And it was critically important for people who don't know the Netflix prize. This was in the 2008, 2009 time period. They put a million dollar prize out to any computer science team that can make the algorithm, I think 10% better at predicting what movie you would give four or five stars to. So they just took all their data, they released it, and then they got probably $50 million worth of work from computer scientists around the world. It was the first time an X prize, and I think X prize and this were around the same time. And they were all inspired by those old prizes to like who could circumnavigate the globe, who could solo fly over Amelia Earhart, who could solo fly over the Atlantic or the Pacific. It was like a very interesting moment at time. And that hit AMP, right? And AMP, the group was algorithms, machine learning. I don't know what the P stands for. It was for people actually, because we thought that the AI is not good enough yet. So it needs a little bit of human nudging. So it's actually this kind of human feedback was already there. We were like, we do need the human feedback because this last mile is just too hard for AI to figure out itself. So we had people there as well. Putting the people in there makes sense because Berkeley's a little hippy dippy, Freiburg's alma mater, obviously. They were like, we need some people in the middle of this. We had Ben Horowitz on, sat in the other week, and he was like, the best explanation I've ever heard for why we are going to be able to control the rollout of superintelligence and this jump between artificial intelligence or artificial general intelligence and superintelligence that gets recursive and runs off with it and P dooms us all and we're all going to die. Sentiment by some people came from you. So please explain your thesis here. And then I'd like you to go even one step further and talk specifically about maybe the culture in the Bay Area, perhaps even the East Bay and this group of people. I mean, happy to get into it. I think there's sort of two different things happening at the same time. On the one hand, I actually think we already have artificial general intelligence. I've been saying it since last year. And I based that on the kind of consensus we had in that AMP lab where it was, I think, the largest AI lab at the time in 2009, 2010. And that definition of AI that most of us had, AGI, we already achieved that last year. And I wasn't actually sure about this. So I actually went and checked with some of the people that were in the lab, like, hey, is it just me? Am I hallucinating? And they said, no, no, no, that definition for sure. But we've moved the goalpost. So I actually think we have all the intelligence we need. And actually, if you happen to stop all progress right now, I think we have all the intelligence we need to completely transform the planet, okay? But that's the idea. They do all intelligence work by humans, right? I mean, if it solves this latest cohort of math problems, and we're just starting to build harnesses and build out the infrastructure, I guess your statement would be correct. And I kind of am in line with you. We've hit artificial general intelligence. It just hasn't been distributed, equally distributed yet. Yeah, so the labs and a lot of researchers, they're kind of obsessed with superintelligence, okay? When I say superintelligence, I mean it the way it was defined by Botstrom in 2014 in his book called Superintelligence. And there he's talking about something completely different. He's talking about something that can do a millennia worth of thought. So like 1,000 years of human thought, it can do it like in a minute, okay? All of mankind in a minute. It thinks in 11 dimensions. It's so much faster. Just a single agent is just many orders of magnitude. Imagine 1,000 times faster than any of us, okay? And that's just a different thing. It can write a novel PhD thesis instantaneously and so on. So I think the labs are on the quest of that. And in that way, by the way- And so just to summarize that there, the ability to write an entire unique PhD thesis instantly, which do we even have the amount of compute in your mind to do something like that today? If everybody got together and said, hey, today we're going to give all our compute or for the next hour, just as a thought experiment to this incredible mega prompt, do you think it would actually happen? Is it a computer issue or is it a model issue? Well, actually the AIs are kind of slow. What we have to do is we have to paralyze them and have many of them. And we have to have them to collaborate with each other. So it's actually not the way kind of that he wrote it down. He had also intelligence in the book of how it can be communities of intelligence. But I'm just saying the labs and many of the other companies are focused on this. And that's why they're so obsessed with the math, the clay problems, the seven millennial problems and so on. But I argue that the biggest challenge that's facing us is how do we actually just make this AI applicable inside organizations? That's what Databricks is focused on. We just want to help all these organizations. And when I go talk to organizations out there, enterprises, I see that they're just using AI in very rudimentary ways. They're just using it as a glorified Google search. They're using chatbots all day. And instead of typing in Google search and getting 10 blue links, and then looking at the 10 blue links, the AI just does that for them. The second thing that they're doing is they're doing coding. Okay, and with the coding, actually they're not seeing enough speed ups. They're seeing maybe like 20, 30%. I ask them this question every day. I'm in meetings every day with customers and I ask them these questions. That's kind of what reality looks like. I always ask them, how many of you have thousands of agents running around automating all of work and doing co-work for you and so on? It's just not happened yet. Now they might be running a half dozen agents, a dozen agents, like somebody who's at the forefront might actually be coordinating against that many, but the human still needs to be in the loop, just like AMP. Like there's a person who still needs to be in there because it will return slop. It will return weirdness. It can go drift off course. It's not possible to have a thousand agents doing stuff realistically. Am I correct? Yeah, well, some are further along. I mean, I'm actually using this all throughout Databricks and I'm happy to show you, but the reality is that they're not. And you have to ask the question, why is that? Like if it can solve Navy or Stokes, very difficult math problems, how come enterprises and organizations out there are so far behind? Why is that? Well, there's many reasons, but the main reason is, or maybe one way to look at it, if we could gather all the information that you have inside a large organization with 200,000 employees, record all the meetings, which by the way, that itself, one of the big bank CEOs told me the other day, no way, we're never recording the meetings, like not in a million years. But assume you have that. Because of liability. Liability, I mean, by the way, which I already, I was already kind of shocked because if you can't do that, how can the AI ever help you? Like the AI is simply not in the meeting. If it's not in the meeting, it's useless. It doesn't matter if you have Terry Tao or you have the greatest mathematician in the world. If they're in the cold and they don't know what decisions or what you're doing in your meeting with hundreds of thousands of employees, there's no way it can help you. So if you capture all that context and you could feed it to the AI, they would nail the problems. They could help us right now already. So that's really the context problem. Now you might say, okay, well, let's figure that out and do that. Then we were doing that at Databricks, but that's not enough. Even if you do that, you have a second problem, which is, you could unleash something like OpenClaw and just have it access all your data everywhere. Well, then you get into this problem that you're gonna get hacked. Cyber is a real thing. And all the big organizations that have successful businesses, they're really- terrified right now of getting attacked. This is a big concern. It certainly creates a lot of surface area when you embrace this. I mean, if a CEO or in a small company, you want to connect everything, it's a certain amount of surface area. But for a 200,000 person organization, 10,000, my lord, the surface area has now gone 1,000x. Yes, exactly. So that's the second problem you bump into, which is, okay, we can access all the data. Well, wait, we don't want to maybe access all of it to the agents, because now we have an insider threat and we might get hacked. So what do we do about that? Well, let's say we solve that too. So now we've solved the cyber problem, which by the way, we have actually ways to do that at Databricks. Happy to show you. Then you still have another problem, which is, okay, now the token cost is going up exponentially. So if the token cost is going up exponentially, is your revenue at your company going up exponentially? And I don't know any company who started using AI and as of their use of AI, their revenue started accelerating exponentially, matching their cost curve. So then eventually, first of all, CEOs are like, go get the AI, get more AI, get it in there. We need to move faster. But then at some point, the CFO shows up and says, hey, our OPEX is going up significantly here, and even the COGS, what are we doing about it? And we have an earnings call soon. And then they freak out. So then how do we fix that? So you need to also do this efficiently, which we also have ways to do that at Databricks. Now you've done all of these three, then there's a strategic last question that still remains, which is like, okay, fine, we figured it out. We accessed all the data, we secured it, and we figured out the cost situation. How do we avoid getting locked in? And how do we own our own IP? Because otherwise, there's no business to be made in the future. Data sovereignty is what you're referring to, intelligence sovereignty. And if you use Anthropic, OpenAI, or any of these platforms, there is this risk that it will leak, that it will get incorporated into their next version. And as we've seen, a company called Anthropic seems to be releasing every two weeks, a half dozen products that just now, they're competing against Microsoft. I think Microsoft is one of their giant partners. And they just came out with basically an Excel killer. They're killing Photoshop, and they're just going after everybody wholesale. For free. So by the way, these companies are amazing. They're doing amazing work. And without them, we wouldn't even have this intelligence, probably. So I'm thankful. This is awesome. I'm just pointing out why, when you look around you, all these successful organizations, all the Global 2000, all the Fortune 500, Nasdaq, and so on, how come it's just glorified chatbots and a little bit of coding? This is the reason. So you need to really tackle all four of those. And only then can you start getting something out of it. One of those issues as well, I believe, is the autonomy in an organization to come up with a groundbreaking idea. You may have captured a large portion of your market. You may be getting incremental benefits. So if I tell you, hey, we can put another 500 horsepower into your Ford Taurus, it's like, okay, my Ford Explorer now has 500 extra horsepower. It's going to rip the chassis off. This thing is not capable of going 500 miles an hour. So then it's, well, who decides we're launching three more product lines? Well, at Entropic, somebody is deciding, why don't we just go after every single business in the world? And they started doing dashboards. That's a little close to your business, is it not? A little dashboards over here? Yeah, so dashboards, we don't have a product where we charge for dashboards. Dashboards are usually backed by data. And you typically want that data to be governed. You don't want just numbers and then those numbers are incorrect. This is a big problem in organizations. So that gets back to the second thing I said, the governance security aspect. So yeah, maybe we can get access to all the data and get all the context, but we've got to make it secure. So you can actually connect all of these agents from outside to Databricks, but then we are the governed data repository. And then when you access that data and the governance, we charge consumption rates on that. So actually, that's one of the reasons you see acceleration of our business because all these companies, whenever they have agents and they're using it, then I think we're just in the beginning. As I said, I still think it's mostly Google search and coding, but the agents, when they start using that, they just send us more queries. How does the behavior change when people actually embrace agentic technology and they start working with agents, let's say, every hour, every other hour of the day, like you and I do? In a small organization, org charts are built this way. There's like a tree structure, the CEO at the top, and all decision making goes kind of up and down in these org charts. And you have all these old processes and getting agreement across this org chart is very, very hard inside of an enterprise or inside of any organization that's sizable. It's somewhat easy up until Donber's number, which is 150. You can know everyone. So small startups, it's a different story, but above 150, this becomes a coordination problem. But if you look at how actually any organization actually sells a product or a service to its customers, it's actually not this kind of hierarchical thing. It actually cuts across that org chart. Like here at Databricks, we have customers, they give us feedback, the feedback goes to product management organization, product management hands it to engineering organization, engineering builds products, that goes to marketing that markets it, and then marketing gives it to sales that sells it to customers again. So you kind of want to go across, you want to cut out that latency so that you can be really, really fast. But that requires that you have an AI that actually understands your whole business, your IP, it needs to understand your org chart, it needs to know who's who, who's responsible. What percentage of companies actually understand what you just described? Would you say 10% of organizations understand this, 5%? At scale, I don't know how many, I don't know the answer to that. At scale, I know that Databricks is doing it, I'm doing it. Yeah. I haven't seen anyone else, to be honest, do it at this kind of, you know, I think probably Block and Square with Jack Dorsey, since he's pushing, he's calling it the company world model, he calls it the same thing I kind of described. I think, you know, a different way of viewing it, he's calling it the company world model. So I think that they're probably pretty far ahead. In general, I think digital natives are probably further ahead, digital natives being companies that have only existed 10, 15 years. If you've been around 20, 30, 40, 50 years, which means you're an amazing company, maybe you're a Fortune 500, the best companies in the United States, you have maybe 100,000 employees, they're loyal, they love your products, and you know what, you're the best in the world on that. You have so much software, you have so much regulation, and you have so many processes around security and so on, that it's very hard for you to adopt this. But that is the very problem Databricks wants to solve for them. We want them to adopt the technologies so that they can do what I do at Databricks, basically. Yeah, let's see it. You said you would be willing to show us how you run Databricks with agents and with AI, and I've been looking forward to this all day because I literally am taking the entire while you queue it up my entire life on podcasting and on early stage investing, and I'm looking at each of the components of those things as services, as agents, and defining the goal, working backwards to what are the signs of success that you're heading towards the goal? Not that you've achieved the goal. Achieving the goal is kind of binary, yes or no. You made the sale, you didn't. But what are the precursor signals, and then trying to have each of these bots hand off things back and forth. You have to be a real systems thinker. It's like playing five chess games at once while riding a horse. It's really intellectually, I find it super stimulating. I can tell you do too. You can share your screen. Let's jump in. We have a product called Genie, but the key thing that Genie has, because there's so many chatbots out there, and there's so many assistants, and there's so many co-work products out there and agents in the background. The key thing is that it has an ontology. The ontology is a graph that it constantly is constructing for your company. That graph understands all of the people, who reports to who, what are they working on, what are the emails that are coming in, what meetings have happened, and what's the transcripts of all those meetings and all the decisions that are being made there, what's on Slack, what's being communicated. It has access to all of these things, and then also all of the docs that you're creating, all the Excel sheets, all the PowerPoint presentations. It has access to all of those. That's what we call Genie here. You can see here. I wake up, it has an inbox. In the morning when I come in, it basically has done a bunch of background work for me. It's running 24-7. As you can see, it has access to my calendar. In fact, I could just ask it. I tell Jason on all-in today, here it goes. Let's see what it's going to say. Let's look at some of the stuff that I've done. Actually, the other day, one of the interesting things is I was looking at our HR department came back, and they were saying, hey, we've done a survey on all of Databricks. We had over 10,000 people, employees, that responded to the survey. I looked at the results, and she was going through it. I said, hey, make me a dashboard of the results. Nothing magical here yet. It told me, look, here's how you're doing. You're doing great on some things. Executive leadership, 88%. You're doing okay. Work-life blend, 60%. You're working people pretty hard over there. Maybe everybody says that, right? Yeah. We want to know. We wanted to improve these two. This action one really bothers me because action, by the way, it means that when we ask them for feedback, they give us feedback. Improve this and that. They feel like you're not listening to us. Two out of three feel you are. One out of three feels you're not. You're doing okay. It's not terrible, by the way. This could be like 30%. 60% is not great. Especially not great if you actually take into account that every year it's low. Every year, I promise the company we're going to fix this and every year it doesn't happen. We're going through the results and we're discussing it with these staff. While they're discussing it, they're speculating. My CFO says, hey, I think it's because of work-life blend. Work-life blend is bad and that's causing action to go down. It's causing. Work-life blend is causing low action. I'm like, that doesn't make any sense. But I just entered here immediately as we were discussing and it immediately pulled up. Okay, this is the correlation between these two. And this is how it's looking. But then I was like, okay, wow, maybe he's right. But then it says, no, actually it's not causal. It's not causing it. And here's the exact proof points. We probably have to anonymize these folks. Here's a manager that has work-life blend 44. That's pretty bad. Action is 77%. So, you know, things like this. They're working hard and he's recognizing and taking action on their concerns. Exactly. That's your guy right there. He's pushing people hard and he's listening to them. I like that guy. Exactly. So now I'm learning stuff about the organization. This is amazing. It would have taken me a week to get the data team to do this analysis for me, but that's just me getting information. That's useful. We're cutting this latency up and down the work chart a little bit. But then I'm like, okay, why is it low? And look through all of the comments. And it gives me some reasons. I didn't like the reasons. So then I actually clarified the question and I said, hey, can you slice it by department for me? And then I actually figured it out. It said, look, product management has low action because they don't like decision making. It's too many stakeholders. Engineering, they don't like the tools and systems. There's too much. Sales operations, it's career growth, and so on and so forth. That makes sense because salespeople always think they should get a promotion because they're salespeople and they should get their commissions raised. And product people think you should just listen to them instead of six people trying to design a piece of art. This all starts to track now with the data and the AI. I love it. How did it do this? It has access to this ontology. It's not going and searching live only. It actually found that it already had in its graph these people. Five people had already contributed to this and there's 19 pieces of information here that you can see that it's actually leveraging that it already had. It didn't search for them live. These are in the ontology. We can look at, for instance, this particular one. If you click on it, it has a definition, it's a metric, and there's a graph. And this graph, you can see it here. There's a favorability and it comes from... This is the author. You can click on the author and because it understands the org charts, it understands who this person is. This person actually has 29 snippets. They have lots of different assets that it's learned from them. This constantly is learning the intelligence or ontology of your organization. That's a typical thing. Here's another one that is maybe interesting. I wanted to know... Actually, there's new results here in the last 59 minutes. I haven't actually looked at all of those. But I wanted to understand the org chart and what's going on with the org chart and span of control. And I asked it and already out of the box, it was actually... I was shocked by this. It immediately told me there is an org inside Databricks which is very deep. This person reports to this person, reports to this person, reports to this person. They have three people reporting to them, five people reporting to them, four people reporting to them, five people reporting to them. That's not a flat organization. Then you can look at, okay, what can we do about that? Again, it understands. Since it understands all the people, it can immediately out of the box understand them. Engineering, cost. Cost is something that we look at at all. That's another thing we wanted to see if we could understand. What's great about this, too, is instead of you as a leader saying, hey, listen, if we're going to have an opinion, let's go with mine, you've now created a forum where people can be data first, test theories, and you don't have to be dogmatic about who came up with the theory. You just have to be intellectually curious and open to possibilities. Eventually, if this is where we are today, can you imagine in a year or two, it's going to just be giving you these... Through a culture report, it's going to be like a temperature gauge in your company. It's just like you're going to be looking at the nest in your company and it's like, oh, wow, it looks a little hot today. What's going on? It's like, oh, yeah, we made people come in this weekend. Yeah, maybe we should buy some pizzas or give people a comp day during Thanksgiving. This is my favorite. This one actually came out of Genie. This is our 2,000 engineers, and this is how many pull requests or how much code they've actually shipped into production. You look at the middle here, per week, roughly. But it had this L shape, and you look at... L-shape, you know, the top people are actually committing way more. Yes. You know, so what's going on? Yeah, so what the hell is going on? So we looked into this and it turns out they're running automated factories. The rest are not. So we pushed them. And actually, by the way, interesting thing I asked that, hey, can you like add the cost to this, add the cost to this line? And one of the interesting things we found is that it's not even the case that cost necessarily is higher for those people. So look here at the top, the top folks, some of them are actually not spending as much as some of the other folks. So which, by the way, goes back to there is a way to spend tokens in a smart way. You can use open source. You can route simpler questions to simpler models. And we actually have a product for this. And you can cut your costs down significantly. So this is the kind of stuff, by the way, it's also recording the meetings is really important. So, you know, one of the things I heard that there was a customer meeting and I wanted to understand how that product, how that meeting went. And, you know, and I just asked it, you know, hey, was there a meeting with this customer recently? How did it go? And it literally started by saying the meeting went poorly. And it listed and it's listing exactly what, who said what, what are the features they need. So, you know, these are just some of the things that you can do with AI. And, you know, in the background, when I wake up, it has all these deep dives for me. So instead of waking up, calling people, doing meetings, it's doing the work for me. It's pinging them. It's, you know, sending, you know, whatever material is needed for the company. So it just compresses the time it takes to do things. Well, you know, it's a lot of being in management and being a founder is detective work. I call it like being Columbo. If you remember that TV show, I think it might show our age, but you're kind of like, oh, you know, it's one more thing there. Can you tell me about the meeting, the client meeting? How did that go? And who talked most on the phone? And what percentage of time did they talk? And what did the customer actually think? And then you, as the founder, are getting spun. You're getting spun. And it's not that an employee necessarily wants to spin you. A team member is not looking to spin you necessarily. That can happen. But that's not the majority. Most people are good people. But they have, they're humans, right? They're the people in the app. And here you take the people out of that discussion. You say, here's first principles, transparently what happened. Now we have ground truth. And we can start the discussion without you being the CEO, having to be Mr. Detective. And, you know, it is so, I mean, I don't know about how frustrating it was for you two years ago, to spend two hours being a detective. You get three meetings into this. And it's like, if people had just told you what happened, or if you had that report on culture, the problem would have been solved. You wouldn't have had three weeks of hand-wringing. Yeah? Yeah. I mean, or the customer feedback, right? That I can immediately find out all the customers that, you know, I have some, some of them where I'm not just having it look at features that are requested from all of our customers automatically from all the transcripts of all the customer meetings that we have. And it's just gathering those and they're immediately going to engineering. And then we have factories and engineering that can build features automatically. So it's a game changer. You know, it's just that game of whispers that we played when we were kids, right? It's like when you have people have to meet, they have to tell. So one of our main goals is reduce number of human blockers. So we measure that throughout the organization. And we just explain a blocker in this context, please. Well, something I can learn from. Yeah. I mean, the AI is very fast, right? It's just iterating in the background and it's doing its work and, you know, it's preparing material and so on. But at some point it's like, okay, well now we need to go to legal and make sure that we are allowed to do this thing. Or now we need to go to finance to get approval for this budget. Or now we need to make sure that marketing is okay with this. Or actually just within the same organization, we need to talk to a sibling organization, get a meeting with them and see what they think. And we have to get an agreement. And if we can't reach an agreement, we'll schedule another meeting where we'll look at this again. And then if that meeting doesn't, maybe we escalate it to the managers and then so on. So these are the blockers that slow down organizations. Ah, so it's a blocker finder, which is great if you're the CEO, because here's the next thing. One, you have to play detective. The other one is the blame game. Why isn't this done is what we always ask. You're a leader, whatever your group, another group. Hey, we were supposed to do this by today. We're supposed to hit this target. Who's responsible? And then you get three Spiderman's pointing at each other. If you know the meme here, it's like, well, this actual piece of data has not been resolved and your team has run nothing. I had a similar thing. I came up with a bot. I was going to share it with the whole company. And thank God I didn't. But I came up with a bot just called major decisions. And I just said, go into Slack. Join every room as me. Just join every challenge me, which some people are like, wait a second. How did you even know we had a room? Join every room. Read every notion page, even if I was invited to it or not. Get every email and find for me for the month and every couple of days. Give me a report on the most important decisions who participated in them. And what was the resolution? What's not resolved? Then I said, give me the people who participate the most in these kind of discussions. And then I realized, oh, wow, these are the people who are actually making decisions in the organization. These are the people who are quickest. And my next report is going to be, who's quickest to contribute to those discussions? Now, in a venture firm, that's going to be a discussion like, should we invest or not? Should we take our pro rata or not? Should we sell our shares if we got a secondary offer? On the podcast, it's like, should we book this guest or not? Should we use this clip or that one? And then it picked up employment discussions. And it was like, should we fire this person or not? Or do we do PIPs? I'm like, we don't do PIPs. And I just think PIPs are ridiculous. The performance isn't here. That's like, the person didn't show up. Let's torture them for two quarters. Yeah, you mispracticed and you showed up late for the game. That's table stakes. You can't be on the team if you can't do those things. So now we're going to torture you, try to make you come into work on time or do a workout you don't want to do. So maybe you could speak to what this is going to do for you as a founder and a CEO in terms of figuring out who are your all-stars on the team? Who are the ones who are actually contributing? Because now we're getting to essentially business moneyball, like that movie Moneyball. It's fantastic, Brad Pitt. It's such a good movie. It's such a good book. We're actually getting into management moneyball, aren't we? Yeah, absolutely. By the way, one of my favorite questions is just look at different orgs, because we have certain culture principles, truth-seeking, first principle, and so on. And I say, hey, which of these leaders follow these principles? Look in their whole orgs. Look at all the meetings. And it can derive from those. And by the way, you could even ask, hey, this leader, what is the actual culture they're implementing? And it'll come up with different, it'll tell you, no, actually, the culture there is this, not the company culture, which is essential. They're deviating from the core principles. That drift is cancerous for you as a founder, or it could be something you need to change and could be an early warning sign. We need to be consistent, whatever it is, right? Maybe they're right, and the rest of the organization, including me, are wrong. But then we need to at least, it tells me that there's this divergence. So those kind of things were nearly impossible to do. Many of this other stuff you could have done, but a question like that, get the culture of this subgroup in a 12,000-person organization. Figure out how the Japan organization at Databricks, I don't even speak Japanese, and we have hundreds of people over there working. What's the culture like? How do they make decisions? How is it different from the EMEA or the LATAM region that we have? So those are kind of game changers. For us, it's really, I share all this information with the employees. They have access to all of this themselves. And then I tell them, this is what we want. That L-curve, we wanted to shift it to the right. So everybody, let's change that. Let's move towards this, the North Star that we have together. And that helps us just be more competitive. And then once we get more competitive, we can build more products, and we take market share, and we can accelerate our growth further. I'd like to not be 70%, 80% growth every year. I'd like to be 100%, way over 100%. So that's how I see it. So in this era right now, this is a competitive advantage. Whoever can do this best, at some point, maybe everyone is using it. It's fully diffused, and everybody's doing this. But right now, this is big alpha. If you can do this really, really well, better than any other organization. Speaking of big alpha, a lot of people have been very patiently been on your cap table. And we have a big debate between founders and capital right now. Stay private longer. What's the point of going public if we have secondary markets that are quite efficient? Stripe has been private closer to 20 years, I think, than 10. And they seem to have given the indication they're going to stay private longer. SpaceX took a little while. Uber took a little while. I felt that one. But luckily, Masayoshi-san was splashy-cashy. When are you going public? And how do you make that decision? I know you got a lot of pressure on you to do it. But you also have a lot of pressure relief valves in the vibrant secondary market. Yeah. Look, my goal is to make Databricks as successful as possible in the next decade or two. That's how I'm thinking about it. What's the right strategy to get there? I mentioned this alpha of what we're doing here, the products we're building. By the way, we're getting into new markets. We got into the security market. We got into the marketing market. I'm focused on those. Then the question is, the path to get there is the best way and the fastest way for us to be public or to be private. And I actually think that... Take me through that. What's on each side of the ledger for you? Yeah, I actually think that you get access to capital. You get much, much better marketing. Everybody knows about you. Every quarter, you have this big marketing event. You can tell your story again and again and again. Those are huge advantages. We have to organize our own tenders every year. Every year, we do... Finance has to go through this big process. I think we raised $20, $30 billion. And then we have to arrange that. It's a heavy lift. There is a marketplace that just does that. It's also probably pretty emotional and distracting, I would think, right? People have to decide. Then you might lose people that, hey, they take $10 million off the table. Maybe I don't want to come to practice anymore. I think the liquidity is a good thing. Because people know that they're going to get it every year. And it comes and it's predictable. And that's the one time they have. And actually, in the past, it's turned out... Since we started doing these a few years ago, it turns out that the money that we set aside for tenders, they never use up all of it. So most employees are bullish. Yeah, so most employees are like, no, this is... That's good for you. You get signal from that, right? Who's selling, who's not. It's a little bit of signal. It could be personal reasons. But acquiring companies is a great reason to have equity. Yeah. I mean, we haven't had any problem doing billion-dollar acquisitions because they know... Because of the liquidity that we will provide. And then I think most people do the calculation. It's like, okay, if it's... The business is $7 billion plus and it's growing 70-80%. They do the math. It's like, okay, I could... Most people say, I want liquidity. But then when you tell them, like, okay, well, how much do you want to sell? We're growing 70-80%. Yeah, it's a different story. Can you do compounded growth of 1.7 to the power of 3 or 4? And then they start scratching their heads like, okay, maybe I'll sell like 5%. Yeah, sitting on your hands is a very important skill to learn as an investor and an employee with this kind of stock. I mean, listen, you do have to protect downside when you get in that space. Who do you see as your competition right now? Everybody says something like Snowflake. But I'm watching a market where, as I said earlier, Anthropic is launching feature after feature. Cloudflare is looking at features next to them. Repl.it is looking at features next to them. Everybody seems to be looking in their peripheral vision. And because you can build software fast, and because you have a lot of developers, if those developers keep going up that ramp that you showed, you only had 10% of people at that peak, which means as that 90% climb up there, your developer resources are going to go through the roof. You have a decision to make. Do we just have less developers at the low end of the tail and be more profitable? Or do we invest all that developer time as they move up the ramp? How do you think about both of those issues? What to do with massive resources that this efficiency is creating? And then who is the competitor? And do you need to just keep making peripheral product moves? Yeah, we will make peripheral product moves. But maybe I should just start by saying, okay, so those were the upsides of going public. The downsides are, you know, is the reason why, you know, to answer your specific question, like, you know, why do we compete? Who do we compete with? Why do we build this product? I don't want the market to force me that, okay, now it's down. And now it's, you know, sentiment is terrible this week. And now your stock is down. And when the stock is down, the employees literally are getting a pay cut. And I say, well, you know, you promised me I was going to make a million dollars. Actually, you said this is going to be 2 million in a couple of years. But I'm looking at it right now. It's underwater. And it's actually worth 200k. So you lied to me. I'm leaving. Okay. And then, you know, three months later, it's like, oh, no, no, no, actually, the revenue is accelerating. We were totally wrong. It's up to the right now. It's like, oh, okay, wow, it's great. So there's like back and forth. A little bit of a roller coaster. That's what I want to avoid so that we can focus on that long term, you know, building the company towards the vision that we have in the long run without being distracted. We will go public. We are going to be public. But right now, I think during this transition period of AI, there's just too much up and down. And I think it's distracting to companies. It's distracting to CEOs. It's demoralizing to CEOs. You know, they call me, you know, they're like depressed because, you know, stock is down. They don't even understand why. And then the stock is up. So that's what we're trying to avoid. I think it's an issue people are starting to have with their sleep scores. You know, you get a whoop and I love it, but I got my wife a whoop. And then we're like comparing sleep scores. And now it's kind of like looking at your Uber stock every day. You get a little bit of volume in your relationship. It could be challenging. It's interesting. Hey, we didn't circle around to what Ben Horowitz said. He said that your formulation of super intelligence is some combination of the model, the power, and the time it takes to train and be accurate. Can you walk us through it? Do you have it off the top of your head there? Ready to go? I have to do it. I mean, it's pretty simple. So I think the main problem is the context problem. We're solving that with Genie and the ontology. The labs are focused on super intelligence. That's what Botstrom talked about. Botstrom in his book also said, how do we get there? He actually, in 2014, I believe, defined RSI, recursive self-improvement, which means that the AI starts improving itself. And then it gets better and better and better and better and better. And then we get this takeoff, maybe a fast takeoff. And at that point, we reach the singularity and we're no longer in control. And at that point, let's hope that the AIs are well-aligned, because if they're not, we're all going to be made into pets. And this is where the 10% risk. Yeah, paperclip maximizer. and the 10% risk to humanity, and all of that comes from there. But I think a lot of this is actually coming from most of the folks that are building this AI. They've seen that the AI has become really good at coding. And almost in every company, as I said earlier, the coding is being done by coding agents. So then they're seeing, and I think this is actually causing a big existential crisis in Silicon Valley. And it's actually for most of us who started, you know, who grew up coding our whole lives, you know, it's, it's, it's a big deal. Like, you know, it's like, like I spent, you know, 10, 12 hours, seven days a week, you know, from third grade until, you know, my thirties, just coding all the time. Right. And I was really good at it. And I knew all these languages and so on. And then suddenly it's like, the AI is doing that. Well, if it's doing it- And the AI is how much better than you. That's the other part. It's like- Yeah. So now it's writing itself. And the next version, it wrote itself. Wait a minute. Isn't that the recursive self-improvement? But wait a minute, then this is going to speed up and then we're going to get into this loop. The books, the book called it super intelligence and the paperclip maximizer. So it might go off and all these bad things happen. Actually interesting. Botstrom has kind of changed his view. Now, if you have to follow him now, he's actually not anymore. He's saying that, you know, we should do this. There are risks. Of course there are risks with cyber, but you know, I actually think, you know, you need to actually think this through further just because 98% of the code is being written by AI. We don't have RSI. If it automates the last 2%, who cares? You know, it doesn't matter if it's 98, 98% or a hundred percent. Why does it matter? Actually doesn't matter. So we really need four conditions to be true. The four conditions is that we need the next model that's trained to, you know, be trained in much shorter amount of time. Okay. And still the big pre-training runs that the labs do, they don't do actually that many of them per year. Okay. And it's still following the what's called the scaling laws, which means you need exponentially more hardware to get that improvement. So exponential more than 10X more compute to get a little linear improvement. Okay. So they're scrambling to get all the GPUs and put together the biggest data center that they can possibly put together with the networking and do all the engineering. And then they're having humans do all of this because they really don't want to screw up the next run. If the next run gets screwed up, then, you know, the whole thing falls apart. But you know, we would like that next training run to be faster. That's condition number one. Okay. And actually it can't just be a little bit faster. It's like this, you know, it can't be like, you know, you're halving the distance every time you'll never get there. So in some sense, it has to be super linear. Secondly, we also want it to use less resources, right? Because, you know, you could say, okay, it's getting faster and faster, but that's because we're 10Xing the hardware all the time. Yes. Well, you can't do that trick because we run out of hardware and we run out of atoms. So that's like the second requirement. Third requirement is that the accuracy is also improving at least linearly or, you know, we're getting better accuracy across the board in a generalized manner. It can't just be, it's getting just better at, you know, this one dimension that we did reinforcement learning on or just math. It needs to be across the board on all of its tasks. Anyway, even if you do all of those three, it's not enough. Let's say you do that five, six, seven times. That's awesome. You get really awesome models. That's not that kind of super intelligence. The fourth condition is that you can actually put this in a loop and all the previous three conditions need to be continuously happening so that we end up in a world where the next model takes, you know, three months, then one month, then, you know, two weeks, one week. And it's getting smarter and smarter and smarter and it's, you know, costing us a hundred bucks or maybe it costs us a hundred million, then 50 million, 25 million, 10 million, five, two, one. And then it goes down and down. That's what we, that's the kind of scenario we have. If you actually look at it, that's the flywheel, that flywheel doesn't exist right now. The models are taking longer to train, right? And there's more data cleaning and there's more manual whack-a-mole-ing happening where, you know, you have vendors like Mercor that has to actually go get the data from very skilled labor. And then you have to do reinforcement learning in these gyms and you have to kind of whack-a-mole in each domain. So it's very domain specific. And then of course the pre-training requires more resources. And you know, so that doesn't look like we're getting into this loop. By the way, even if you satisfy all the four conditions I'm saying, that doesn't guaranteed mean that you'll have, you know, a conscious being that's just, you know, taking over everything and just, you know. It's the precondition for that happening and there's no guarantee that it actually happens. It's a precondition. But even if you had that, which we don't have, you would have to, to threaten me right now, you would have to have a killer robot come into this room right now and wrestle me down, okay? Or something, right? And those don't exist yet. So you know. Right now, you can have a bunch of hackers take a really capable model and you can find out that the refrigerators in grocery stores in France have the password admin, admin, and that you can remotely script kitty into them and turn it into defrost mode and make a bunch of butter go bad and milk, which is a tragedy for the French. I understand, but it is not super intelligence. I can assure you. Yeah. It means, I mean, did you see that hack and how people were losing their minds over it? I'm like, guys, you know how, when you buy a new router now, it has the serial number and then a random password admin as a man. Yeah. If they had done that on the refrigerators, they would have been able, they wouldn't have been able to hack one of them unless they got into the place, took screenshots of 20 different refrigerators, physically compromised, you know, some supermarket in the eighth and draws mint, which would have lost, you know, I don't know, 10 pounds of butter wouldn't have been a big deal. So look, cyber, I do think is a real thing. Yes. And I think it's a real risk. We actually have a whole product in the cyberspace called Lake Watch built on all this data that has automated agents that actually detect these kinds of intrusions that are happening and they monitor your agents that you have. This is a real problem. And I do think bad things will happen here, but then we will adjust. But bad things happen when internet came out as well. Shouldn't it? Shouldn't we be able to solve for this? Because you tell me if I'm right or wrong here. One theory I heard, which resonated with me for a certain type of hacking, not for the, you know, script kitty hacking, but real hacking is you have a lot of compute, you need a lot of compute to execute certain hacks, like the hugging face one, you know, thousand agents, whatever. The bad guys don't have that much compute. The good guys have a massive amount of more compute. And so, if you just did your basic job as a white hat and, you know, defended properly and looked for these exploits, let's say you have a thousand times the resources, you should be able to get to these problems long before the hackers. Does that make good sense to you? I understand the argument. Yeah. It's a good argument, right? Yeah. But the issue is that you have to weigh that against the following asymmetric scenario that we have, which is if I'm an attacker, you know, I can launch thousands of thousands of thousands of agents and I, all of them can fail except for one. And if one of them gets through, I'm completely successful. The asymmetry is that if I'm a defender, you know, I was able to like, you know, you know, protect, you know, my, my boundaries all the time, except one got through. This is a suicide bomber, not to be too graphic, but you only need to get one 9-11 to make your point. Yeah. You can try a thousand times and not get through. So they need to be a hundred percent safe all the time. They need to just get one thing through. It's like very asymmetric, that risk. But however, the way I would look at it, the reason, you know, I think that we're actually going to overcome this and it's going to be totally fine is that these are actually latent bugs that exist in the source code. By the way, we're not creating more of them now because almost all of us are now scanning it. We all have products. I mean, we actually sell a product where we can scan the vulnerabilities of new code. So new code that's being produced is not going to have these vulnerabilities. By the way, that might sound silly, but think about it this way. In the next 12 months, we're going to write more code than ever in the history of mankind. Right? Actually, less than the next 12 months. So all that code is going to be secure. So then, and by the way... Because right now the AI is sophisticated enough to not make human errors and to look for it. And it's more dogged. Yeah. You just can't scan those things. So then what remains is all the legacy code, which by the way, we can rewrite all of it, which is what we have to go through. And people are doing that, right? Yeah. We're doing that. There are other ways. 80, 90, yeah. So we can protect, you know, do shadow patching before even actually without touching the existing legacy code. But so, you know, what's happening is that you can think of it as like, you know, it's like a fruit garden and there are like these bugs that, you know, attackers are leveraging. They're picking the low-hanging fruits. And before humans could pick a certain low-hanging fruit. Now agents can reach higher and pick higher, you know, hanging fruit. But we're going to clean those up and then they can maybe reach a little bit higher. But there's only a finite number of vulnerabilities in the code. Once we've secured that code base, there is no more. So it's not like there's an infinite thing and this is going to go on forever. No, it then stops. Then we're at the steady state. And then, you know, vulnerabilities might actually be fewer than what we had in the past. I think that eventually then, you know, back to AMP, where you went at Berkeley, it's the people in the loop that are the vulnerability. And it's just going to be somebody getting compromised. As we saw the last week or so, the humans do have vulnerabilities. I'll leave it at that. Hey, I want to end on this one thing. You spent a lot of time in Berkeley, hippy-dippy, EA community, accelerist, decelerist. What's the nature of this group of the EA faction and how they look at the world and how confounding they are to the rest of American society? Who are these people? What do they believe? Are they a little drunk on their own success? Or do they actually have really important insights and we need to really focus on what they're saying and take them at their word? It's a big controversy. Dario, you know, during the roadshow, is saying, cancer and Alzheimer's, I believe, will be gone in under 10 years. Now, that's very beautiful to say, except if your mom or dad are dying from cancer and you think, oh, I got a window here that I could save them, or my grandmother's got Alzheimer's. Now you're talking about giving people false hope, and you maybe shouldn't make claims like that. But I don't doubt Dario believes it. I actually think he does. Unpack these people because you've been around them for two decades, three decades. Well, I think that most people on both sides, actually, on all sides, they're the heroes in their own book, right? We all wake up thinking, I'm the good guy and I'm doing the right thing. I think it comes from a good place. I think they are seriously nervous about this kind of superintelligence taking over. If you read Botström's books, actually, if you read those books and you sort of internalize what he wrote before any of this, then you actually get kind of freaked out, right? And I was certainly freaked out when I read it. So I think that they're starting with those assumptions and then they're looking at, you know, okay, well, then if it's getting smarter this fast and look at the cyberattacks that are happening, dot, dot, dot, we're going to get this kind of superintelligence that's described in the book. But there's a few dot, dot, dots there that are not clear. But then they would say, well, look, you know, shouldn't we be cautious, right? So I think we need to take, you know, we should look at safety. Cyber I think is a big deal that we should look at. But the reality is that I think we know how to handle this. We will be able to manage through this. I think the biggest risk right now is cyber and I think it's manageable. This RSI, I don't see any evidence of it. If there's data that, you know, others have that I don't have, yeah, I don't know what I don't know. But based on what I'm talking to, you know, here in San Francisco, where all the labs are and all the people I meet, I don't see those four criterias that I mentioned even being fulfilled, you know, so I don't see any risk to be like worried about that, you know, that happening. And then the second thing I said, even if we would get there, I don't see, you know, even the means in a society like it's just digital, like we can just shut down the computers right now. You know, I do think cyber is real. Like if a hospital went down and set up a refrigerator, right? That is concerning. Kids using it and developing parasocial relationships with character AI or it giving you bad information if you're suicidal or something like there are concerns to have about how the technology gets deployed. And we just went through this with, you mentioned Dunbar's number, but we went through this with, you know, social and the profound impact that had on society. We're going through it now with truth and news and manipulation of news via algorithms. So there are things to be concerned about being turned into paperclips. Maybe not. But I think that, you know, the healthcare stuff is absolutely real. Like, you know, at Databricks, we actually, we were involved with Regeneron where they found the actual genome response of a chronic liver disease using Databricks, their researchers there and actually came up with drugs for that. Best case scenario in under a decade, if you were to take the claim we had Dario make, any chance that like we cure cancer in the next 10 years, that's a pretty bold statement. It's very hard for me to say. I don't know exactly what's needed. I mean, I think progress will be faster, but for a lot of these things, it also has to go through, you know, human trials, all the human trials, like, you know, we can't just test stuff on humans, willy-nilly, right? And just because you tested it on animals, it's not enough either, right? So I don't know, maybe in 10 years, maybe not in 10 years, maybe it takes 30 years, maybe it takes 50 years. I don't know. Maybe it takes six months. Maybe it's already solved more or less, but it is helping already. So use case I gave you with chronic liver disease, that's super important. By the way, that was the previous generation of AI that we used at Databricks. We trained a new one now with Merck, and it's called TEDi, transformer-enabled drug discovery. Transformer-enabled drug discovery is a model, transformer model, but instead of, you know, the next token being English, it's the gene regulatory network, GRN. So it actually can say, okay, this genome is actually causing this disease. This genome is just reacting to it, so don't target it for a drug. So this will accelerate drug discovery. It's a game changer, you know? Drug discovery aside, I'll give you another example, like Crisis Text Line, it uses Databricks and uses large language models and these agents, and they actually detect if kids want to do self-harm and it helps prevent that, right? You know, Virtue Foundation uses Databricks. You know, Zipline, this was a use case that was reported before, used Databricks to deliver food. They had these drones, right? And blood. You know, these were big companies that would deliver, you know, everything about those drones and so on, like their paths, the, you know, all of that was running. So we see these use cases all the time with AI, and it is going to make the world a better place. There are risks. We will deal with those as well. People are nervous because, you know, things are changing, and I think the AI companies, there's a lot of researchers who maybe, you know, they understand the research very well, but they haven't looked at, you know, how does the economy look? What's going to happen? You know, how are these things going to evolve? And they've watched a lot of sci-fi, let's be honest. Like they are being informed by, you know, a certain narrative. And the idea that there's a 10% chance that 7 billion people die because of AI seems so farcical and out there that when you pick a number, it makes you seem credible to an average Joe who's like, well, these are smart people who make a lot of money. And if they think it, maybe they're right. If they're saying it themselves, right? That's how people think. But for me, that risk is, you know, close to zero. I think the cyber risk is real and really bad things can happen with that. That's where we're focused on it. You know, and then, you know, I think actually to solve this context gap that I mentioned in enterprises, the thing we're focused on to actually get value everywhere, I actually think it's going to take 10 years. You know, I think this is something that's going to take 10, 15 years. The labs think this will happen like in the next six months, 12 months, in, you know, two years. But I actually think GDP will move very slowly and it's going to take decades for us to actually get through it. Why? Like you said, I mean, just go back to the anecdote at the beginning, the, you know, the CEO of the bank that said, we can't even record the meetings. If you can't record the meetings, the AI doesn't even know what's happening in the meeting. How could it possibly do the kind of things that we discussed when I showed you Jeannie and the ontology? It's going to be a paced rollout to be sure. And there are some of us who are running ahead around the corners, doing really cool stuff, which is exactly what we both experienced with the internet. When the internet first came out, the people who were using it to its fullest extent were like, okay, this is going to change everything. And then 99% of people were on dial up and had never seen a high speed connection. So they, their brains couldn't conceive of YouTube or, you know, unlimited free photography story. It doesn't make any sense. There was a kid called Robert Morris, who took down 10% of the internet with a worm. It's called the Morris worm. You know, he almost got a jail sentence for it. And then he went on and he became a famous MIT professor in computer science. And he's like a very famous guy. But you know, that took down a whole 10% of the internet back in the day. Which is completely possible. Like at some point today, somebody feels like they may have cracked signal to a certain extent. Okay, sure. Let's see what happens. All right, everybody. Another great All In interview. Oli, thank you so much for your time. And we'll see you next time on the All In interview. Thank you so much. Great job, Oli. You were awesome.