WEBVTT - Why Paul Kedrosky Says AI Is Like Every Bubble All Rolled Into One

0:00:02.720 --> 0:00:16.439
<v Speaker 1>Bloomberg Audio Studios, Podcasts, Radio News.

0:00:18.520 --> 0:00:22.400
<v Speaker 2>Hello and welcome to another episode of the Odd Lots podcast.

0:00:22.480 --> 0:00:24.800
<v Speaker 3>I'm Joe Wisenthal and I'm Tracy Alloway.

0:00:25.120 --> 0:00:28.320
<v Speaker 2>Tracy covering the AI boom is actually reminding me a

0:00:28.360 --> 0:00:31.240
<v Speaker 2>little bit of the tariff boom in April, simply because

0:00:31.280 --> 0:00:33.880
<v Speaker 2>every day they are new headlines, like they're just today

0:00:34.040 --> 0:00:38.519
<v Speaker 2>we're recording this November twelfth, Anthropic commits fifty billion dollars

0:00:38.520 --> 0:00:41.160
<v Speaker 2>to build AI data centers in the US. So the

0:00:41.240 --> 0:00:44.479
<v Speaker 2>advanced model companies are vertically integrating more to build their

0:00:44.479 --> 0:00:46.879
<v Speaker 2>own data centers. Every day some new development.

0:00:47.080 --> 0:00:49.760
<v Speaker 3>Yeah, it's becoming pretty hard to keep up. So I

0:00:49.760 --> 0:00:52.400
<v Speaker 3>think we're probably just going to talk in terms of

0:00:52.440 --> 0:00:54.520
<v Speaker 3>billions and trillions. We're just going to say lots and

0:00:54.560 --> 0:00:57.280
<v Speaker 3>lots of money is going into the space. But the

0:00:57.320 --> 0:00:59.840
<v Speaker 3>way I've been thinking about it is, Okay, at this

0:01:00.240 --> 0:01:04.640
<v Speaker 3>everyone agrees that the AI buildout is super expensive, and

0:01:04.760 --> 0:01:08.240
<v Speaker 3>all these companies are spending massive amounts of capex to

0:01:08.360 --> 0:01:12.200
<v Speaker 3>do this, and I'm starting to think that AI capex

0:01:12.319 --> 0:01:16.399
<v Speaker 3>is kind of like the Schrodinger's Cat of markets in

0:01:16.440 --> 0:01:20.400
<v Speaker 3>the sense that it could either be a massive strength

0:01:20.600 --> 0:01:23.920
<v Speaker 3>for these companies because the capex is so expensive and

0:01:23.959 --> 0:01:26.200
<v Speaker 3>it takes so much money to build out, and so

0:01:26.319 --> 0:01:28.320
<v Speaker 3>anyone who manages to do it kind of builds a

0:01:28.360 --> 0:01:32.400
<v Speaker 3>moat around their business. Or it could be a massive weakness,

0:01:32.480 --> 0:01:34.720
<v Speaker 3>right if you're spending all this money and then that

0:01:34.760 --> 0:01:37.640
<v Speaker 3>doesn't end up generating the revenues that you actually need

0:01:37.680 --> 0:01:41.640
<v Speaker 3>to justify it. And going back to the Schrodinger's analogy,

0:01:42.560 --> 0:01:45.000
<v Speaker 3>it seems like we just don't know what's going to

0:01:45.080 --> 0:01:47.720
<v Speaker 3>come out of the box, right, Like it's simultaneously a

0:01:47.760 --> 0:01:51.240
<v Speaker 3>strength and a weakness, and until we build out AGI

0:01:51.400 --> 0:01:53.000
<v Speaker 3>or whatever, like, we're just not going to know.

0:01:53.720 --> 0:01:56.080
<v Speaker 2>I told her, right, there's so much at stake here,

0:01:56.280 --> 0:01:59.520
<v Speaker 2>and obviously we know the numbers are absolutely enormous. They're staggering,

0:01:59.600 --> 0:02:02.720
<v Speaker 2>and we could talk about them too. The financing structures

0:02:02.760 --> 0:02:04.240
<v Speaker 2>are also very interesting.

0:02:04.520 --> 0:02:04.680
<v Speaker 4>You know.

0:02:04.760 --> 0:02:09.320
<v Speaker 2>It's one thing if you just have Meta or Alphabet

0:02:09.440 --> 0:02:11.440
<v Speaker 2>and they make a ton of money already and they're

0:02:11.480 --> 0:02:14.160
<v Speaker 2>spending money on data centers whatever. That's one thing. It's

0:02:14.200 --> 0:02:18.320
<v Speaker 2>another thing when you start seeing these SPVs where the

0:02:18.440 --> 0:02:20.560
<v Speaker 2>hyperscaler puts in this amount of money and then the

0:02:20.600 --> 0:02:22.800
<v Speaker 2>private credit puts in this equity and then they borrow

0:02:22.880 --> 0:02:25.840
<v Speaker 2>a bunch and then there's all these questions about the payback.

0:02:25.880 --> 0:02:28.440
<v Speaker 2>And we think of tech as from years and years

0:02:28.480 --> 0:02:31.280
<v Speaker 2>as basically being this equity story, and when it becomes

0:02:31.320 --> 0:02:33.960
<v Speaker 2>a credit story. Yeah, and when you know people are

0:02:33.960 --> 0:02:37.440
<v Speaker 2>talking about quoting Oracle CDs, I always forget these companies

0:02:37.480 --> 0:02:40.520
<v Speaker 2>even have CDs because I'm so unused to thinking of

0:02:40.520 --> 0:02:43.760
<v Speaker 2>big tech companies as credits. So when I see people

0:02:43.800 --> 0:02:47.440
<v Speaker 2>starting to tweet Oracle CDs charts or core Weave CDs charts,

0:02:47.440 --> 0:02:50.040
<v Speaker 2>It's like, Okay, we are in a different level of

0:02:50.120 --> 0:02:51.560
<v Speaker 2>capital intensity.

0:02:51.160 --> 0:02:53.840
<v Speaker 3>Right, and some of those swaps have been going up lately.

0:02:54.160 --> 0:02:56.960
<v Speaker 3>I'm going to say one more thing, thinking back to

0:02:57.000 --> 0:02:59.880
<v Speaker 3>the two thousand and eight financial crisis. I remember the

0:03:00.040 --> 0:03:03.320
<v Speaker 3>economist at Raymond James I it is Jeff's out who

0:03:03.400 --> 0:03:06.440
<v Speaker 3>went on to become a very big name. Yeah, we

0:03:06.480 --> 0:03:08.600
<v Speaker 3>should have him on the podcast. But he made the

0:03:08.639 --> 0:03:13.200
<v Speaker 3>point that historically when you had real estate crashes property crashes,

0:03:13.600 --> 0:03:16.960
<v Speaker 3>it was usually because of a problem in the economy.

0:03:17.160 --> 0:03:19.080
<v Speaker 3>But then what happened in the run up to two

0:03:19.120 --> 0:03:21.720
<v Speaker 3>thousand and seven two thousand and eight is the housing

0:03:21.760 --> 0:03:25.960
<v Speaker 3>market crash became the proximate cause of the troubles in

0:03:26.000 --> 0:03:28.520
<v Speaker 3>the economy. And if you think about how much money

0:03:28.600 --> 0:03:33.000
<v Speaker 3>is being spent on AI right now again billions, trillions

0:03:33.040 --> 0:03:37.800
<v Speaker 3>possibly of dollars, it's very easy to see how AI

0:03:37.880 --> 0:03:40.760
<v Speaker 3>could borph into a problem for the wider real economy.

0:03:40.800 --> 0:03:43.280
<v Speaker 2>Totally just on this note, and then we'll get into

0:03:43.360 --> 0:03:46.160
<v Speaker 2>our conversation. The Center for Public Enterprises out with a

0:03:46.200 --> 0:03:49.600
<v Speaker 2>great report today called Bubble or Nothing by Ed vat Aarun,

0:03:50.000 --> 0:03:52.440
<v Speaker 2>pointing out one of the things that makes data centers

0:03:52.480 --> 0:03:55.480
<v Speaker 2>interesting is how they sit at this intersection of essentially

0:03:55.880 --> 0:04:00.119
<v Speaker 2>industrial spending and real estate. It's an interesting ascid class

0:04:00.360 --> 0:04:02.280
<v Speaker 2>for its own right. So much to talk about. We

0:04:02.320 --> 0:04:04.600
<v Speaker 2>could never do a justice in one episode, but that

0:04:04.680 --> 0:04:06.640
<v Speaker 2>means we got to do more. Anyway. I'm very excited

0:04:06.640 --> 0:04:08.680
<v Speaker 2>for today's episode. We really do have the perfect guest.

0:04:08.920 --> 0:04:11.480
<v Speaker 2>Someone who's been writing about this for a long time,

0:04:11.640 --> 0:04:14.000
<v Speaker 2>someone who's just been writing about the Internet and all

0:04:14.040 --> 0:04:16.600
<v Speaker 2>things for longer than any of us, someone who's been

0:04:16.640 --> 0:04:20.160
<v Speaker 2>blogging and investing for far longer than either of us

0:04:20.240 --> 0:04:22.560
<v Speaker 2>or anything like that. Way more knowledgeable about how these

0:04:22.600 --> 0:04:25.840
<v Speaker 2>businesses worked, and most very focused on the data center

0:04:25.880 --> 0:04:28.200
<v Speaker 2>buildout we're going to be speaking with Paul Kadrowski. He

0:04:28.279 --> 0:04:31.240
<v Speaker 2>is a fellow at the MIT Institute for the Digital Economy,

0:04:31.480 --> 0:04:38.159
<v Speaker 2>also a partner at sk Ventures, and longtime internet blogger, writer, newsletter, yapper, etc.

0:04:39.000 --> 0:04:42.360
<v Speaker 2>Someone we've never never had on the podcast before. So Paul,

0:04:42.440 --> 0:04:44.320
<v Speaker 2>thank you so much for joining us.

0:04:44.440 --> 0:04:46.880
<v Speaker 5>Hey, guys, thanks good to be here. Other than the

0:04:46.920 --> 0:04:47.599
<v Speaker 5>blogging part, but.

0:04:47.800 --> 0:04:50.839
<v Speaker 2>No, it's all. It's all. You're a true pioneer in

0:04:50.920 --> 0:04:53.920
<v Speaker 2>that and it's impressive that you still write with the

0:04:53.960 --> 0:04:57.320
<v Speaker 2>output that you do. At some point in the last year,

0:04:58.000 --> 0:05:00.240
<v Speaker 2>I feel like you really got laser focused, maybe in

0:05:00.240 --> 0:05:02.880
<v Speaker 2>the last two years, really got laser focused on the

0:05:02.960 --> 0:05:05.560
<v Speaker 2>data center's story is this is where the action is.

0:05:05.880 --> 0:05:07.960
<v Speaker 6>Yeah, I did, and in part just because I caught

0:05:08.000 --> 0:05:09.719
<v Speaker 6>myself by surprise with it.

0:05:09.720 --> 0:05:10.200
<v Speaker 5>It was weird.

0:05:10.240 --> 0:05:12.160
<v Speaker 6>I was looking at first half GDP day it actually

0:05:12.200 --> 0:05:15.719
<v Speaker 6>first quarter GDP data earlier in the year, and you know,

0:05:15.760 --> 0:05:17.760
<v Speaker 6>this has become a commonplace that people know this, but

0:05:17.800 --> 0:05:20.480
<v Speaker 6>I hadn't realized what a large fraction of GDP growth

0:05:20.640 --> 0:05:22.720
<v Speaker 6>in the first quarter data centers were was on the

0:05:22.800 --> 0:05:25.680
<v Speaker 6>order of fifty percent, much larger if you included all

0:05:25.680 --> 0:05:27.760
<v Speaker 6>sort of externalities all the other things that data center

0:05:27.800 --> 0:05:31.240
<v Speaker 6>spending in turn kind of accelerates. And then obviously the

0:05:31.240 --> 0:05:33.080
<v Speaker 6>same thing was true in the second quarter, and it

0:05:33.120 --> 0:05:35.360
<v Speaker 6>was I got back to thinking about my dog, and

0:05:35.400 --> 0:05:36.960
<v Speaker 6>I was my analogy is that.

0:05:36.800 --> 0:05:38.680
<v Speaker 3>As one does, as one does.

0:05:38.960 --> 0:05:41.359
<v Speaker 6>I got to get like my dog barks when the

0:05:41.400 --> 0:05:44.200
<v Speaker 6>mailman comes to the house and keeps barking, and then

0:05:44.240 --> 0:05:47.200
<v Speaker 6>the mailman goes away. And I'm convinced he thinks he

0:05:47.279 --> 0:05:49.600
<v Speaker 6>makes the mailman go away, right, he has this really

0:05:49.640 --> 0:05:52.800
<v Speaker 6>screw causality, and it's like, dude, if you don't bark,

0:05:52.839 --> 0:05:54.720
<v Speaker 6>it goes away. Anyway, this is part of the job.

0:05:54.760 --> 0:05:58.280
<v Speaker 6>They just go away. And I think about macro policy

0:05:58.320 --> 0:06:00.160
<v Speaker 6>in the same way that if you don't understand and

0:06:00.279 --> 0:06:02.960
<v Speaker 6>the drivers of GDP growth, you're likely to think to

0:06:03.000 --> 0:06:05.200
<v Speaker 6>whatever it is you would most like to be causing

0:06:05.240 --> 0:06:07.200
<v Speaker 6>GDP growth is doing that. So in the case of

0:06:07.200 --> 0:06:09.520
<v Speaker 6>the US in the first half of the year, you know,

0:06:09.680 --> 0:06:11.920
<v Speaker 6>was this puzzle was, well, maybe it's terroifts, maybe tariffs

0:06:11.960 --> 0:06:14.120
<v Speaker 6>are actually contributing to it, maybe consumers are much.

0:06:14.040 --> 0:06:15.400
<v Speaker 5>More resilient than we expected.

0:06:15.880 --> 0:06:18.080
<v Speaker 6>And as it turns out, a huge factor, probably the

0:06:18.160 --> 0:06:21.920
<v Speaker 6>largest factor, was this sort of unintentional private sector stimulus

0:06:21.960 --> 0:06:26.000
<v Speaker 6>program otherwise known as data centers, and for me that

0:06:26.080 --> 0:06:28.840
<v Speaker 6>I'll start it. So that started this puzzle of understanding

0:06:29.400 --> 0:06:33.080
<v Speaker 6>this sort of disconmisserate size, the consequences of that size,

0:06:33.440 --> 0:06:36.880
<v Speaker 6>and the acceleration's consequences in terms of where where the

0:06:36.920 --> 0:06:37.960
<v Speaker 6>money is coming from, and all.

0:06:37.920 --> 0:06:38.719
<v Speaker 5>Sorts of other things.

0:06:38.760 --> 0:06:41.760
<v Speaker 6>But just to reframe in terms of something you guys

0:06:41.800 --> 0:06:44.320
<v Speaker 6>were already talking about, and this I think is super important,

0:06:44.320 --> 0:06:47.960
<v Speaker 6>and understanding why this particular episode is likely to turn

0:06:47.960 --> 0:06:49.640
<v Speaker 6>out to be historically really important.

0:06:50.200 --> 0:06:53.679
<v Speaker 2>Wait, when you say you're referred to this podcast episode,

0:06:53.720 --> 0:06:57.040
<v Speaker 2>you're not referring to the broader episode of AI data Center.

0:06:57.160 --> 0:06:58.960
<v Speaker 5>Entirely, just the podcast.

0:07:01.080 --> 0:07:03.480
<v Speaker 6>Who Cares about data centers at the ten year anniversary

0:07:03.480 --> 0:07:06.680
<v Speaker 6>of bad Law. So the reason why sort of it's

0:07:06.680 --> 0:07:08.800
<v Speaker 6>going to be historically important is because, for the first time,

0:07:08.839 --> 0:07:12.160
<v Speaker 6>we combine all the major ingredients of every historical bubbles

0:07:12.160 --> 0:07:14.280
<v Speaker 6>in a single bubble. We have a metabubble no pun

0:07:14.320 --> 0:07:17.400
<v Speaker 6>intended for meta. We have real estate. You guys just

0:07:17.400 --> 0:07:19.640
<v Speaker 6>talked about this, right, Some of the largest bubbles in

0:07:19.720 --> 0:07:22.640
<v Speaker 6>US history had some relationship to real estate. We have

0:07:22.680 --> 0:07:25.880
<v Speaker 6>a great technology story. Almost all the large modern bubbles

0:07:25.880 --> 0:07:27.200
<v Speaker 6>has something to do with technology.

0:07:27.200 --> 0:07:28.120
<v Speaker 5>We have loose credit.

0:07:28.480 --> 0:07:30.880
<v Speaker 6>Most of the major bubbles in some sense have a

0:07:30.920 --> 0:07:34.480
<v Speaker 6>loose credit aspect. And one of the other exacerbating pieces

0:07:34.520 --> 0:07:36.800
<v Speaker 6>that some of the largest bubbles, thinking about even the

0:07:36.800 --> 0:07:40.240
<v Speaker 6>financial crisis, is some kind of notional government backstop. You know,

0:07:40.280 --> 0:07:43.520
<v Speaker 6>think about the role in terms of broadening home ownership

0:07:43.520 --> 0:07:45.320
<v Speaker 6>in the context of the real estate bubble, and the

0:07:45.400 --> 0:07:48.160
<v Speaker 6>role that Fanny and Freddie played and loosening credit standards

0:07:48.160 --> 0:07:50.560
<v Speaker 6>and all of those things. This is the first bubble

0:07:50.600 --> 0:07:52.760
<v Speaker 6>that has all of that. It's like, we said, you

0:07:52.800 --> 0:07:56.040
<v Speaker 6>know what would be great, Let's create a bubble that

0:07:56.160 --> 0:07:58.040
<v Speaker 6>takes everything that ever worked and put it.

0:07:58.000 --> 0:07:59.720
<v Speaker 5>All in one. And this is what we've done.

0:08:00.120 --> 0:08:02.480
<v Speaker 6>Got a speculative real estate component is probably one of

0:08:02.520 --> 0:08:07.440
<v Speaker 6>the strongest technology stories we ever had back to rural electrification.

0:08:07.560 --> 0:08:09.840
<v Speaker 6>In terms of a technology story, we have loose credit.

0:08:09.880 --> 0:08:12.800
<v Speaker 6>You guys talked about what's happening with respect to not

0:08:12.880 --> 0:08:14.840
<v Speaker 6>just the role of private credit, but how private credit

0:08:14.880 --> 0:08:17.840
<v Speaker 6>is largely supplanted commercial banks with respect to being lenders here.

0:08:18.000 --> 0:08:19.560
<v Speaker 6>So we have all of these pieces that have all

0:08:19.560 --> 0:08:21.200
<v Speaker 6>come together at once, and I think in terms of

0:08:21.240 --> 0:08:24.360
<v Speaker 6>framing what's going on right now. It's really important to

0:08:24.480 --> 0:08:28.040
<v Speaker 6>understand that it brings together all of these components and

0:08:28.080 --> 0:08:29.720
<v Speaker 6>ways we've never seen before, which is one of the

0:08:29.720 --> 0:08:31.720
<v Speaker 6>reasons why the notion that we can land this thing

0:08:31.840 --> 0:08:33.560
<v Speaker 6>on the runway gently is nonsense.

0:08:34.360 --> 0:08:37.160
<v Speaker 3>I love that framing the metal babble is perfect. Also,

0:08:37.520 --> 0:08:40.120
<v Speaker 3>I had an epiphany earlier. I already told Joe, so

0:08:40.160 --> 0:08:43.040
<v Speaker 3>you can attest to this, but I realized private credit

0:08:43.640 --> 0:08:47.000
<v Speaker 3>kind of supplanted shadow banking as the term. Right like

0:08:47.240 --> 0:08:49.800
<v Speaker 3>after two thousand and eight, we called it shadow banking,

0:08:50.240 --> 0:08:52.480
<v Speaker 3>and then at some point it flipped to I guess

0:08:52.559 --> 0:08:54.480
<v Speaker 3>the couplier private credit.

0:08:54.559 --> 0:08:57.120
<v Speaker 2>Shadow bank always owned it sinister right away that private

0:08:57.120 --> 0:08:57.560
<v Speaker 2>credit is.

0:08:57.559 --> 0:08:59.560
<v Speaker 3>Well, someone figured that out and they're like, well, now

0:08:59.559 --> 0:09:00.439
<v Speaker 3>it's private credit.

0:09:00.520 --> 0:09:01.640
<v Speaker 5>I like to think of it as a kind of

0:09:01.679 --> 0:09:05.880
<v Speaker 5>financial witness protection program. It was like, oh, you're those guys.

0:09:06.200 --> 0:09:07.480
<v Speaker 5>That's great, now who you are?

0:09:07.920 --> 0:09:10.120
<v Speaker 6>Yeah, it's kind of like that, And it's now like

0:09:10.200 --> 0:09:13.000
<v Speaker 6>one point whatever. It is one point seven trillion dollars

0:09:13.080 --> 0:09:16.560
<v Speaker 6>is the size of which is larger than many components

0:09:16.559 --> 0:09:19.040
<v Speaker 6>of the orthodox lending market combined. In terms of the

0:09:19.080 --> 0:09:21.839
<v Speaker 6>private credit industry itself, so that's a huge new piece

0:09:21.840 --> 0:09:24.520
<v Speaker 6>of this that sometimes escapes notice how big it is

0:09:24.520 --> 0:09:26.520
<v Speaker 6>and why it emerged, So all of those pieces.

0:09:26.640 --> 0:09:28.880
<v Speaker 3>Yeah, it's stunning the growth that we've seen. Let me

0:09:28.920 --> 0:09:31.840
<v Speaker 3>ask a very basic question before we go further. But

0:09:32.160 --> 0:09:35.719
<v Speaker 3>one thing I've been wondering is Joe mentioned that anthropic

0:09:35.760 --> 0:09:39.160
<v Speaker 3>headline that we heard before. We've seen Meta raising financing

0:09:39.200 --> 0:09:42.720
<v Speaker 3>for data center builds, all that stuff. Why do these

0:09:42.880 --> 0:09:47.679
<v Speaker 3>massively profitable and cash rich companies have to raise financing

0:09:48.120 --> 0:09:49.040
<v Speaker 3>at all?

0:09:49.240 --> 0:09:51.880
<v Speaker 6>Well, they don't, but there's these irritating shareholders out there

0:09:52.480 --> 0:09:55.560
<v Speaker 6>get all pissy whenever you start diluting earnings pre shared

0:09:55.559 --> 0:09:57.840
<v Speaker 6>too much and diverting it towards a single source. Now

0:09:57.840 --> 0:10:00.280
<v Speaker 6>that's not the case with private companies obviously, but by

0:10:00.320 --> 0:10:03.000
<v Speaker 6>the same token, open ai doesn't have the luxury of

0:10:03.000 --> 0:10:05.600
<v Speaker 6>having cash flows via which they can do any of

0:10:05.640 --> 0:10:09.200
<v Speaker 6>the things we're describing, so anthropic open Ai and everyone

0:10:09.200 --> 0:10:11.280
<v Speaker 6>else they have no option other than to do exactly

0:10:11.280 --> 0:10:13.560
<v Speaker 6>what we're describing. It's a different story with respect to

0:10:14.360 --> 0:10:16.840
<v Speaker 6>how what percentage of Google's free cash flow or Amazon

0:10:16.880 --> 0:10:19.240
<v Speaker 6>free cash flow that they want to continue to divert

0:10:19.440 --> 0:10:22.040
<v Speaker 6>towards data centers. So in terms of the privates, this

0:10:22.080 --> 0:10:25.000
<v Speaker 6>is the only option that they have. The public's obviously

0:10:25.000 --> 0:10:27.959
<v Speaker 6>increasing the hyperscalers increasingly. We've got up to the point

0:10:27.960 --> 0:10:30.520
<v Speaker 6>where around five hundred billion dollars or fifty percent of

0:10:30.520 --> 0:10:33.600
<v Speaker 6>their free cash flow is going directly towards spending on

0:10:33.760 --> 0:10:36.400
<v Speaker 6>data centers, and that's obviously a point at which you know,

0:10:36.480 --> 0:10:38.120
<v Speaker 6>we have other things we have to do with free

0:10:38.200 --> 0:10:41.440
<v Speaker 6>cash flow, and including having some of it be earnings

0:10:41.440 --> 0:10:44.160
<v Speaker 6>per share, and so we increasingly it's become the option.

0:10:44.320 --> 0:10:46.240
<v Speaker 5>You see what METT is doing recently with respect it

0:10:46.360 --> 0:10:47.119
<v Speaker 5>is SPVs.

0:10:47.400 --> 0:10:50.760
<v Speaker 6>We bring in other participants, create new financing vehicles, and

0:10:50.800 --> 0:10:52.920
<v Speaker 6>then we play this entertaining game of it's not really

0:10:53.000 --> 0:10:53.440
<v Speaker 6>our debt.

0:10:53.480 --> 0:10:55.320
<v Speaker 5>It's in an SPV. I don't have to roll it

0:10:55.360 --> 0:10:56.280
<v Speaker 5>back onto my own.

0:10:56.160 --> 0:10:58.839
<v Speaker 6>Balance sheet and then bring in new lenders, new private

0:10:58.840 --> 0:10:59.760
<v Speaker 6>credit firms and others.

0:11:00.000 --> 0:11:02.200
<v Speaker 5>So that's the reason. Obviously it's partly because of the scale.

0:11:02.240 --> 0:11:04.400
<v Speaker 6>It's probably because the privates who have no other option,

0:11:04.760 --> 0:11:07.400
<v Speaker 6>and it's probably we've kind of tapped out the public

0:11:07.440 --> 0:11:09.520
<v Speaker 6>companies in terms of the fraction of free cash flow

0:11:10.080 --> 0:11:10.920
<v Speaker 6>that they.

0:11:10.760 --> 0:11:14.920
<v Speaker 5>Feel as if they can spend with impunity on these projects.

0:11:14.640 --> 0:11:16.959
<v Speaker 2>Explain to us for those who don't know. You know, again,

0:11:17.160 --> 0:11:19.880
<v Speaker 2>SPV one of these terms that we really haven't heard

0:11:19.960 --> 0:11:22.400
<v Speaker 2>in a while. And there's nothing inherently bad about an

0:11:22.480 --> 0:11:25.720
<v Speaker 2>SPV except that you only hear about them typically after

0:11:25.840 --> 0:11:27.800
<v Speaker 2>there's something, you know, some sort of crazy.

0:11:27.679 --> 0:11:29.640
<v Speaker 5>Ride, which is weird obviously, But yes, tell.

0:11:29.559 --> 0:11:31.679
<v Speaker 2>How would you U say in the broad strokes, how

0:11:31.720 --> 0:11:34.800
<v Speaker 2>would you characterize what these financing vehicles are?

0:11:35.280 --> 0:11:37.959
<v Speaker 6>So Mechanically, it's just a way of making sure that

0:11:38.000 --> 0:11:39.720
<v Speaker 6>I don't have to roll data onto my balance sheet.

0:11:39.760 --> 0:11:42.960
<v Speaker 6>But legally it's a structure into which I and my

0:11:43.040 --> 0:11:46.439
<v Speaker 6>partners contribute capital that in exchange for which they retain

0:11:46.559 --> 0:11:49.600
<v Speaker 6>legal title to the project that we've created, which allows

0:11:49.679 --> 0:11:52.280
<v Speaker 6>us to all contribute capitalists but not have to put

0:11:52.280 --> 0:11:54.160
<v Speaker 6>it back on my balance sheet and therefore not to

0:11:54.200 --> 0:11:55.359
<v Speaker 6>have that debt rated.

0:11:55.640 --> 0:11:56.920
<v Speaker 5>Which is really the key.

0:11:57.040 --> 0:11:59.520
<v Speaker 6>Now, if you look at the actual intrinstics, say, for example,

0:11:59.559 --> 0:12:01.640
<v Speaker 6>the reason that a project that they did in conjunction

0:12:01.720 --> 0:12:04.720
<v Speaker 6>with blue Out, it's wild and byzantine. It looks like

0:12:04.760 --> 0:12:06.400
<v Speaker 6>something you might have seen and what was that in

0:12:06.440 --> 0:12:08.240
<v Speaker 6>Harry Potter or the forest with all the spider webs.

0:12:08.240 --> 0:12:09.720
<v Speaker 5>It looks a little like that, right where.

0:12:09.559 --> 0:12:11.640
<v Speaker 6>Everything's connected to everything and all I know is something

0:12:11.640 --> 0:12:14.160
<v Speaker 6>and here's going to get me. So there's incredible complexity,

0:12:14.200 --> 0:12:16.680
<v Speaker 6>but at the core, it's a mechanism via which I

0:12:16.679 --> 0:12:18.720
<v Speaker 6>can raise more capital and keep it off my balance

0:12:18.800 --> 0:12:21.280
<v Speaker 6>sheet by creating a legal entity that controls the actual

0:12:21.360 --> 0:12:23.559
<v Speaker 6>data center and I don't. Therefore I have to put

0:12:23.559 --> 0:12:26.400
<v Speaker 6>it back, roll it all back onto my balance sheet, navierated.

0:12:26.920 --> 0:12:31.320
<v Speaker 6>Now there's weird intricacies obviously, So for example, what happens

0:12:31.440 --> 0:12:34.400
<v Speaker 6>if at some period in the future this thing isn't

0:12:34.440 --> 0:12:37.120
<v Speaker 6>performing the way we expect who owns it at that point?

0:12:37.320 --> 0:12:38.960
<v Speaker 5>Is there a payment exchange, does.

0:12:38.840 --> 0:12:41.200
<v Speaker 6>It become metas, does it become blue ouls, does it

0:12:41.200 --> 0:12:45.000
<v Speaker 6>become someone else? And these things will turn out to matter.

0:12:45.080 --> 0:12:46.840
<v Speaker 6>Right now, no one cares. If you go through some

0:12:46.880 --> 0:12:49.040
<v Speaker 6>of the documents on these things, it's not entirely clear

0:12:49.480 --> 0:12:51.600
<v Speaker 6>what the recourse payment will be when it ever, if

0:12:51.600 --> 0:12:54.120
<v Speaker 6>and when it ever has to revert back to another owner,

0:12:54.160 --> 0:12:55.760
<v Speaker 6>and it's not going to be held on to by

0:12:55.760 --> 0:12:57.440
<v Speaker 6>the SPV. And I think this will turn out to

0:12:57.440 --> 0:12:59.480
<v Speaker 6>be really important four or five years down the road,

0:13:00.080 --> 0:13:14.200
<v Speaker 6>but right now nobody cares.

0:13:16.960 --> 0:13:21.199
<v Speaker 3>So Number one, the lifespan of data centers is actually

0:13:21.360 --> 0:13:24.440
<v Speaker 3>not that long. I can't remember the exact estimate, but

0:13:24.480 --> 0:13:27.000
<v Speaker 3>maybe like three or four years something like that. And

0:13:27.040 --> 0:13:30.160
<v Speaker 3>then also you have this risk that tenants are sort

0:13:30.200 --> 0:13:33.240
<v Speaker 3>of rolling through and no one knows what that actually

0:13:33.280 --> 0:13:35.200
<v Speaker 3>means for the structure of the debt, and you kind

0:13:35.200 --> 0:13:37.080
<v Speaker 3>of get this asset liability mismatch.

0:13:37.760 --> 0:13:40.280
<v Speaker 6>Yeah, so I'll start with the first one first. So

0:13:40.520 --> 0:13:42.760
<v Speaker 6>this gets into something Michael Berry was tweeting about the

0:13:42.800 --> 0:13:46.319
<v Speaker 6>other day, which was sort of entertaining that back about

0:13:46.360 --> 0:13:51.120
<v Speaker 6>four years ago, tech companies changed the appreciation schedule or

0:13:51.160 --> 0:13:53.040
<v Speaker 6>the assets inside of data centers.

0:13:53.240 --> 0:13:57.200
<v Speaker 5>They extended them somewhat. Now, that wasn't an error.

0:13:57.240 --> 0:14:00.520
<v Speaker 6>The reality is that data centers used for the purposes

0:14:00.559 --> 0:14:02.400
<v Speaker 6>like at aws, where You've got a big S three

0:14:02.440 --> 0:14:05.160
<v Speaker 6>bucket and I'm storing data inside of it. Those things

0:14:05.280 --> 0:14:08.280
<v Speaker 6>generally speaking, the assets are long lived. I'm not running

0:14:08.280 --> 0:14:10.880
<v Speaker 6>them flat out, it's not. These are not streetcar racers

0:14:10.880 --> 0:14:13.200
<v Speaker 6>that I'm running around inside of a data center. These

0:14:13.200 --> 0:14:16.640
<v Speaker 6>are relatively inexpensive chips that I'm using for really mundane

0:14:16.679 --> 0:14:20.680
<v Speaker 6>purposes like storing large amounts terabytes exhibites of data inside

0:14:20.680 --> 0:14:23.080
<v Speaker 6>of s three buckets, so it's not unreasonable to say

0:14:23.080 --> 0:14:26.040
<v Speaker 6>their lifespans fairly long. They're not being taxed that heavily,

0:14:26.160 --> 0:14:29.160
<v Speaker 6>so pushing out the depreciation schedule makes a lot of sense.

0:14:29.240 --> 0:14:32.640
<v Speaker 6>But that was coincident with the emergence of GPU driven

0:14:32.720 --> 0:14:36.000
<v Speaker 6>data centers using products like the chips from Nvidia, and

0:14:36.040 --> 0:14:39.200
<v Speaker 6>those have much shorter lifespans, so depending on the usage.

0:14:39.200 --> 0:14:39.720
<v Speaker 5>So there's two.

0:14:39.640 --> 0:14:44.400
<v Speaker 6>Different reasons why the lifespan and therefore the depreciation schedule

0:14:44.440 --> 0:14:46.760
<v Speaker 6>of a GPU inside of a data center is very different.

0:14:46.880 --> 0:14:49.560
<v Speaker 6>So the reason most people think about is, oh, well,

0:14:49.640 --> 0:14:51.720
<v Speaker 6>technology changes really quickly and I want to have the

0:14:51.800 --> 0:14:53.400
<v Speaker 6>latest and greatest, and therefore I'm going to have to

0:14:53.480 --> 0:14:58.320
<v Speaker 6>upgrade all the time. That's important, but it's probably about equal,

0:14:58.360 --> 0:15:01.600
<v Speaker 6>if not maybe slightly less important the nature of how

0:15:01.640 --> 0:15:04.200
<v Speaker 6>the chip is used inside the data center. So when

0:15:04.280 --> 0:15:07.560
<v Speaker 6>you run using like the latest, say a Nvidia chip

0:15:07.600 --> 0:15:10.160
<v Speaker 6>for training a model, those things are being run flat

0:15:10.160 --> 0:15:12.480
<v Speaker 6>out twenty four hours a day, seven days a week,

0:15:12.480 --> 0:15:14.720
<v Speaker 6>which is why they're liquid cool. They're inside of these

0:15:15.080 --> 0:15:17.520
<v Speaker 6>giant centers where one of your primary problems is keeping

0:15:17.560 --> 0:15:18.120
<v Speaker 6>them all cool.

0:15:18.600 --> 0:15:20.880
<v Speaker 5>It's like saying I bought a used car and.

0:15:20.840 --> 0:15:22.720
<v Speaker 6>I don't care what it was used for. Well, if

0:15:22.760 --> 0:15:24.440
<v Speaker 6>it turns out it was used by someone who was

0:15:24.480 --> 0:15:27.240
<v Speaker 6>doing like Laman's twenty four hours of endurance with it,

0:15:27.480 --> 0:15:30.160
<v Speaker 6>that's very different. Even if the mileage is the same

0:15:30.200 --> 0:15:31.280
<v Speaker 6>as someone who only drove to.

0:15:31.320 --> 0:15:32.200
<v Speaker 5>Church on Sundays.

0:15:32.360 --> 0:15:36.720
<v Speaker 6>Right, these are very different consequences with respect to what's

0:15:36.760 --> 0:15:38.920
<v Speaker 6>called the thermal degradation of the chip. The chip's been

0:15:39.000 --> 0:15:42.440
<v Speaker 6>run hot and flat out, so it probably it's useful.

0:15:42.480 --> 0:15:45.400
<v Speaker 6>Lifespan might be on the order of two years, maybe

0:15:45.400 --> 0:15:48.680
<v Speaker 6>even eighteen months. So there's a huge difference in terms

0:15:48.720 --> 0:15:51.800
<v Speaker 6>of how the chip was used, leaving aside whether or

0:15:51.840 --> 0:15:53.600
<v Speaker 6>not there's a new generation of what's come along. So

0:15:53.760 --> 0:15:56.920
<v Speaker 6>that takes us back to these depreciation schedules. So these

0:15:56.960 --> 0:16:00.920
<v Speaker 6>depreciation schedules change, just as the nature of how the

0:16:00.920 --> 0:16:04.360
<v Speaker 6>lifespan of the chips changed dramatically, because I can use

0:16:04.360 --> 0:16:06.560
<v Speaker 6>something for you know, storing things in s three buckets

0:16:06.600 --> 0:16:08.720
<v Speaker 6>for a long time, six to eight years isn't unreasonable.

0:16:09.200 --> 0:16:12.760
<v Speaker 6>But if I'm doing the the Laman's endurance equivalent with

0:16:12.880 --> 0:16:16.200
<v Speaker 6>a GPU, it might be eighteen months. That's a huge

0:16:16.240 --> 0:16:19.000
<v Speaker 6>difference in terms of the likely lifespan of a product

0:16:19.040 --> 0:16:21.840
<v Speaker 6>that I'm depreciating over a very different period. And so

0:16:21.920 --> 0:16:24.280
<v Speaker 6>that's a huge part of the problem here with respect

0:16:24.320 --> 0:16:28.440
<v Speaker 6>to understanding the intrinsics in terms of how data centers

0:16:29.040 --> 0:16:31.360
<v Speaker 6>can and can't make money. How you have to think

0:16:31.400 --> 0:16:34.560
<v Speaker 6>about the likely capex requirements because of this much shorter

0:16:34.640 --> 0:16:37.000
<v Speaker 6>life span of the underlying technology, and then.

0:16:36.840 --> 0:16:40.400
<v Speaker 3>Talk about the tenancy rollover risk. I guess we might

0:16:40.400 --> 0:16:40.760
<v Speaker 3>call it.

0:16:41.200 --> 0:16:44.760
<v Speaker 6>Yeah, it's really interesting. So one way to think about

0:16:45.160 --> 0:16:48.160
<v Speaker 6>data centers is as giant apartment buildings. Right, They're essentially

0:16:48.200 --> 0:16:50.560
<v Speaker 6>gigantic commercial pieces of commercial real estate with a bunch

0:16:50.600 --> 0:16:53.560
<v Speaker 6>of tenants. Sometimes there's a lot of tenants, sometimes there's

0:16:53.560 --> 0:16:55.920
<v Speaker 6>only one. Sometimes Google bought the whole apartment building and

0:16:55.960 --> 0:16:57.760
<v Speaker 6>just moved in, Or it's a giant office building they

0:16:57.800 --> 0:16:59.840
<v Speaker 6>just moved in. It's all theirs, right, So think about

0:16:59.880 --> 0:17:02.320
<v Speaker 6>it in those sorts of terms. And the reason why

0:17:02.400 --> 0:17:04.960
<v Speaker 6>as a sponsor of a data center I might take

0:17:05.000 --> 0:17:07.159
<v Speaker 6>a different view on how many tenants I want is

0:17:07.200 --> 0:17:09.720
<v Speaker 6>again you think about it in terms of what can

0:17:09.760 --> 0:17:11.919
<v Speaker 6>I get Google to pay? But whereasus what can I

0:17:12.000 --> 0:17:15.000
<v Speaker 6>get someone who's a much flightier tenant to pay? Well,

0:17:15.040 --> 0:17:17.399
<v Speaker 6>I can get the flightier tenants, more of them and

0:17:17.480 --> 0:17:21.440
<v Speaker 6>diversified as all leasing inside the data center, paying higher

0:17:21.560 --> 0:17:24.800
<v Speaker 6>lease rates for GPUs over the period of tendency than

0:17:24.800 --> 0:17:26.840
<v Speaker 6>I can get a Google to pay. Why because Google's

0:17:26.840 --> 0:17:28.880
<v Speaker 6>got great credit, they don't have to pay very much

0:17:28.880 --> 0:17:29.600
<v Speaker 6>and they know they don't.

0:17:29.600 --> 0:17:31.280
<v Speaker 5>So if you look at the commercial real estate.

0:17:31.200 --> 0:17:34.520
<v Speaker 6>Data, the cap rate, the blended cap rate for these

0:17:34.560 --> 0:17:37.320
<v Speaker 6>for the largest data centers that are tenanted by hyperscalers

0:17:37.920 --> 0:17:41.000
<v Speaker 6>is horrible. It's like four point eight five point three percent.

0:17:41.119 --> 0:17:43.920
<v Speaker 6>It's like, why don't you just buy a treasure you're doing.

0:17:44.160 --> 0:17:47.440
<v Speaker 6>So what happens then is people start blending in more

0:17:47.440 --> 0:17:50.359
<v Speaker 6>different kinds of tenants to Tracy's point, as an effort

0:17:50.400 --> 0:17:53.240
<v Speaker 6>to try and improve the yield the cap rate on

0:17:53.600 --> 0:17:56.240
<v Speaker 6>the underlying instrument, which is the data center. So you

0:17:56.280 --> 0:17:58.440
<v Speaker 6>could do all of this should start to sound familiar

0:17:58.520 --> 0:18:01.040
<v Speaker 6>because it's this idea of a blend together all of

0:18:01.040 --> 0:18:03.359
<v Speaker 6>these different tendencies. I can increase the yield of the

0:18:03.400 --> 0:18:07.479
<v Speaker 6>securitized instrument, but that also changes the risk profile of

0:18:07.520 --> 0:18:09.400
<v Speaker 6>what comes out at the other end, which just takes

0:18:09.480 --> 0:18:12.920
<v Speaker 6>us to things like the increasing usage of these things

0:18:12.920 --> 0:18:15.639
<v Speaker 6>in asset backed securities, which are these trench securities that

0:18:15.720 --> 0:18:18.359
<v Speaker 6>have all the different pieces, We have different layers associated

0:18:18.400 --> 0:18:21.399
<v Speaker 6>with it, and that's a reflection of well, there's different

0:18:21.440 --> 0:18:24.280
<v Speaker 6>tenants inside these data centers, and people want different exposures

0:18:24.280 --> 0:18:26.240
<v Speaker 6>to risks. So I may only want to buy the

0:18:26.280 --> 0:18:29.440
<v Speaker 6>senior tranch. You may want to buy the mezzanine and trace.

0:18:29.520 --> 0:18:31.560
<v Speaker 6>He may want to buy the equity charge.

0:18:31.800 --> 0:18:33.959
<v Speaker 3>Can I just say, I know we already said this,

0:18:34.359 --> 0:18:39.719
<v Speaker 3>but Paul is truly, truly the perfect guest. I remember

0:18:39.720 --> 0:18:43.359
<v Speaker 3>reading his coverage of subprime and securitization in like two

0:18:43.400 --> 0:18:45.560
<v Speaker 3>thousand and eight, and so having someone who's able to

0:18:45.640 --> 0:18:49.880
<v Speaker 3>synthesize that experience with what's going on now is just fantastic.

0:18:50.040 --> 0:18:51.760
<v Speaker 2>I kind of can't believe we're doing this again. I know,

0:18:51.800 --> 0:18:54.280
<v Speaker 2>I mean, look, I mean again, there's nothing inherently wrong

0:18:54.320 --> 0:18:58.960
<v Speaker 2>with SPVs. There's nothing inherently wrong tranching, right, Like a

0:18:58.960 --> 0:19:02.159
<v Speaker 2>lot of these things are very intuitive, etc. But it

0:19:02.240 --> 0:19:05.360
<v Speaker 2>is still a little weird how central this is and

0:19:05.400 --> 0:19:08.639
<v Speaker 2>how it's the same old There's nothing I mean, on

0:19:08.680 --> 0:19:10.520
<v Speaker 2>some financial level, it feels very familiar.

0:19:10.680 --> 0:19:12.520
<v Speaker 5>No, there's nothing new un to the sun.

0:19:13.160 --> 0:19:15.199
<v Speaker 6>But I think that point is really important It's not

0:19:15.280 --> 0:19:18.200
<v Speaker 6>that tranches are evil. It's not the securitization is evil,

0:19:18.280 --> 0:19:20.840
<v Speaker 6>or that asset backed security your project finance is evil.

0:19:21.200 --> 0:19:26.000
<v Speaker 5>No, all of these things are terrific pieces of the arsenal.

0:19:26.040 --> 0:19:28.920
<v Speaker 6>Whenever you're actually raising money for projects, the issues start

0:19:28.960 --> 0:19:30.800
<v Speaker 6>to arise at the scale, which is what you guys

0:19:30.840 --> 0:19:34.200
<v Speaker 6>have already alluded to. But the secondary piece, which again

0:19:34.280 --> 0:19:37.560
<v Speaker 6>will sound painfully familiar to the financial crisis, is there's

0:19:37.560 --> 0:19:40.119
<v Speaker 6>a flywheel that gets created at the back end of this.

0:19:40.680 --> 0:19:44.600
<v Speaker 6>So once you start securitizing the yield producing assets in

0:19:44.640 --> 0:19:47.720
<v Speaker 6>the form of these tranch securities, the people who are

0:19:47.720 --> 0:19:50.640
<v Speaker 6>purchasing those things don't give a rats ask what's going

0:19:50.680 --> 0:19:53.919
<v Speaker 6>on inside this AI. I joke all the time that

0:19:53.960 --> 0:19:55.720
<v Speaker 6>a lot of these people can't spell AI. They don't

0:19:55.720 --> 0:19:57.359
<v Speaker 6>care what's going on inside the.

0:19:57.400 --> 0:19:58.520
<v Speaker 5>Data center, right.

0:19:59.119 --> 0:20:00.840
<v Speaker 6>It could be you know, the world Hide and Go

0:20:00.920 --> 0:20:03.359
<v Speaker 6>Seek Championships had going on in there. I don't care

0:20:03.600 --> 0:20:05.240
<v Speaker 6>as long as it generates heels and I.

0:20:05.160 --> 0:20:06.280
<v Speaker 5>Can securitize it.

0:20:06.600 --> 0:20:06.719
<v Speaker 3>Well.

0:20:06.720 --> 0:20:09.000
<v Speaker 6>It's very much an analogous to what's happened in prior

0:20:09.080 --> 0:20:12.440
<v Speaker 6>periods like this, where again you get this secondary flywheel

0:20:12.480 --> 0:20:15.840
<v Speaker 6>effect of let's just create more of these things because

0:20:15.840 --> 0:20:18.680
<v Speaker 6>our customers want more and they're really easy to securitize

0:20:18.720 --> 0:20:20.520
<v Speaker 6>and look gets backst up by Meta and Google or

0:20:20.520 --> 0:20:21.040
<v Speaker 6>whoever else.

0:20:21.160 --> 0:20:24.200
<v Speaker 2>Well, so this actually brings important point. I mentioned this

0:20:24.359 --> 0:20:27.040
<v Speaker 2>great report out from the Center for Public Enterprise. One

0:20:27.080 --> 0:20:31.120
<v Speaker 2>of the things that they pointed out is in this

0:20:31.280 --> 0:20:34.720
<v Speaker 2>market environment where everyone is just you know, there's this

0:20:34.800 --> 0:20:38.399
<v Speaker 2>sort of AI pixi us, but also just the reality

0:20:38.440 --> 0:20:41.040
<v Speaker 2>if your revenues are surging, the market probably loves you,

0:20:41.920 --> 0:20:45.399
<v Speaker 2>like talk to us about the unit economics. Here is

0:20:45.400 --> 0:20:48.960
<v Speaker 2>the incentive for all the players essentially to just grow

0:20:49.080 --> 0:20:52.920
<v Speaker 2>the top line as much as possible, even if these

0:20:52.960 --> 0:20:56.320
<v Speaker 2>aren't whether we're talking about inference on a per token basis,

0:20:56.720 --> 0:20:59.119
<v Speaker 2>even if these aren't particularly profitable, how do you think

0:20:59.160 --> 0:21:01.880
<v Speaker 2>about the union economics of some of these businesses and

0:21:01.960 --> 0:21:05.200
<v Speaker 2>how that could eventually perhaps sort of you know, come

0:21:05.240 --> 0:21:06.280
<v Speaker 2>home to Ruster to speak.

0:21:06.600 --> 0:21:07.359
<v Speaker 5>Yeah, So.

0:21:09.160 --> 0:21:11.159
<v Speaker 6>The term of art obviously is these things have negative

0:21:11.240 --> 0:21:13.840
<v Speaker 6>unit economics, which is a fancy way of saying that

0:21:13.880 --> 0:21:15.639
<v Speaker 6>we lose money on every sale and try to make

0:21:15.640 --> 0:21:18.200
<v Speaker 6>it up on volume. Right, I mean, that's the that's

0:21:18.200 --> 0:21:20.320
<v Speaker 6>the problem here. So but that's okay, I mean, we've

0:21:20.320 --> 0:21:21.960
<v Speaker 6>had lots of Amazon.

0:21:21.520 --> 0:21:24.119
<v Speaker 5>In its early days that negative unit economics. You can

0:21:24.119 --> 0:21:24.760
<v Speaker 5>get past that.

0:21:25.080 --> 0:21:27.000
<v Speaker 6>And as an aside, I'll say right here, all of

0:21:27.000 --> 0:21:28.639
<v Speaker 6>the things that I'm saying is and to say that

0:21:28.720 --> 0:21:31.760
<v Speaker 6>you know AI is some kind of you know, free

0:21:31.960 --> 0:21:36.040
<v Speaker 6>tamagatche thing, that's just a fad as an incredibly important technology.

0:21:36.240 --> 0:21:38.439
<v Speaker 6>What we're talking about is how it's funded and the

0:21:38.440 --> 0:21:40.600
<v Speaker 6>consequences of doing that in terms of what's going to

0:21:40.600 --> 0:21:42.639
<v Speaker 6>happen with respect to the businesses and the return on

0:21:42.680 --> 0:21:46.680
<v Speaker 6>those businesses. Right, So, the unit economics are dire for

0:21:46.800 --> 0:21:49.280
<v Speaker 6>a bunch of reasons, have mostly having to do with

0:21:49.960 --> 0:21:52.840
<v Speaker 6>the more tokens you have to produce. The costs rise

0:21:53.040 --> 0:21:56.280
<v Speaker 6>more or less linearly with the demand on the system.

0:21:56.320 --> 0:21:59.600
<v Speaker 6>As opposed to an orthodox software business where the more

0:21:59.640 --> 0:22:02.280
<v Speaker 6>people use my service, the more people across which I

0:22:02.280 --> 0:22:05.800
<v Speaker 6>can spread my relatively fixed costs. That's not the way

0:22:05.960 --> 0:22:09.800
<v Speaker 6>that for the most part, current generation large language models

0:22:09.840 --> 0:22:14.200
<v Speaker 6>were costs rise linearly or sublinearly with the number of users,

0:22:14.240 --> 0:22:16.680
<v Speaker 6>which makes for really crappy unit.

0:22:16.480 --> 0:22:18.280
<v Speaker 5>Economics, and that's a big part of the problem.

0:22:18.359 --> 0:22:20.600
<v Speaker 6>So from there you get to the question of Okay,

0:22:20.680 --> 0:22:22.280
<v Speaker 6>so what does it have to look like in terms

0:22:22.280 --> 0:22:25.159
<v Speaker 6>of making it look profitable. There's lots of ways to

0:22:25.200 --> 0:22:27.000
<v Speaker 6>back into this. You can do bottoms up models. It

0:22:27.040 --> 0:22:29.560
<v Speaker 6>would suggest that like if every iPhone newsrun earth paid

0:22:29.560 --> 0:22:33.160
<v Speaker 6>fifty bucks do at work, we could have around a

0:22:33.160 --> 0:22:35.760
<v Speaker 6>four hundred billion dollar, five hundred billion dollar annual stream

0:22:35.760 --> 0:22:37.480
<v Speaker 6>of revenue flowing. And well, that's not going to happen,

0:22:37.560 --> 0:22:39.080
<v Speaker 6>but it's worth pointing out like that would do it.

0:22:39.119 --> 0:22:40.480
<v Speaker 6>But it gives you a sense of the kind of

0:22:40.520 --> 0:22:44.280
<v Speaker 6>scale of what at a consumer level, for example, it

0:22:44.359 --> 0:22:45.159
<v Speaker 6>might have to look like.

0:22:45.560 --> 0:22:46.800
<v Speaker 5>People come out it from the other end.

0:22:46.800 --> 0:22:48.320
<v Speaker 6>One of my favorite ways that people come out is

0:22:48.320 --> 0:22:50.520
<v Speaker 6>to say, well, we could create a viable model here.

0:22:50.520 --> 0:22:53.200
<v Speaker 6>If you think this was in the JPM call last week.

0:22:53.200 --> 0:22:54.600
<v Speaker 6>I don't know if you guys saw the summary of it,

0:22:54.640 --> 0:22:57.040
<v Speaker 6>but it was huge fun for the whole family listening.

0:22:57.080 --> 0:22:59.560
<v Speaker 6>And so one of the ways they backed into it

0:22:59.560 --> 0:23:02.400
<v Speaker 6>was a top model where they said, well, the global

0:23:02.520 --> 0:23:04.639
<v Speaker 6>TAM for human labor.

0:23:05.480 --> 0:23:08.560
<v Speaker 5>I love the five trillion dollars. I love the global TAM.

0:23:08.600 --> 0:23:08.880
<v Speaker 5>I said.

0:23:08.920 --> 0:23:10.720
<v Speaker 6>That was right up there with saying like if I

0:23:10.800 --> 0:23:13.240
<v Speaker 6>reduce humans to their chemical components, here's what.

0:23:13.200 --> 0:23:13.879
<v Speaker 5>I can get for you.

0:23:14.240 --> 0:23:17.600
<v Speaker 3>Well, this was this was Steve Eisman's line, which was like,

0:23:17.800 --> 0:23:21.080
<v Speaker 3>beware of anyone that mentions tam right.

0:23:21.040 --> 0:23:23.200
<v Speaker 6>Right, right, no exactly, and so then and then they play.

0:23:23.280 --> 0:23:26.240
<v Speaker 6>The next step is of course to say, well, imagine

0:23:26.280 --> 0:23:28.600
<v Speaker 6>we can get ten percent of that, right, which is

0:23:28.880 --> 0:23:31.240
<v Speaker 6>which is obviously one of the oldest cliches. It's like saying,

0:23:31.240 --> 0:23:32.600
<v Speaker 6>you know, I'm going to get five percent of the

0:23:32.680 --> 0:23:34.560
<v Speaker 6>Chinese market. No one ever gets five percent of the

0:23:34.600 --> 0:23:35.160
<v Speaker 6>Chinese market.

0:23:35.240 --> 0:23:35.800
<v Speaker 5>This doesn't happen.

0:23:35.880 --> 0:23:38.480
<v Speaker 6>So the same thing won't happen with global labor. But

0:23:38.560 --> 0:23:40.200
<v Speaker 6>if you were to do that, you do the math

0:23:40.280 --> 0:23:42.600
<v Speaker 6>on that that call those kinds of numbers gets you

0:23:42.680 --> 0:23:45.480
<v Speaker 6>to a weighted average cost of capital basis to a

0:23:45.480 --> 0:23:48.680
<v Speaker 6>reasonable return on current and planned expenditures with respect to

0:23:48.760 --> 0:23:51.320
<v Speaker 6>AI data centers. If you assume we're heading to about

0:23:51.320 --> 0:23:54.120
<v Speaker 6>a three or four trillion dollar a number, which is

0:23:54.359 --> 0:23:57.119
<v Speaker 6>kind of the I think it's around the number that

0:23:57.160 --> 0:23:58.600
<v Speaker 6>most people put out there, which I think is a

0:23:58.600 --> 0:24:00.880
<v Speaker 6>completely wrong number, but nevertheles that's the kind of number

0:24:00.880 --> 0:24:01.919
<v Speaker 6>and what you'd have to do to get there.

0:24:01.960 --> 0:24:02.800
<v Speaker 5>So you can get there from.

0:24:02.640 --> 0:24:05.600
<v Speaker 6>A bottoms up model by making some really unreasonable assumptions

0:24:05.640 --> 0:24:07.920
<v Speaker 6>about the total numbers of subscribers and what they pay.

0:24:08.400 --> 0:24:10.639
<v Speaker 6>You can get there from a top down model. You

0:24:10.680 --> 0:24:12.600
<v Speaker 6>can also get there by thinking about it purely in

0:24:12.680 --> 0:24:16.400
<v Speaker 6>terms of industrial users. I think about purely API users

0:24:16.480 --> 0:24:19.879
<v Speaker 6>just for end retail users of AI don't exist. And say,

0:24:20.200 --> 0:24:22.720
<v Speaker 6>you know, Andthropics projecting seventy billion dollars in revenue in

0:24:22.760 --> 0:24:25.320
<v Speaker 6>twenty twenty eight, something like thirty five percent of their

0:24:25.320 --> 0:24:28.800
<v Speaker 6>current revenues. Most of their revenues today are from their API.

0:24:29.080 --> 0:24:31.960
<v Speaker 6>Thirty five percent of that is from software developers that

0:24:32.080 --> 0:24:37.000
<v Speaker 6>split between two large users, Copilot and Cursor. And so

0:24:37.119 --> 0:24:38.920
<v Speaker 6>you know, we can model that out. Everybody has to

0:24:39.000 --> 0:24:40.560
<v Speaker 6>become a software developer.

0:24:40.160 --> 0:24:41.480
<v Speaker 5>And we can make the math work.

0:24:41.720 --> 0:24:44.400
<v Speaker 6>The problem is it's got huge fragility right in customer

0:24:44.440 --> 0:24:48.159
<v Speaker 6>concentration risk. So a Cursor disappears as a user of

0:24:48.280 --> 0:24:51.399
<v Speaker 6>Entropics API, and you just blew out fifteen percent of

0:24:51.920 --> 0:24:54.280
<v Speaker 6>your revenues because they're gone and they've done something else.

0:24:54.840 --> 0:24:56.640
<v Speaker 6>And as it turns out, Cursor a two weeks ago

0:24:56.680 --> 0:24:58.800
<v Speaker 6>announced that they were trading their own internal model that

0:24:58.840 --> 0:25:00.600
<v Speaker 6>you could use for software developed and you wouldn't have

0:25:00.680 --> 0:25:03.920
<v Speaker 6>to call the Anthropic API so you can think about

0:25:03.920 --> 0:25:05.800
<v Speaker 6>all these different ways to get there, but they all

0:25:05.840 --> 0:25:08.000
<v Speaker 6>have a lot of built in fragility with respect to

0:25:08.800 --> 0:25:11.040
<v Speaker 6>so we all become software developers and we all subscribe

0:25:11.080 --> 0:25:11.520
<v Speaker 6>to Cursor.

0:25:12.840 --> 0:25:15.000
<v Speaker 3>Just going back to the used car analogy that you

0:25:15.040 --> 0:25:18.160
<v Speaker 3>mentioned before, when we're thinking about all this financing of

0:25:18.440 --> 0:25:21.439
<v Speaker 3>the AI capex spen, is it useful to think of

0:25:22.000 --> 0:25:26.880
<v Speaker 3>GPUs essentially as the collateral the problem?

0:25:26.960 --> 0:25:28.160
<v Speaker 5>Yes, or what would you.

0:25:28.080 --> 0:25:29.720
<v Speaker 3>Call the collateral in this case?

0:25:29.920 --> 0:25:31.160
<v Speaker 5>So what ends up happening.

0:25:31.359 --> 0:25:33.040
<v Speaker 6>The collateral in this case is the gp There's no

0:25:33.119 --> 0:25:35.800
<v Speaker 6>question it is the GPA. The issue is this disconnect,

0:25:35.800 --> 0:25:38.600
<v Speaker 6>this temporal mismatch that you alluded to earlier with respect

0:25:38.600 --> 0:25:41.520
<v Speaker 6>to the duration of the underlying debt and the assets

0:25:41.520 --> 0:25:42.640
<v Speaker 6>that are producing.

0:25:42.400 --> 0:25:44.320
<v Speaker 5>The income that allows me to pay for the debt.

0:25:44.600 --> 0:25:48.159
<v Speaker 6>Right, so we've got this probably unprecedented temporal messmatch with

0:25:48.200 --> 0:25:52.120
<v Speaker 6>thirty year loans and two year depreciation on the underlying collateral,

0:25:52.160 --> 0:25:55.000
<v Speaker 6>which is essentially the GPUs that are the income producing assets.

0:25:55.840 --> 0:25:59.560
<v Speaker 6>And so that creates this constant refinancing risk because I'm

0:25:59.560 --> 0:26:01.040
<v Speaker 6>going to can you only have to turn over the

0:26:01.040 --> 0:26:03.720
<v Speaker 6>base And we've seen this many many times right now,

0:26:03.760 --> 0:26:05.480
<v Speaker 6>it's easy to turn it over, but in two years

0:26:05.480 --> 0:26:07.800
<v Speaker 6>it may not be possible. There's a wave of refinancings

0:26:07.840 --> 0:26:09.640
<v Speaker 6>coming in twenty twenty eight in many of the more.

0:26:09.560 --> 0:26:10.719
<v Speaker 5>Speculative data centers.

0:26:11.000 --> 0:26:12.639
<v Speaker 6>Will they be able to turn over their debt and

0:26:12.680 --> 0:26:14.399
<v Speaker 6>refinance all the GPUs today?

0:26:14.400 --> 0:26:16.320
<v Speaker 5>They could? This today is in twenty twenty eight.

0:26:16.800 --> 0:26:21.240
<v Speaker 6>So that's the inherent problem, is this structural temporal mismatch

0:26:21.320 --> 0:26:24.200
<v Speaker 6>between the income producing assets and the duration of the lungs.

0:26:24.200 --> 0:26:26.480
<v Speaker 6>And it gets worse if you think about it in

0:26:26.520 --> 0:26:29.320
<v Speaker 6>more realistic terms, think about it in terms of one

0:26:29.359 --> 0:26:31.720
<v Speaker 6>of the other gating factors here that's driving all.

0:26:31.600 --> 0:26:34.240
<v Speaker 5>Of this is the scarcity of energy supply. It's really difficult.

0:26:35.000 --> 0:26:36.680
<v Speaker 6>You can hook them up to the well. It's actually

0:26:36.720 --> 0:26:38.119
<v Speaker 6>kind of turned into a bit of a joke. I

0:26:38.119 --> 0:26:39.520
<v Speaker 6>can hook you up to the grid, but I can't

0:26:39.520 --> 0:26:40.800
<v Speaker 6>give you power. I don't know if you saw the

0:26:40.840 --> 0:26:43.800
<v Speaker 6>recent episode with the Oregon Public Utilities Commission, Amazon had

0:26:43.840 --> 0:26:46.840
<v Speaker 6>three data centers that they connected to the grid, and

0:26:46.880 --> 0:26:49.080
<v Speaker 6>it was kind of like the Oregon PUC said, Oh,

0:26:49.119 --> 0:26:51.840
<v Speaker 6>you want power too, Oh, I can't help you with that.

0:26:52.200 --> 0:26:53.040
<v Speaker 5>We can't help you with that.

0:26:53.160 --> 0:26:55.560
<v Speaker 6>So now there's a complaint in it the Oregon PUC

0:26:55.640 --> 0:26:59.480
<v Speaker 6>from ADS, Amazon's the digital services group that runs aws,

0:26:59.480 --> 0:27:01.440
<v Speaker 6>complaining we now have data centers, but.

0:27:01.400 --> 0:27:02.240
<v Speaker 5>We have no power.

0:27:02.800 --> 0:27:04.680
<v Speaker 6>Right it sounds a little bit like like a winter

0:27:04.800 --> 0:27:07.320
<v Speaker 6>storm hazard or something, but it's the structural problem with

0:27:07.359 --> 0:27:10.639
<v Speaker 6>respect to the inability. We can connect people, but we

0:27:10.680 --> 0:27:13.240
<v Speaker 6>can't provide them with power. So the next stage is

0:27:13.280 --> 0:27:15.639
<v Speaker 6>and this takes bets back to the collateral problem in

0:27:15.680 --> 0:27:18.560
<v Speaker 6>the temporal mismatch, is that people are doing behind the

0:27:18.600 --> 0:27:22.119
<v Speaker 6>meter power. They're building natural gas or if you're fair me,

0:27:22.320 --> 0:27:26.040
<v Speaker 6>you're saying wild things about nuclear power and you're saying, Okay,

0:27:26.080 --> 0:27:27.840
<v Speaker 6>I'm coming with my own power. You don't need to

0:27:27.880 --> 0:27:30.119
<v Speaker 6>connect me to the grid. I'm going to power this myself.

0:27:30.880 --> 0:27:33.199
<v Speaker 6>That creates two or three different issues, but among the

0:27:33.240 --> 0:27:36.360
<v Speaker 6>more important is think about how long lived an asset

0:27:36.400 --> 0:27:38.920
<v Speaker 6>a natural gas plant is. This is not something that's

0:27:38.960 --> 0:27:41.680
<v Speaker 6>got a five year lifespan and we just truly wave goodbye.

0:27:41.760 --> 0:27:44.480
<v Speaker 6>This is going to be running probably twenty five to

0:27:44.520 --> 0:27:47.919
<v Speaker 6>thirty years. And the only thing your ability to forecast.

0:27:48.560 --> 0:27:50.399
<v Speaker 6>We know the cost of the natural gas plant, but

0:27:50.440 --> 0:27:51.920
<v Speaker 6>in terms of the cost of the center, and it's

0:27:51.920 --> 0:27:54.840
<v Speaker 6>incompability to generate enough income to pay off the loan

0:27:54.880 --> 0:27:58.080
<v Speaker 6>associated with the natural gas plant. God help you if

0:27:58.119 --> 0:28:00.560
<v Speaker 6>you think you can sort that out, because what you've

0:28:00.560 --> 0:28:03.760
<v Speaker 6>really got is a huge likelihood of a stranded asset

0:28:03.800 --> 0:28:06.240
<v Speaker 6>of their natural gas plants that are longer useful for

0:28:06.359 --> 0:28:07.919
<v Speaker 6>powering these things that they were built for.

0:28:23.880 --> 0:28:26.840
<v Speaker 2>The good news is that Daniel Jurgen said this on

0:28:27.040 --> 0:28:31.359
<v Speaker 2>the show. You know the back orders for natural gas turbines,

0:28:31.359 --> 0:28:33.080
<v Speaker 2>like you probably if you ordered one today, you would

0:28:33.080 --> 0:28:35.440
<v Speaker 2>probably get it in twenty thirty. So the good news

0:28:35.480 --> 0:28:37.960
<v Speaker 2>that I suppose ten years is that at least you

0:28:38.000 --> 0:28:40.560
<v Speaker 2>don't have to have the turbines sitting there for years.

0:28:40.560 --> 0:28:42.160
<v Speaker 2>Like I don't know, Maybe I don't know if that's

0:28:42.200 --> 0:28:44.280
<v Speaker 2>good news at all, but there are se I may

0:28:44.320 --> 0:28:46.160
<v Speaker 2>never get it in, You may never get the gas

0:28:46.200 --> 0:28:48.440
<v Speaker 2>plant built. Anyway, someone will be stuck with the book.

0:28:48.760 --> 0:28:51.680
<v Speaker 6>It kind of raises this goes back to Tracy's question earlier.

0:28:51.720 --> 0:28:55.040
<v Speaker 6>This raises a really interesting thing. So like, honestly, what

0:28:55.120 --> 0:28:57.719
<v Speaker 6>the f are all these people doing who are announcing

0:28:58.920 --> 0:29:02.200
<v Speaker 6>the giant unding translation. I think of it like people

0:29:02.320 --> 0:29:04.560
<v Speaker 6>all showing up with the OK Corral at once and

0:29:04.600 --> 0:29:07.240
<v Speaker 6>It's like, dude over there has one gun, I got two.

0:29:07.280 --> 0:29:09.959
<v Speaker 3>Yeah, I got Oh that's not a nice this is anie.

0:29:10.160 --> 0:29:10.320
<v Speaker 5>Yeah.

0:29:10.600 --> 0:29:13.560
<v Speaker 6>But it's this deterrence. It's this deterrence program that's going on.

0:29:13.640 --> 0:29:16.560
<v Speaker 6>Don't even imagine spending fifty because I'm spending one hundred.

0:29:17.080 --> 0:29:19.360
<v Speaker 5>No point in you doing any of those. That's very

0:29:19.600 --> 0:29:20.520
<v Speaker 5>game theoretic.

0:29:20.800 --> 0:29:23.040
<v Speaker 3>Well, this also worries me because you hear so many

0:29:23.120 --> 0:29:27.200
<v Speaker 3>people framing this as like an existential competition. Right, and

0:29:27.240 --> 0:29:31.600
<v Speaker 3>once you start calling something existential, the limit on spend,

0:29:31.760 --> 0:29:33.000
<v Speaker 3>well it becomes unlimited.

0:29:33.080 --> 0:29:33.240
<v Speaker 5>Right.

0:29:33.360 --> 0:29:35.400
<v Speaker 3>It's about survival, so you'll spend anything.

0:29:35.520 --> 0:29:39.120
<v Speaker 2>That's why the conversation has turned in recent weeks to

0:29:39.240 --> 0:29:42.120
<v Speaker 2>the one entity that actually, at least in theory, can

0:29:42.160 --> 0:29:43.560
<v Speaker 2>print as much money as possible.

0:29:43.840 --> 0:29:47.720
<v Speaker 6>Right, that's the you know, the Sarah Friar's accidental foot

0:29:47.720 --> 0:29:49.040
<v Speaker 6>in mouth the thing earlier in the week.

0:29:49.240 --> 0:29:49.880
<v Speaker 5>But that's right.

0:29:49.920 --> 0:29:52.120
<v Speaker 6>But that's again goes back to my original point about

0:29:52.120 --> 0:29:56.560
<v Speaker 6>what makes this bubble unusual. It's this element that not

0:29:56.600 --> 0:29:58.760
<v Speaker 6>only is there a kind of bagstock, but there's actually

0:29:59.000 --> 0:30:01.960
<v Speaker 6>a notion of wrapping in the flag. We have to

0:30:02.000 --> 0:30:04.520
<v Speaker 6>win this competition, we have to do what it takes.

0:30:04.560 --> 0:30:08.080
<v Speaker 6>This is existential. It's US versus China, and it's not

0:30:08.160 --> 0:30:10.600
<v Speaker 6>just the US doing this. I was talking to some

0:30:10.640 --> 0:30:13.840
<v Speaker 6>Canadian policymakers just earlier this morning, exact same thing going

0:30:13.840 --> 0:30:15.800
<v Speaker 6>on there. We have to build a domestic in the

0:30:15.880 --> 0:30:18.360
<v Speaker 6>same thing in the UK, same thing in Germany. And

0:30:18.440 --> 0:30:21.520
<v Speaker 6>so there's this idea around the world that sovereign ai

0:30:21.640 --> 0:30:24.720
<v Speaker 6>is something that's incredibly important. So this this government backstop

0:30:24.760 --> 0:30:27.240
<v Speaker 6>isn't just mythic, it's it's global. It's this idea that

0:30:27.280 --> 0:30:28.960
<v Speaker 6>we all have to win, we all have to win,

0:30:28.960 --> 0:30:32.520
<v Speaker 6>which obviously can't happen, but that the government's playing a

0:30:32.600 --> 0:30:34.120
<v Speaker 6>role and that that be can trace this kind of

0:30:34.160 --> 0:30:35.680
<v Speaker 6>limitless course of capital.

0:30:35.720 --> 0:30:38.000
<v Speaker 2>You know. So one of the things that's going on,

0:30:38.200 --> 0:30:40.480
<v Speaker 2>and maybe it's part of the same the sort of

0:30:40.640 --> 0:30:44.880
<v Speaker 2>maximalist strategy mentioned Anthropic wants to get into data centers,

0:30:44.920 --> 0:30:48.800
<v Speaker 2>so everyone's sort of looking at how they can expand vertically.

0:30:48.840 --> 0:30:50.920
<v Speaker 2>Can I own the data centers? I think? You know,

0:30:51.000 --> 0:30:53.760
<v Speaker 2>Sam Altman has talked about owning chips or owning a

0:30:53.760 --> 0:30:57.240
<v Speaker 2>semiconductor fab at some point, like maybe that'll be part

0:30:57.240 --> 0:30:59.960
<v Speaker 2>of the story. Who knows. There's one thing that I don't.

0:31:00.040 --> 0:31:01.920
<v Speaker 2>I'm sort of curious. I'd love to have your take

0:31:02.000 --> 0:31:05.760
<v Speaker 2>on there was. At the end of September, Meta announced

0:31:05.760 --> 0:31:08.280
<v Speaker 2>the deal to buy Compute from core Weave, one of

0:31:08.280 --> 0:31:12.280
<v Speaker 2>these neo clouds. I don't totally get that because Meta

0:31:12.320 --> 0:31:14.440
<v Speaker 2>has its own data centers, et cetera. Do you have

0:31:14.480 --> 0:31:18.960
<v Speaker 2>some intuitive sense about what an established hyperscaler needs a

0:31:19.040 --> 0:31:22.520
<v Speaker 2>neo cloud for in this arrangement, what core Weave can

0:31:22.560 --> 0:31:25.680
<v Speaker 2>supply that Meta can't build on its own or buy

0:31:25.680 --> 0:31:26.160
<v Speaker 2>on its own.

0:31:26.840 --> 0:31:30.440
<v Speaker 5>Nothing.

0:31:29.480 --> 0:31:32.840
<v Speaker 6>So here's what's going on. This is what's going on

0:31:32.960 --> 0:31:36.000
<v Speaker 6>is that there's this form of hoarding going on. So

0:31:36.800 --> 0:31:39.640
<v Speaker 6>what's happening is is people saying, you have capacity, I

0:31:39.680 --> 0:31:40.600
<v Speaker 6>can lock that up.

0:31:40.760 --> 0:31:41.640
<v Speaker 5>I'll lock that up.

0:31:42.000 --> 0:31:44.000
<v Speaker 6>And because I can't lock it up yet by building

0:31:44.000 --> 0:31:45.960
<v Speaker 6>a data center quickly enough, I'll lock it up in

0:31:45.960 --> 0:31:49.400
<v Speaker 6>the marketplace. So once you start thinking of compute as

0:31:49.400 --> 0:31:52.920
<v Speaker 6>a hordable commodity, and what people are doing is trying

0:31:52.960 --> 0:31:56.479
<v Speaker 6>to hoard it, control it before someone else can do it,

0:31:56.480 --> 0:31:59.120
<v Speaker 6>because until they bring on their own access capacity. That's

0:31:59.160 --> 0:32:01.560
<v Speaker 6>really what's going on in a lot of these transactions.

0:32:01.600 --> 0:32:03.720
<v Speaker 6>This is a way of making sure that I may

0:32:03.720 --> 0:32:05.800
<v Speaker 6>not need this but you sure can have it. And

0:32:05.880 --> 0:32:08.400
<v Speaker 6>so there's there's an element of compute hoarding going on

0:32:08.560 --> 0:32:12.080
<v Speaker 6>across the map because of you know, this backlog and building.

0:32:11.880 --> 0:32:13.600
<v Speaker 5>Data centers that may or may not ever get built.

0:32:13.640 --> 0:32:14.280
<v Speaker 5>So that's the answer.

0:32:14.360 --> 0:32:16.160
<v Speaker 6>The answer isn't that they care at all about whether

0:32:16.200 --> 0:32:19.120
<v Speaker 6>or not they can run giant workloads on any particular

0:32:19.280 --> 0:32:22.600
<v Speaker 6>neo clouds provider. It's the idea of hoarding capacity and

0:32:22.640 --> 0:32:24.840
<v Speaker 6>making sure that no one else can have it, like

0:32:24.960 --> 0:32:27.120
<v Speaker 6>trying to have like the Hunt Brothers and the getting

0:32:27.120 --> 0:32:28.360
<v Speaker 6>a corner on the silver market.

0:32:29.320 --> 0:32:31.040
<v Speaker 3>You know, I want to go back to China because

0:32:31.080 --> 0:32:33.840
<v Speaker 3>it is true that the US and China seem locked

0:32:33.880 --> 0:32:37.320
<v Speaker 3>in this existential race for AI supremacy, but they seem

0:32:37.360 --> 0:32:39.680
<v Speaker 3>to be taking very different approaches to it. And in

0:32:39.720 --> 0:32:42.240
<v Speaker 3>the US, it's all about spending as much money as

0:32:42.280 --> 0:32:45.720
<v Speaker 3>you can developing these you know, state of the art,

0:32:46.000 --> 0:32:50.040
<v Speaker 3>mostly closed source models, whereas in China it seems to

0:32:50.080 --> 0:32:53.880
<v Speaker 3>be much more about rapid adoption and creating open source

0:32:53.920 --> 0:32:56.800
<v Speaker 3>models that just get out into the market much faster

0:32:57.400 --> 0:33:01.960
<v Speaker 3>and much more cheaply. And so I'm curious, like, which

0:33:02.000 --> 0:33:04.520
<v Speaker 3>of those approaches do you think it's going to win?

0:33:04.560 --> 0:33:04.840
<v Speaker 5>Here.

0:33:05.600 --> 0:33:09.920
<v Speaker 6>Yeah, so that's a really good question. So I think

0:33:10.280 --> 0:33:11.920
<v Speaker 6>it's going to be something closer to.

0:33:11.880 --> 0:33:14.120
<v Speaker 5>The Chinese approach, but not for the reasons they expect.

0:33:14.440 --> 0:33:17.840
<v Speaker 6>So the reason is because, so what, let's I'll reframe

0:33:17.840 --> 0:33:19.800
<v Speaker 6>what the Chinese are doing slightly, so I'll say that

0:33:19.840 --> 0:33:21.800
<v Speaker 6>instead of it just being a sort of an example

0:33:21.840 --> 0:33:24.160
<v Speaker 6>of open source, I don't think that's right. The right

0:33:24.200 --> 0:33:25.840
<v Speaker 6>way to think about it is they're using this kind

0:33:25.880 --> 0:33:29.000
<v Speaker 6>of distillation approach increasingly where there's kind of a you

0:33:29.040 --> 0:33:30.920
<v Speaker 6>think about it like, Okay, I'm a sales manager. I

0:33:30.920 --> 0:33:32.760
<v Speaker 6>don't want to train all my salespeople. I'm going to

0:33:32.760 --> 0:33:33.760
<v Speaker 6>train this dude.

0:33:33.640 --> 0:33:35.840
<v Speaker 5>And they're going to train all the sales But that's distillation, right.

0:33:35.880 --> 0:33:38.560
<v Speaker 6>You train the trainer, I train somebody who trains something else,

0:33:38.600 --> 0:33:41.360
<v Speaker 6>and something else in this case are these smaller models.

0:33:41.360 --> 0:33:44.960
<v Speaker 6>So that approach of kind of training the trainer really

0:33:44.960 --> 0:33:47.880
<v Speaker 6>speeds up the process of creating new models because I

0:33:47.960 --> 0:33:50.880
<v Speaker 6>distill them, I train them out of out of other

0:33:50.960 --> 0:33:54.200
<v Speaker 6>models that are really compute intensive, like anthropics or opening

0:33:54.200 --> 0:33:56.520
<v Speaker 6>eyes or whoever else is right. So the notion is,

0:33:57.440 --> 0:34:00.120
<v Speaker 6>so is there are huge efficiency gains to be had

0:34:00.200 --> 0:34:03.440
<v Speaker 6>in training and the Chinese are showing the huge efficiency

0:34:03.480 --> 0:34:05.520
<v Speaker 6>gains to be had, and the one way to think

0:34:05.560 --> 0:34:09.600
<v Speaker 6>about it is that the transformer models that underlie large

0:34:09.640 --> 0:34:12.920
<v Speaker 6>language models that are so computationally intensive, went from the

0:34:13.040 --> 0:34:16.400
<v Speaker 6>lab to the market faster than any product in technology history.

0:34:16.680 --> 0:34:19.560
<v Speaker 6>So they're absolutely bloated and full of crap. Right, So

0:34:19.680 --> 0:34:22.719
<v Speaker 6>these things are wildly inefficient. There's all kinds of other

0:34:22.760 --> 0:34:25.319
<v Speaker 6>ways to do the same sorts of things, one of

0:34:25.360 --> 0:34:27.480
<v Speaker 6>which is distillations. So what you're really seeing is a

0:34:27.560 --> 0:34:30.879
<v Speaker 6>kind of an accident of history that we've came down.

0:34:30.960 --> 0:34:33.839
<v Speaker 6>The US came down this path that led directly out

0:34:33.840 --> 0:34:36.880
<v Speaker 6>of the original transformer paper in twenty seventeen, and the

0:34:36.920 --> 0:34:38.319
<v Speaker 6>Chinese have said, yeah, we're not going to be able

0:34:38.320 --> 0:34:39.200
<v Speaker 6>to do that for a bunch.

0:34:39.000 --> 0:34:41.200
<v Speaker 5>Of different reasons. But we don't have to do.

0:34:41.120 --> 0:34:43.520
<v Speaker 6>That because I can take this approach of distillation, which

0:34:43.600 --> 0:34:44.640
<v Speaker 6>lets us get you.

0:34:44.719 --> 0:34:46.320
<v Speaker 5>If you look at Kimmy, this sort.

0:34:46.160 --> 0:34:49.520
<v Speaker 6>Of relatively recent open source these things are actually really

0:34:49.520 --> 0:34:52.479
<v Speaker 6>effective in benchmark very well, and it's not surprising because

0:34:52.480 --> 0:34:54.440
<v Speaker 6>they've been trained by really good trainers, which.

0:34:54.280 --> 0:34:55.680
<v Speaker 5>Is to say some of the other models that are

0:34:55.719 --> 0:34:56.200
<v Speaker 5>out there.

0:34:56.640 --> 0:34:59.520
<v Speaker 6>But these are about efficiency games, which should then ask

0:34:59.600 --> 0:35:02.279
<v Speaker 6>the question is whoa wait a minute, if there's all

0:35:02.280 --> 0:35:05.200
<v Speaker 6>these efficiency gains ahead from training, and training is seventy

0:35:05.200 --> 0:35:08.160
<v Speaker 6>percent of the workload on data centers? Hang on a second,

0:35:08.239 --> 0:35:11.640
<v Speaker 6>aren't we completely misforecasting the likely future the arc of

0:35:11.680 --> 0:35:14.640
<v Speaker 6>demand for compute And the answer is yes. And this

0:35:14.760 --> 0:35:17.840
<v Speaker 6>is rather than looking at it as an example of

0:35:17.840 --> 0:35:20.120
<v Speaker 6>why China is doing something better for worse, another way

0:35:20.120 --> 0:35:23.320
<v Speaker 6>of looking at is saying, just just refuted the approach

0:35:23.360 --> 0:35:26.239
<v Speaker 6>that we're taking to training altogether, because it shows how

0:35:26.280 --> 0:35:30.000
<v Speaker 6>blowdd and inefficient the approach we're taking is, and yet

0:35:30.040 --> 0:35:32.839
<v Speaker 6>we're projecting on that basis what future data center needs are.

0:35:33.280 --> 0:35:35.520
<v Speaker 2>Part of the question, it seems to me, and this

0:35:35.560 --> 0:35:38.360
<v Speaker 2>is where it gets a little bit philosophical, is what

0:35:38.520 --> 0:35:42.440
<v Speaker 2>do these AI companies think they're building? Because one theory

0:35:42.520 --> 0:35:46.200
<v Speaker 2>is like, well, maybe they're building business tools, right, maybe

0:35:46.239 --> 0:35:48.879
<v Speaker 2>they're building business tools of various sorts. And if they're

0:35:48.920 --> 0:35:52.279
<v Speaker 2>building business tools of various sorts, that implies the possibility

0:35:52.280 --> 0:35:55.200
<v Speaker 2>that eventually they get good enough. This does the job right,

0:35:55.320 --> 0:35:59.000
<v Speaker 2>This makes it easier for this website. You can use

0:35:59.000 --> 0:36:02.760
<v Speaker 2>an agent to book your travel, and the technology works,

0:36:02.760 --> 0:36:04.480
<v Speaker 2>and we don't have to keep building it because we

0:36:04.520 --> 0:36:06.839
<v Speaker 2>got to the point where it works. And then there

0:36:06.880 --> 0:36:09.239
<v Speaker 2>is this other question of like, well, maybe they want

0:36:09.280 --> 0:36:12.520
<v Speaker 2>to build something called AGI or ASI that's like so

0:36:12.760 --> 0:36:16.040
<v Speaker 2>sci fi et cetera, in which case you could never

0:36:16.080 --> 0:36:19.040
<v Speaker 2>get enough, or simply having built the thing that allows

0:36:19.080 --> 0:36:21.480
<v Speaker 2>you to book your travel or book a dinner reservation

0:36:21.800 --> 0:36:25.320
<v Speaker 2>or translated text or whatever, that's not nearly enough. You

0:36:25.400 --> 0:36:28.040
<v Speaker 2>you hear different things. But what do you think the

0:36:28.120 --> 0:36:31.080
<v Speaker 2>builders at the cutting edge of these labs are going for?

0:36:31.280 --> 0:36:33.840
<v Speaker 2>Is it really the sort of sci fi building god

0:36:33.920 --> 0:36:37.320
<v Speaker 2>cliche or do they want to build profitable business tools?

0:36:38.680 --> 0:36:39.719
<v Speaker 5>So it's the first.

0:36:39.440 --> 0:36:41.440
<v Speaker 6>Thing until you challenge them, and then it's the second.

0:36:41.560 --> 0:36:44.960
<v Speaker 6>So what happens is if you have the conversation internally,

0:36:44.960 --> 0:36:47.520
<v Speaker 6>they'll say, yeah, no, no, no, we're building this really effective

0:36:47.560 --> 0:36:51.120
<v Speaker 6>productivity enhancing tools that'll be used across a host of businesses,

0:36:51.160 --> 0:36:52.600
<v Speaker 6>and these all sounds really good.

0:36:52.640 --> 0:36:54.840
<v Speaker 5>But then when you walk through some of the math.

0:36:54.680 --> 0:36:58.160
<v Speaker 6>In terms of justifying the ROI on the spend, all

0:36:58.200 --> 0:37:00.000
<v Speaker 6>of a sudden, then it turns into what I call faith.

0:37:00.280 --> 0:37:02.960
<v Speaker 5>Argumentation about AGI, and they.

0:37:02.800 --> 0:37:06.080
<v Speaker 6>Say it's like the greatest call option ever, Like what

0:37:06.120 --> 0:37:08.120
<v Speaker 6>would you pay for a call option that could get

0:37:08.160 --> 0:37:10.520
<v Speaker 6>you anything, and it's like, well, wait a minute, this

0:37:10.560 --> 0:37:13.000
<v Speaker 6>isn't a way of justifying any particular expenditure.

0:37:13.040 --> 0:37:14.520
<v Speaker 5>This is just faith based argumentation.

0:37:14.680 --> 0:37:17.960
<v Speaker 6>We're saying, you know, with the uber call option for anything,

0:37:18.000 --> 0:37:19.600
<v Speaker 6>you should be willing to pay anything for it. And

0:37:19.640 --> 0:37:22.520
<v Speaker 6>obviously that that kind of justification doesn't get you anywhere.

0:37:22.520 --> 0:37:26.560
<v Speaker 6>So in house they'll arm wave a lot about these

0:37:26.560 --> 0:37:27.840
<v Speaker 6>different models that will emerge.

0:37:27.840 --> 0:37:28.319
<v Speaker 5>Who knows.

0:37:28.360 --> 0:37:29.839
<v Speaker 6>I had someone at inn Vidia tell me the other

0:37:29.920 --> 0:37:31.760
<v Speaker 6>day that we really are just waiting for the uber

0:37:31.800 --> 0:37:33.440
<v Speaker 6>of ai to come along and show.

0:37:33.320 --> 0:37:37.040
<v Speaker 5>Us the future. And I'm like, okay, so that's it's

0:37:37.080 --> 0:37:38.120
<v Speaker 5>not an answer, right.

0:37:38.239 --> 0:37:42.440
<v Speaker 2>So because in theory, if you're building a business productivity tool,

0:37:42.840 --> 0:37:46.680
<v Speaker 2>then eventually you could solve your unit economics problem. Right,

0:37:46.760 --> 0:37:49.080
<v Speaker 2>If you're just trying to build a really great business opportunity,

0:37:49.120 --> 0:37:50.360
<v Speaker 2>then as simply you know what, we don't have to

0:37:50.400 --> 0:37:53.200
<v Speaker 2>build anymore. It works, and then the cash flow just

0:37:53.200 --> 0:37:57.200
<v Speaker 2>starts pouring in and the cost per token goes down can.

0:37:57.040 --> 0:37:59.280
<v Speaker 6>And there's a bunch of that already happening. It's really interesting.

0:37:59.400 --> 0:38:02.440
<v Speaker 6>But what's incre thing happening is the problems they're solving

0:38:02.440 --> 0:38:05.600
<v Speaker 6>are really mundane, and so it's things like I'm trying

0:38:05.600 --> 0:38:07.960
<v Speaker 6>to onboard a bunch of new suppliers right now that

0:38:08.000 --> 0:38:10.480
<v Speaker 6>people have weird zip codes and they sometimes don't match up.

0:38:10.520 --> 0:38:12.520
<v Speaker 6>I have a dude in the back who fixes that.

0:38:12.840 --> 0:38:14.560
<v Speaker 6>I'd rather have someone who could do it faster so

0:38:14.640 --> 0:38:17.360
<v Speaker 6>they could onboard a lot more suppliers. Oh, it turns

0:38:17.440 --> 0:38:19.759
<v Speaker 6>out these small language models are really good at that.

0:38:19.800 --> 0:38:23.200
<v Speaker 6>These micro models like IBM's granted and whatever else, But

0:38:23.320 --> 0:38:27.960
<v Speaker 6>those things require a fraction of the training, are very cheap,

0:38:28.120 --> 0:38:31.520
<v Speaker 6>are not going to justify anywhere near the economics needed

0:38:31.600 --> 0:38:34.439
<v Speaker 6>to pay for the current spend. And yet those things

0:38:34.480 --> 0:38:37.360
<v Speaker 6>are almost likely very likely the future because it'll be

0:38:37.400 --> 0:38:40.920
<v Speaker 6>profitably get token used from micro models often hosted internally

0:38:41.440 --> 0:38:45.040
<v Speaker 6>to do really mundane background tasks, not very glamorous onboarding

0:38:45.080 --> 0:38:49.640
<v Speaker 6>new suppliers, matching records, great stuff, just not really very exciting.

0:38:49.680 --> 0:38:52.399
<v Speaker 6>But large language models are amazing at it, and small

0:38:52.480 --> 0:38:54.719
<v Speaker 6>language models are amazing at it, and almost.

0:38:54.440 --> 0:38:58.839
<v Speaker 3>Free and writing songs, right, Joe, I'm actually I'm still

0:38:58.840 --> 0:39:02.480
<v Speaker 3>annoyed that AI is like getting into art and music

0:39:02.520 --> 0:39:05.480
<v Speaker 3>writing and all the fun stuff versus the stuff that

0:39:05.520 --> 0:39:08.680
<v Speaker 3>I don't want to do like folding launchy to your classic.

0:39:08.320 --> 0:39:10.560
<v Speaker 5>Example or matching customer records. Are that?

0:39:11.200 --> 0:39:14.120
<v Speaker 3>So, going back to the beginning of this conversation when

0:39:14.160 --> 0:39:16.640
<v Speaker 3>we were just talking about the scale of AI investment

0:39:16.719 --> 0:39:19.920
<v Speaker 3>and its impact on the US economy, I'm pretty sure

0:39:20.080 --> 0:39:23.520
<v Speaker 3>you are one of the ones who's described AI capex

0:39:23.600 --> 0:39:27.560
<v Speaker 3>as like a private sector stimulus program for the US economy.

0:39:28.040 --> 0:39:31.840
<v Speaker 3>What are the actual consequences, either positive or negative, of

0:39:31.960 --> 0:39:36.400
<v Speaker 3>having this massive private sector spend in the economy versus

0:39:36.640 --> 0:39:39.720
<v Speaker 3>something I guess more typical, which would be a government

0:39:39.760 --> 0:39:43.680
<v Speaker 3>stimulus or maybe growth driven by consumer spending or something

0:39:43.719 --> 0:39:44.000
<v Speaker 3>like that.

0:39:44.600 --> 0:39:48.000
<v Speaker 6>Yeah, So to an orthodox economist, the old line is like,

0:39:48.040 --> 0:39:49.879
<v Speaker 6>it really doesn't matter what we pay people to do as.

0:39:49.840 --> 0:39:51.840
<v Speaker 5>Long as we pay them, right. It's the idea of I.

0:39:51.840 --> 0:39:53.560
<v Speaker 6>Should be, I should be you should be willing to

0:39:53.600 --> 0:39:55.920
<v Speaker 6>pay people to dig holes in the ground and people.

0:39:55.640 --> 0:39:56.960
<v Speaker 5>Over there to fill the holes back in.

0:39:57.040 --> 0:39:59.439
<v Speaker 6>Again, it really doesn't matter as long as the money

0:39:59.440 --> 0:40:03.200
<v Speaker 6>he's out there circulation, right, It's just it's all just stimulus.

0:40:03.280 --> 0:40:06.920
<v Speaker 5>Right. So, to that way of thinking, it doesn't matter

0:40:07.320 --> 0:40:09.560
<v Speaker 5>because the money's all finding its way back into the economy.

0:40:09.600 --> 0:40:12.680
<v Speaker 6>But I think that's obviously hugely misleading, because in this context,

0:40:12.719 --> 0:40:15.760
<v Speaker 6>these are investments created with an expectation of a return.

0:40:16.239 --> 0:40:19.160
<v Speaker 6>If they can't, then that flows backwards into all the

0:40:19.239 --> 0:40:21.360
<v Speaker 6>entities that are built on that basis, whether it's private

0:40:21.400 --> 0:40:24.440
<v Speaker 6>credit firms and their returns, the S and P five hundred,

0:40:24.440 --> 0:40:26.160
<v Speaker 6>what is it like? Thirty five percent now is AI

0:40:26.239 --> 0:40:30.160
<v Speaker 6>related mag seven meg ten whatever? Fifty percent now the

0:40:30.239 --> 0:40:32.680
<v Speaker 6>last two years return. So this is a massive negative

0:40:32.719 --> 0:40:34.919
<v Speaker 6>wealth effect when you unwind it, not just in terms

0:40:34.920 --> 0:40:36.640
<v Speaker 6>of the direct spending, but in terms of the wealth

0:40:36.640 --> 0:40:39.480
<v Speaker 6>effect with respect to what people's holdings are. So this

0:40:39.560 --> 0:40:41.120
<v Speaker 6>is not as simple as saying this has just been

0:40:41.160 --> 0:40:42.440
<v Speaker 6>a wonderful stimulus program.

0:40:42.560 --> 0:40:44.880
<v Speaker 5>We're paying people to dig holes and filling them back in. Again,

0:40:45.320 --> 0:40:45.719
<v Speaker 5>this is.

0:40:45.680 --> 0:40:48.520
<v Speaker 6>A wasting asset on something that's likely to be produced

0:40:48.560 --> 0:40:51.279
<v Speaker 6>in quantities that we can never earn an economic return from,

0:40:51.360 --> 0:40:55.439
<v Speaker 6>in part because of wildly flawed assumptions and projections about

0:40:55.440 --> 0:40:58.240
<v Speaker 6>the future of demand for those units. And so that's

0:40:58.280 --> 0:41:00.560
<v Speaker 6>that's the deep structural problem, and can get into this

0:41:00.600 --> 0:41:03.320
<v Speaker 6>whole question of like, well it was just private equity

0:41:03.360 --> 0:41:06.560
<v Speaker 6>guys get hurt, you know, cares Screw those guys, right,

0:41:07.040 --> 0:41:08.879
<v Speaker 6>And it's not, of course, because as we just talked

0:41:08.880 --> 0:41:10.760
<v Speaker 6>about it, it's it's in equity funds.

0:41:10.520 --> 0:41:12.040
<v Speaker 2>It's firefighters and teachers money.

0:41:12.120 --> 0:41:14.720
<v Speaker 6>Yeah, and it's in reeds now look at the larger

0:41:14.760 --> 0:41:16.840
<v Speaker 6>holdings and reads now increasingly our data centers.

0:41:16.920 --> 0:41:17.759
<v Speaker 5>Yeah. And it's even in.

0:41:17.760 --> 0:41:20.000
<v Speaker 6>Sort of sneaky backdoor ways like we're seeing increasing I

0:41:20.000 --> 0:41:21.880
<v Speaker 6>don't if you guys are familiar with these new interval funds.

0:41:21.880 --> 0:41:23.520
<v Speaker 5>They're appearing there all over.

0:41:23.400 --> 0:41:26.080
<v Speaker 2>Now, Paul Kadrowski, we could I have a million more

0:41:26.160 --> 0:41:28.359
<v Speaker 2>questions you could ask you, But much like the race

0:41:28.360 --> 0:41:31.160
<v Speaker 2>towards a GI itself, that would imply that we'll ever

0:41:31.320 --> 0:41:34.200
<v Speaker 2>actually get to the end of this conversation. So how

0:41:34.239 --> 0:41:37.239
<v Speaker 2>about we wrap here and then just plan on, you know,

0:41:37.360 --> 0:41:41.160
<v Speaker 2>revisiting the com six months, maybe three years. We just

0:41:41.239 --> 0:41:44.000
<v Speaker 2>keep revisiting down the line where we are in the cycle.

0:41:44.080 --> 0:41:45.960
<v Speaker 5>As long as we haven't been turned into paper clips.

0:41:45.960 --> 0:41:46.279
<v Speaker 1>I'm good.

0:41:46.880 --> 0:41:49.920
<v Speaker 2>Yeah, that's the no one talks about the nightmare. I

0:41:49.960 --> 0:41:52.680
<v Speaker 2>feel like that was a no one talks about the

0:41:52.719 --> 0:41:56.480
<v Speaker 2>old school paper clip maximizer stuff. Everyone's onto more esoteric fears.

0:41:56.520 --> 0:41:58.319
<v Speaker 5>I know people have moved on. We need to worry.

0:41:58.480 --> 0:42:01.560
<v Speaker 3>Does anyone wait, did anyone ever try to securitize Clippy?

0:42:01.680 --> 0:42:03.200
<v Speaker 5>They didn't, right, I don't think so.

0:42:03.440 --> 0:42:05.920
<v Speaker 2>No, thanks Paul.

0:42:06.040 --> 0:42:07.720
<v Speaker 6>Hey, thanks guys.

0:42:19.440 --> 0:42:21.319
<v Speaker 2>Paul's so good. That's a lot of fun. He's so good.

0:42:21.400 --> 0:42:24.440
<v Speaker 3>Here's my highest form of praise for an odd thought's guest.

0:42:24.640 --> 0:42:26.880
<v Speaker 3>I am going to go back and read that transcript

0:42:26.920 --> 0:42:27.839
<v Speaker 3>from beginning to end.

0:42:27.880 --> 0:42:30.600
<v Speaker 2>It is a very good that is a very good

0:42:30.840 --> 0:42:32.920
<v Speaker 2>practice to do. You're not going to listen to it.

0:42:33.800 --> 0:42:34.520
<v Speaker 5>I'm going to read it.

0:42:34.760 --> 0:42:36.360
<v Speaker 2>Yeah, I can read it. I can't listen to it.

0:42:36.520 --> 0:42:37.520
<v Speaker 3>I just listened to it.

0:42:37.600 --> 0:42:39.200
<v Speaker 2>I can need to read it. I can't listen to

0:42:39.280 --> 0:42:41.640
<v Speaker 2>our episodes. No, I just you know, I think there's

0:42:41.680 --> 0:42:43.480
<v Speaker 2>a lot, there's a lot more to do on all

0:42:43.520 --> 0:42:47.000
<v Speaker 2>this topic, but the financing in particular and some of

0:42:47.040 --> 0:42:52.239
<v Speaker 2>these arrangements. It's just incredible how the speed with which

0:42:52.719 --> 0:42:55.680
<v Speaker 2>I guess I would say the financing has gotten interesting.

0:42:55.840 --> 0:42:57.360
<v Speaker 2>Do you know what I'm saying that? I think like

0:42:57.400 --> 0:43:00.880
<v Speaker 2>a data center project ten years ago, Microsoft AWS thing

0:43:01.160 --> 0:43:05.120
<v Speaker 2>just seemed like a fairly straightforward is probably more complicated

0:43:05.160 --> 0:43:07.880
<v Speaker 2>than I appreciate at the time, but basically straightforward. We

0:43:07.920 --> 0:43:09.600
<v Speaker 2>make this money and part of it is going to

0:43:09.600 --> 0:43:13.160
<v Speaker 2>go to building more data centers to you know, serve

0:43:14.000 --> 0:43:16.759
<v Speaker 2>you know, Amazon Prime Streaming or whatever it is, or

0:43:16.800 --> 0:43:19.080
<v Speaker 2>some client thing or whatever. And then the degree of

0:43:19.120 --> 0:43:23.960
<v Speaker 2>complexity with these SPVs and rollover risk and depreciation schedules

0:43:24.000 --> 0:43:27.480
<v Speaker 2>and changing of who it's gotten very interesting, very fast.

0:43:27.760 --> 0:43:31.480
<v Speaker 3>Life Uh finds a way life finds. Yeah, that was

0:43:31.520 --> 0:43:35.560
<v Speaker 3>my terrible, terrible impression. I think that's absolutely right. One

0:43:35.560 --> 0:43:37.440
<v Speaker 3>thing I would say is the fact that a lot

0:43:37.480 --> 0:43:41.040
<v Speaker 3>of these big, supposedly cash rich companies are doing this

0:43:41.120 --> 0:43:44.399
<v Speaker 3>through SPVs that effectively preserve their balance sheet and their

0:43:44.440 --> 0:43:46.160
<v Speaker 3>cash flow so they can do something else with it.

0:43:46.239 --> 0:43:49.960
<v Speaker 3>I mean a lot of companies use SPVs. Sure, yeah,

0:43:50.480 --> 0:43:54.560
<v Speaker 3>But I do think it says something about the scale, yes, right,

0:43:54.640 --> 0:43:57.399
<v Speaker 3>Like there's a scale problem here where if all you're

0:43:57.480 --> 0:44:01.120
<v Speaker 3>spending was appearing on balance sheet investment might think very

0:44:01.200 --> 0:44:04.399
<v Speaker 3>very differently about your company. And then the other thing

0:44:04.400 --> 0:44:07.600
<v Speaker 3>I would say is I still think the comparing contrast

0:44:07.640 --> 0:44:11.080
<v Speaker 3>between the US and China and their approaches to AI.

0:44:11.800 --> 0:44:13.480
<v Speaker 3>You know, both of them, I think would agree that

0:44:13.520 --> 0:44:16.160
<v Speaker 3>this is an existential problem of some sort or an

0:44:16.200 --> 0:44:21.839
<v Speaker 3>existential competition. But they're following very different paths, and it

0:44:21.880 --> 0:44:24.279
<v Speaker 3>does seem to me like the arc of history kind

0:44:24.320 --> 0:44:26.960
<v Speaker 3>of leans towards stuff becoming cheaper.

0:44:28.160 --> 0:44:30.520
<v Speaker 2>The artifactory bend towards China.

0:44:31.400 --> 0:44:34.200
<v Speaker 3>Well that's that too, but it bends towards you know,

0:44:34.560 --> 0:44:36.960
<v Speaker 3>people generally want the cheaper thing, and they want the

0:44:36.960 --> 0:44:40.520
<v Speaker 3>thing that's like available now, and China seems to be

0:44:40.640 --> 0:44:41.319
<v Speaker 3>going for that.

0:44:41.440 --> 0:44:43.960
<v Speaker 2>The counter argument is that if you're going to use

0:44:44.000 --> 0:44:47.640
<v Speaker 2>an open source model for some purposes, you have to

0:44:47.640 --> 0:44:50.200
<v Speaker 2>supply your own electricity, right, you have to supply your

0:44:50.239 --> 0:44:52.279
<v Speaker 2>own inference. You've got to host on your service, like,

0:44:52.280 --> 0:44:56.239
<v Speaker 2>you still run into some constraints, and so rather than

0:44:56.320 --> 0:45:00.160
<v Speaker 2>having it beyond whatever whoever else is data center, you

0:45:00.160 --> 0:45:01.800
<v Speaker 2>gotta find a way to run it yourself.

0:45:01.880 --> 0:45:05.800
<v Speaker 3>Yeah, okay, but China has a leg an electricity.

0:45:05.080 --> 0:45:07.319
<v Speaker 2>Which was the point that Jensen Wong made. I mean,

0:45:07.360 --> 0:45:09.880
<v Speaker 2>part of the reason, like there's so much talk about

0:45:09.880 --> 0:45:13.400
<v Speaker 2>this these days right now, is that the industry insiders

0:45:13.400 --> 0:45:15.319
<v Speaker 2>are saying a bunch of weird things. Paul mentioned the

0:45:15.320 --> 0:45:18.120
<v Speaker 2>Sarah Friar comment yea, and she she sort of had

0:45:18.160 --> 0:45:20.640
<v Speaker 2>to walk back, but then she said there was the

0:45:20.680 --> 0:45:22.680
<v Speaker 2>Sam Altman thing where he was asked how are you

0:45:22.719 --> 0:45:24.040
<v Speaker 2>going to pay for all this? And he said, look,

0:45:24.040 --> 0:45:26.560
<v Speaker 2>you want to sell your shares or not, which is

0:45:26.600 --> 0:45:28.000
<v Speaker 2>like the interviewer probably thought he.

0:45:27.960 --> 0:45:29.160
<v Speaker 3>Was little defensive.

0:45:29.360 --> 0:45:32.880
<v Speaker 2>Obviously, Jensen Wong talking at a recently about how China

0:45:32.960 --> 0:45:35.480
<v Speaker 2>was going to win. Maybe he was saying that because

0:45:35.960 --> 0:45:38.759
<v Speaker 2>he wanted to catalyze more action on solving some of

0:45:38.800 --> 0:45:41.600
<v Speaker 2>the electricity problems in the US. But you know, the

0:45:41.800 --> 0:45:44.920
<v Speaker 2>very people at the center of this are saying things

0:45:45.080 --> 0:45:48.960
<v Speaker 2>right now that you know. What's interesting too, is you

0:45:49.000 --> 0:45:52.279
<v Speaker 2>know this bullwhip phenomenon everyone as Paul described it, he

0:45:52.280 --> 0:45:54.600
<v Speaker 2>didn't use the word bullwhip, but when everyone is trying

0:45:54.600 --> 0:45:56.640
<v Speaker 2>to get their hands on the same gear, you gotta

0:45:56.680 --> 0:45:59.160
<v Speaker 2>wonder how sustaint what's the other side of a bullwep

0:45:59.200 --> 0:46:01.360
<v Speaker 2>could look like? We just got to do more episodes

0:46:01.360 --> 0:46:01.520
<v Speaker 2>on this.

0:46:01.719 --> 0:46:03.680
<v Speaker 3>Yeah, we have to. Shall we leave it there for now?

0:46:03.760 --> 0:46:04.759
<v Speaker 2>Let's leave it there all right?

0:46:04.800 --> 0:46:07.439
<v Speaker 3>This has been another episode of the Audthots podcast. I'm

0:46:07.440 --> 0:46:10.359
<v Speaker 3>Tracy Alloway. You can follow me at Tracy Alloway and.

0:46:10.320 --> 0:46:13.000
<v Speaker 2>I'm Jill Wisenthal. You can follow me at The Stalwart.

0:46:13.200 --> 0:46:16.440
<v Speaker 2>Check out Paul Kadrowski's writing at Paul Kadrowski dot com,

0:46:16.480 --> 0:46:19.719
<v Speaker 2>follow our producers Carmen Rodriguez at Carman Arman, dash Ol

0:46:19.719 --> 0:46:22.759
<v Speaker 2>Bennett at dashbod and Kilbrooks at Kilbrooks. And for more

0:46:22.800 --> 0:46:25.279
<v Speaker 2>odd Lots content, go to Bloomberg dot com slash odd

0:46:25.360 --> 0:46:27.840
<v Speaker 2>Lots with the daily newsletter and all of our episodes,

0:46:28.040 --> 0:46:29.960
<v Speaker 2>and you can shout about all of these topics twenty

0:46:29.960 --> 0:46:33.160
<v Speaker 2>four to seven in our discord Discord dot gg slash

0:46:33.160 --> 0:46:33.680
<v Speaker 2>od Lots.

0:46:33.880 --> 0:46:36.000
<v Speaker 3>And if you enjoy odd Lots, if you like it

0:46:36.080 --> 0:46:40.160
<v Speaker 3>when we talk about the AI private credit leverage, subprime

0:46:40.320 --> 0:46:43.960
<v Speaker 3>economy nexus, then please leave us a positive review on

0:46:44.000 --> 0:46:46.960
<v Speaker 3>your favorite podcast platform. And remember, if you are a

0:46:47.000 --> 0:46:50.040
<v Speaker 3>Bloomberg subscriber, you can listen to all of our episodes

0:46:50.120 --> 0:46:51.400
<v Speaker 3>absolutely ad free.

0:46:51.760 --> 0:46:52.759
<v Speaker 4>All you have to do is.

0:46:52.719 --> 0:46:55.440
<v Speaker 3>Find the Bloomberg channel on Apple Podcasts and follow the

0:46:55.440 --> 0:46:56.360
<v Speaker 3>instructions there.

0:46:56.640 --> 0:47:14.200
<v Speaker 4>Thanks for listening in

0:47:22.600 --> 0:47:23.239
<v Speaker 5>In