HomeVideos

Former Intel CEO on What Went Wrong, What's Next + Lovable CEO on the Real Promise of Vibe Coding

Now Playing

Former Intel CEO on What Went Wrong, What's Next + Lovable CEO on the Real Promise of Vibe Coding

Transcript

1346 segments

0:00

spent a long time at Intel.

0:02

>> Yeah.

0:02

>> And uh

0:03

>> only 34 years.

0:04

>> 34 years.

0:05

>> Yeah.

0:06

>> Probably one of the greatest American

0:08

companies uh ever. And then absolutely

0:12

went off the rails and got absolutely

0:16

demolished by Nvidia, TSMC,

0:21

uh and I guess Apple to a certain

0:23

extent. So you had this incredible Intel

0:26

inside moment. We bought our computers

0:29

based on, you know, hey, the Pentium and

0:32

that sound

0:33

>> Intel inside, baby. Intel insideum.

0:37

And so, let's talk about how things went

0:39

wrong. What went right and then

0:42

>> how did it and and you were there for a

0:45

long time. You took a break and then you

0:47

came back. But there seemed to be have

0:50

been some critical mistakes that we can

0:52

learn from. So, let's just embrace it

0:54

and go right into it. tremendous success

0:56

as an American company coming back now I

0:58

think uh reasonably but when you when we

1:02

look back on it and we do our

1:04

post-mortem what were the mistakes a and

1:07

what would we change in terms of the

1:09

direction of that company

1:12

>> if you were building a global financial

1:14

system from first principles today you

1:16

wouldn't build it on 50-year-old legacy

1:18

rails you'd build airwalls one AI native

1:21

platform for global accounts cards and

1:23

payments it's designed to make the

1:24

entire entire world feel like a local

1:26

market. Others are bolting AI onto

1:28

broken infrastructure, but Airwall was

1:30

built for the intelligent era from day

1:32

one. Stop paying the legacy tax and

1:34

start building the future at

1:36

airwall.com/allin.

1:38

Airwall built for the future.

1:41

>> Having spent so much of my life there,

1:43

you know, I view it. I joined when I was

1:45

18. I went through puberty at Intel,

1:48

right? I joke, right? I was just like,

1:50

you know, I am so early. uh Grove,

1:53

Noise, Bar uh Barrett, right? Uh and uh

1:57

uh you know, they they were the people I

1:59

grew up at, right? You know, so on. They

2:01

were my mentors. They were the people I

2:03

adored uh for it and they were deeply

2:06

technical.

2:07

>> Andy Grove,

2:08

>> Andy Grove, Gordon Moore, Bob, you know,

2:11

co-inventor, you know, these were deeply

2:13

technical leaders. I remember when I

2:15

joined the executive staff for the first

2:17

time, you know, there was, you know,

2:19

probably 15 of the 20 people that were

2:21

in the room were PhDs, right? You know,

2:25

it was just that technical. And, you

2:27

know, I view one of the things that went

2:28

off the rail was when it started to be

2:30

run by business people

2:32

>> as opposed to technical,

2:33

>> the bean counters, the finance people.

2:34

>> Yeah. And you know when I became uh CEO

2:38

uh in 2001 that was the first technical

2:41

leader in essentially 15 years

2:44

>> right you know associated with it you

2:46

know and if you have a business leader

2:47

who does he promote business leaders and

2:49

you know right you know so I think one

2:52

of the fundamental things is and you

2:54

know as you look at the great technology

2:56

companies uh today you know they're

2:58

deeply technical

2:59

>> and founderled typically

3:01

>> you know and even if they're not you

3:02

know Satcha is not a founder no right?

3:04

You know, Sundar is not a founder as

3:07

well, but they're deeply technical

3:09

individuals. And when you're making

3:10

these hardcore technical, you know,

3:13

decisions that affect billions of

3:15

dollars, you don't do that through a

3:17

spreadsheet. That's a lousy investment,

3:20

right? Unless the technology trends make

3:23

it the right investment. And I think

3:25

that's one of the fundamental things.

3:26

And obviously you know in the five years

3:29

uh five six years before I came back you

3:31

know Intel gave $100 billion to

3:35

shareholders.

3:36

>> Oh the dividends

3:38

>> and stock buybacks

3:40

>> a hundred. What I wouldn't have done for

3:42

another hundred billion dollar on the uh

3:47

what would you have done? You probably

3:48

would have made chips for iPhone which

3:51

Intel passed on. Yeah.

3:53

>> Yeah. you know, but you know, it hadn't

3:55

built a new factory in a decade when I

3:57

got there. It's like, you know, how can

3:59

you not be building? How could you not

4:01

buy EUV machines? You know, there's just

4:03

all of these things, you know, that you

4:05

would only do as a technologist because

4:08

the economics behind them by themselves

4:10

were not good.

4:11

>> So, you know, it's getting back to the

4:13

core of technology to me that was, you

4:16

know, the fundamental thing. You know,

4:18

you make good decisions, you make bad

4:19

decisions as leaders. Every business uh

4:22

does that uh as they go along but uh you

4:25

know fundamentally this is a technology

4:27

business and you need technologists

4:29

running technology uh that then hires

4:33

technologists that are sitting at the

4:34

staff that then hire the best

4:36

technologist you know you know

4:38

>> and take big swings at you know

4:40

categories that could matter in the

4:43

future like skating to where the puck's

4:44

going. If you look at Apple, they did

4:45

the same thing for the past 15 years,

4:48

buying back the stock, tremendous amount

4:50

of dividends. They're the largest holder

4:52

of capital of any company, I believe, to

4:54

this date. And what if what companies do

4:58

they buy? They buy little tiny

4:59

acquisitions on the margins. I think the

5:01

largest ones was was Beats cuz they

5:04

wanted to get inroads into, you know,

5:06

certain uh demographic segments like in

5:08

the Android space that they couldn't get

5:10

into. But my god, what a colossal waste

5:12

of time. Like you said, they could have

5:13

done so many amazing things. Tell me

5:16

about Steve Jobs

5:18

in 2008, 2009 deciding, I think we're

5:22

going to make our own silicon and that

5:23

impact because was that a covert product

5:26

project or did you guys know he was

5:28

doing that? Did he inform you?

5:30

>> Well, that seemed to be another one of

5:32

those forks in the road. Yeah,

5:33

>> you know, Steve was an incredible

5:35

leader. You know, he was also a ruthless

5:37

leader, right? You know, very difficult.

5:39

you know, read Walder Isaxson's book on

5:42

him uh as well. I had many many

5:44

conversations with Steve over the years

5:46

uh you know, for it. Um but you know,

5:48

when they moved to Intel and the

5:50

Centrino chip, it was a big deal.

5:53

>> Yeah.

5:53

>> Right. And they were putting

5:55

extraordinary demands on Intel. You

5:58

know, make the chip smaller, drive lower

6:00

power. They're demanding uh customer.

6:04

And when he was no longer convinced that

6:06

we could continue to do that, you know,

6:09

he started the project,

6:10

>> right? You know, and if you remember

6:12

what was it, you know, you know, uh, P

6:15

semi, you know, they acquired some small

6:17

companies, started to build some

6:18

competency, but, you know, they did a

6:20

few little chips internally. It wasn't a

6:22

big deal and then the little chips got a

6:24

little bit bigger, you know, and Steve

6:25

was a master of this, you know, just

6:28

starting, you know, these small efforts

6:30

to build core competence inside the

6:32

company. Uh I remember when we had the

6:34

first conversation with Steve about uh

6:37

porting the uh operating system to the

6:42

Intel chip from the power chip that they

6:44

were running on before they moved to

6:45

Intel. And we were quite proud of the

6:49

silicon software competencies that we

6:52

had and compilers and operating systems,

6:55

you know. So Steve, we'll help you port

6:57

the operating system to the x86. And I

7:00

remember that Steve said, "I've been

7:02

working on that for the last four

7:04

releases."

7:06

>> He had been preparing the core

7:08

technologies inside of Apple for

7:11

something that might happen uh in the

7:14

future, you know, and he was already,

7:15

you know, to me, I just remember I was

7:16

just shocked. I, you know, I've ported

7:18

the last four releases to the x86. I

7:20

think we got this.

7:21

>> Yeah.

7:22

>> Right. You know, it was that kind of

7:23

thing. And that's how they got into the

7:24

semiconductor, you know, doing their own

7:26

semiconductor. Hm. I'm not sure I can

7:28

rely on Intel to be that much ahead of

7:31

the industry and I can start optimizing

7:34

the system design with the silicon

7:36

design as opposed to relying on one

7:38

that's been somewhat optimized for a

7:40

Windows environment versus an iOS

7:42

environment, you know, in their uh

7:44

operating system. And you know, it was

7:46

just, you know, uh, you know, it was

7:49

never that kind of thing. They sort of

7:51

said, you know, right, you failed as a

7:53

supplier. No, I can supply myself

7:55

better.

7:56

>> Yeah. and Jensen uh decides, hey, he's

8:00

going to go all in making these video

8:01

cards and talk about just incredible

8:06

uh serendipity that these happen to be

8:09

also very applicable for cryptocurrency

8:12

and running these AI jobs.

8:15

>> Yeah.

8:16

>> Was that luck or skill or combination of

8:19

both there? Well, you know, when you

8:21

think about that progression, you know,

8:23

Jensen, he was just building high

8:25

performance computers, you know,

8:27

throughput machines. You know, when we

8:29

were at the height of our strength on

8:32

CPUs, uh, at Intel, we sort of scoffed

8:35

at his machines. Yeah.

8:36

>> Right. You like, oh, that's a graphic

8:38

machine. You, you know, there's some

8:40

gamers who want to use that kind of

8:42

stuff, right? You know, it was always

8:43

the big CPU and those little GPUs. But

8:46

when they started to build a real

8:48

software stack, Yes. with it, right? You

8:50

know, sort of, okay, this CUDA thing and

8:52

SIMT as a technology, you know, uh, you

8:55

know, uh, multi-threading and so on. And

8:58

it just sort of kept getting a little

8:59

bit better and a little bit better and

9:01

it was a little bit jobslike in that

9:03

way. You know, we're just making it

9:04

better every release and it's becoming

9:07

more robust and all of a sudden, you

9:10

know, the crazy, you know, uh, Japanese

9:13

HPC guys said, "Hey, we could take those

9:15

graphics cards and maybe start using

9:16

them in HPC." H,

9:18

>> right? you know, and that was sort of

9:20

defining moment where it wasn't just

9:22

about doing graphics anymore. This was a

9:25

more computationally dense platform to

9:28

start attacking some of the world's most

9:30

interesting workloads. And I think

9:32

Jensen would agree that was a defining

9:34

moment and them sort of saying, "Oh,

9:36

these aren't just graphics cards

9:37

anymore. You know, these are

9:39

generalpurpose computing devices that

9:42

can start applying to these other uh

9:44

workloads." And you know AI was you know

9:47

had gone through what its fifth nuclear

9:49

winter by that point. We're just like

9:51

man you know you know this is never

9:53

going to matter right we're never going

9:54

to you know get the breakthroughs but

9:56

the community around it was continuing

9:58

to develop uh you know for it and the

10:01

CUDA software kept getting better uh

10:04

generation by generation and uh you know

10:07

I had a project at Intel Larabe right

10:09

where we were trying to take the x86 and

10:12

essentially do the same thing right you

10:14

know for it and you know in my first

10:16

departure from Intel the project was

10:18

killed a week after I left

10:20

>> huh

10:21

>> and the world would have been so much

10:23

different right I

10:24

>> I mean it really I think it's

10:27

illustrative of illustrative of what

10:30

continuous innovation taking some risks

10:32

and doing that fundamental research and

10:36

the compounding power of technology

10:37

because I think it was William Gibson

10:39

who said the street finds its own use

10:40

for technology like

10:43

Nvidia did not predict that this Bitcoin

10:46

project would take over and that this

10:48

would be the best way to do those

10:49

computations, nor did they anticipate, I

10:52

think, you know, that AI would take off,

10:54

but because it was the best solution,

10:56

the hacker community could kind of

10:58

figure that out. Well, as we wrap on the

11:00

Intel portion of your uh career, um,

11:04

okay, Apple Silicon, that's one. Uh, and

11:07

then you have Nvidia, and then you have

11:09

this Taiwanese company, uh, that starts

11:13

making, you know, really great at

11:15

fabricating the these chips. Um and

11:19

Intel missed that as well. Yeah. And and

11:21

maybe you could talk a little bit about

11:23

TSMC and their surging and we can even

11:26

get into a little bit of the the

11:27

politics of it now and then we'll get

11:29

into some of these AI chips and venture

11:31

investing. You know the thing with TSMC

11:34

was they started with a vision of

11:36

foundry

11:37

>> right you know they were going to become

11:39

the factory for the industry and again

11:41

these factories are so expensive 20

11:44

billion 30 billion and uh the

11:47

engineering and the continuous

11:49

investment required to do it and you

11:51

know it was a stunning you know vision

11:54

uh at that point in time Intel was IDM

11:57

as we called it the integrated design

11:59

and manufacturing you We never worked to

12:03

make our process and our factories

12:06

available for third parties

12:08

>> right you know it was always this thing

12:09

hey it's you know we do enough CPUs

12:12

oursel you know we reuse it for chipsets

12:15

and some of the other things that we're

12:16

doing but it was never standardized in a

12:19

way that it could be made available for

12:21

a broad ecosystem you know using PDKs

12:24

and all the design tools you know we did

12:27

a lot of our own EDA tools ourself you

12:29

know one of the projects that I started

12:31

early in my career was the foundations

12:33

of EDA, right? Uh as well, the first

12:36

place and route, you know, the first

12:38

standard cells, the first highle

12:40

description language, you know, it was

12:42

so proprietary and TSMC basically cut

12:45

that in half and says, I don't care

12:47

whose chip it is. I don't care what

12:48

you're designing, I'll be your

12:50

manufacturing partner. And at the time,

12:52

that was such a trivial piece of the

12:55

business, Intel didn't even care,

12:57

>> right? You know, so on. And then over

13:00

steady progress over a long period of

13:02

time and Apple as a customer driving

13:06

them to be could be become really

13:08

meaningful. You know obviously the world

13:10

changed and when I came back uh to uh

13:13

Intel in 2001 TSMC was producing 5x the

13:17

wafers of Intel.

13:18

>> Wow.

13:19

>> Right. Not 10% more 5x.

13:22

>> Yeah. And all of a sudden that model of

13:25

foundry became the model of the

13:27

semiconductor industry with two

13:29

exceptions Intel and memory. you know,

13:32

memory design and manufacture, right,

13:35

for you know, that is uniquely

13:37

different. And obviously, you know,

13:38

we're seeing the, you know, $3 trillion

13:41

memory companies just extraordinary, you

13:43

know, and, you know, trillion dollar

13:45

foundry company uh in TSMC. You know,

13:48

the industry has said, I want a lot of

13:50

wafers. I want a lot of innovation of

13:53

different designs. I have a layer of

13:55

standardization and EDA tools. And the

13:58

world changed. And obviously as I came

13:59

back to Intel that was one of the core

14:01

thesis of the new strategy. Yeah. We

14:03

must become a foundry as well five to

14:06

one and now it's more like seven to one

14:07

in terms of wafers you know to TSMC to

14:11

and

14:11

>> are we going to be able to onshore that

14:13

obviously we had the chips act and just

14:15

give us broad strokes what you think is

14:17

going to happen here in terms of

14:19

obviously Taiwan is in play. Some people

14:22

in the administration believe um it's

14:25

going to happen the year after Trump's

14:27

out unless he takes his third term.

14:29

Other people believe like it was going

14:32

to happen as early as 27 uh or maybe

14:35

going into 28. So,

14:38

are we going to be able to replicate

14:41

that here in America in a reasonable

14:42

amount of time, or is this like truly

14:44

could be a cataclysmic event if,

14:47

you know, god forbid, China decides,

14:49

hey, we're going to blockade um Taiwan

14:52

and and the Taiwanese decide, yeah,

14:54

we're going to burn the fabs and we're

14:56

going to fly out all of the engineers

14:58

and ship them to America.

15:00

>> Well, there's a lot in that question,

15:02

you know. Do we have an hour to talk

15:04

about this question? Well, I mean we

15:05

have six minutes, but Okay. Um, yeah, do

15:08

the best you can.

15:09

>> Okay.

15:11

>> I want to talk also about the AI bubble.

15:13

>> So, super, you know, three things about

15:14

this super quick. You know, one is the

15:16

chips act is having benefit.

15:17

>> Yeah.

15:18

>> Right. You know, when we started the

15:20

chips act in, you know, in 2001 when I

15:22

came back, the US was building about 12%

15:25

of leading edge. Today, that number is

15:27

more like 18%.

15:29

>> Okay. You know, we're making progress.

15:31

It's not 50%. We have a long way to go,

15:34

right? You know, Intel is starting to be

15:36

a real foundry. Okay, that's real

15:38

progress. Uh, and TSMC's factories are

15:41

up and operating at scale, right? We

15:43

have Samsung and, you know, uh, as well.

15:46

But, you know, I say the Intel and the

15:48

TSMC progress. Okay, that's meaningful.

15:51

Now, let's make it ugly for a second.

15:53

Uh, the island of Taiwan has less than 3

15:56

weeks, a big article in the Wall Street

15:58

Journal two weeks ago on this, less than

16:00

3 weeks of energy reserves.

16:04

Wow. Okay, that should just put a chill

16:08

in everybody's spine, right? Because the

16:11

blockade after 3 weeks, the island

16:14

browns out. When you turn off a fab, it

16:17

doesn't come back on for 90 days, right?

16:20

The economic impact of a brown out of

16:23

Taiwan is greater than the Great

16:25

Depression, right? Uh in the world,

16:27

never do you need to do anything a shot

16:30

to be fired. You just need to say,

16:32

"Great, no energy for 3 weeks.

16:33

>> No oil." Yes.

16:35

>> Right. No LG, right? You know, that's

16:36

how the island run. That is scary, you

16:39

know, to me. We need more resilient

16:41

supply chains uh associated, you know,

16:44

with it. And I don't think this is an

16:46

alternative for the world because if it

16:48

really does become a risk, you know, and

16:50

I'm, you know, I, you know, I don't sit

16:52

in the situation room and get all the

16:54

data and so on, but let's remind each

16:56

other that I think China has blockaded

16:58

the Taiwan Straits seven times over the

17:00

last four years.

17:02

>> Yeah.

17:02

>> This isn't a theory.

17:04

>> No, no. They're running exercises.

17:05

They're being pernitious and

17:08

>> right

17:08

>> pretty provocative in terms of

17:10

>> Is that 2027? Is that 2030? Is that

17:12

2035? their intentions have been clear

17:15

over a sustained period of time. We need

17:17

more resilient uh supply chains, you

17:20

know, forward. So, something, you know,

17:21

I put a lot of my time and energy into

17:23

and we're making progress, but we need

17:25

to go faster, need to go more

17:27

meaningful.

17:27

>> Yeah. And let's talk a little bit about

17:29

the AI buildout. I mean, you watched the

17:32

PC revolution, servers, the internet.

17:35

These were all extraordinary buildouts.

17:37

And then this is the buildout to end all

17:41

buildouts. the amount of data centers,

17:43

the amount of chips, the amount of

17:44

inference needed.

17:46

Do you think it's a bubble? I think I've

17:48

heard you say like it's it's obviously a

17:50

bubble, but what what's the risk factor

17:54

here? That we build too much uh or that

17:57

the technology doesn't solve enough

17:59

problems and we are swimming in tokens?

18:02

What what worries you about what you're

18:04

seeing now? the valuations of these

18:06

companies has gotten quite

18:07

extraordinary. And you know, if they

18:10

build too much and they spend too much

18:12

money and they don't make enough money,

18:14

well, based on your experience with

18:17

running a company, a public one, that's

18:20

a lot of tension on it. When you don't

18:22

make as much money as you're spending,

18:25

people tend to fall out of love with

18:26

these stocks. Yeah.

18:28

Well, I do think there, you know, there

18:30

there is a silver lining here that

18:33

guarantees we don't get too far ahead of

18:36

oursel in terms of bubble, you know, and

18:39

that is energy capacity.

18:41

>> Right.

18:41

>> Right. You know, energy capacity in the

18:43

world is expanding four 5%. You know, in

18:46

the US we had a decade at 1%. Right. You

18:50

know, I mean, it's just hideous what we

18:51

did to our energy grid, you know, over

18:53

about a decade and a half. But now

18:55

that's getting built out. But

18:57

essentially, nobody's going to build and

18:58

buy GPUs and build data centers if they

19:01

don't have energy.

19:02

>> So essentially, you have an upper bound

19:04

on how aggressive and how hyped and

19:07

bubbled that we get. So I take a lot of

19:10

soloulless in that.

19:11

>> Yeah.

19:11

>> Right. You know, for it because what

19:13

then is the incremental value of a token

19:16

and if it's a measure of intelligence,

19:18

it's somewhat infinite, right? You know,

19:20

in the sense if I have more

19:22

intelligence, I will do, you know,

19:24

better supply chain. I will do better

19:26

finance. I will do more, you know,

19:28

efficient logistics. I will, you know,

19:30

all of those things. So to me, the the

19:33

potential value that we unleash in a

19:36

token economic world is somewhat

19:38

infinite, right? And particularly with

19:40

labor shortages and so on that we see

19:43

right in uh developed countries, I am an

19:45

optimist, you know, that we're in a

19:48

couple of decade buildout.

19:50

>> Wow.

19:50

>> Right. Not a couple of years, a couple

19:52

of decades. One of the big objectives

19:55

I've said is that I have to make AI

19:58

10,000x

19:59

better,

20:00

>> right? You know, it's way too expensive

20:02

today. you know, we want to drop, you

20:04

know, by five orders of magnitude the

20:05

cost per token, you know, the energy,

20:08

you know, per token so that we really do

20:10

have Jevans law that we just explode the

20:12

access to AI, right, in much more

20:15

economic uh ways,

20:17

>> which it does seem like Jevans uh

20:19

paradox has been at play over the last

20:21

year, like, oh my lord, these tokens are

20:23

so cheap and the tools are getting so

20:25

good. Yeah, I'm just going to start

20:27

using these tools all day long until the

20:29

bill comes in and you're like, "Okay,

20:30

yeah, maybe I need to get some ROI out

20:32

of this." But you do have these

20:34

incredible companies, Cerebrris, Grock,

20:36

etc. making inference

20:37

>> dematrix

20:39

silicon and so you know, and you know,

20:40

if we accomplish right, you know, these

20:43

orders of magnitude improving and token

20:46

economics, availability, reduction in

20:48

energy costs associated with it. You

20:50

know, we just have a fantastic couple of

20:53

decades in front of us. There has not

20:55

been a time in human history where it's

20:57

been better to be a technologist than

20:59

the one we're in right now. We will

21:01

solve chemistry. We will solve language.

21:03

We will, you know, invent new materials,

21:05

re, you know, new forms of, you know,

21:08

uh, interaction, you know, uh, killing

21:11

cancer, right? Lifting people out of

21:13

poverty. There is not a better time to

21:15

be alive than the one that we're in

21:17

right now. And as technologists, we get

21:19

to sit in the driver's seat of it.

21:21

>> Pretty amazing. and you're investing uh

21:23

and that's your passion. Now what do you

21:26

think of these valuations? It's quite

21:29

seems a you know if you live through the

21:31

dotcom bubble we did see a disconnect

21:33

there. These companies slightly

21:35

different. We just had 11 labs up 600

21:38

million in revenue. Lovable I think

21:40

they're at five or 600 million. So

21:42

that's quite different than the do

21:44

speculation. Yeah.

21:45

>> Yeah. Well fundamentally we have real

21:47

revenues you know real margins coming

21:49

out of these businesses as well. You

21:51

know that said anytime the multiples get

21:52

too high okay some corrections you know

21:55

and to me periodic corrections that keep

21:57

the multiple you know earnings multiples

22:00

and you know so on in reasonable things

22:02

is good because this will not be a

22:03

smooth curve you know I'm predicting two

22:06

decades of goodness and there's going to

22:08

be lots of disruptions along the way

22:10

it's not going to be a smooth curve and

22:12

every time we have one of those

22:13

corrections say thank you right we're

22:15

not letting the bubble get ahead of

22:16

itself right you know hey we had the SAS

22:19

apocalypse there's going to be other

22:20

apocalypses on that journey when when

22:23

industries get impacted by the

22:26

capabilities that will be unleashed and

22:28

that's even before it gets exciting and

22:30

what I call the trinity of computing

22:32

classical computing AI computing and

22:35

quantum computing and when those three

22:37

come together okay that's when things

22:39

get really exciting

22:41

>> quantum's been about 5 years away for 25

22:44

years um when is it actually going to do

22:48

anything meaningful

22:48

>> this decade this decade. So by 2030,

22:51

>> yep,

22:52

>> it'll be meaningful. What should we

22:54

expect in terms of its impact in 2030?

22:56

Like

22:57

>> you know, you're going to be able to

22:58

start doing things that cannot be

22:59

computed today.

23:01

>> You know, chemistry, you know, biology,

23:03

there will be things that can't be

23:05

computed today. You know, some of the

23:06

easy things will be some of like the

23:09

logistics where I will compute the best

23:11

answer to get this thing to you, right?

23:14

>> Traveling salesman problem,

23:15

>> right? you know all of a sudden all of

23:16

those problems uh obviously it's

23:18

probably going to be you know 2020 2032

23:21

2033 when we solve you know things like

23:24

encryption right you know where you know

23:26

you'll have the fundamental Qday you

23:29

know kind of implications but this

23:30

decade we will see quantum supremacy uh

23:33

results across multiple industries you

23:36

know we know how to build cubits we know

23:38

how to error correct cubits we now have

23:40

algorithmics right against uh quantum

23:43

and you know now it's just about

23:45

engineering scale.

23:46

>> Who's going to win?

23:47

>> Well, obviously I'm a SI quantum guy,

23:50

right? Since that's one of our portfolio

23:51

companies. But the thing that you're

23:53

seeing is that you now have like four,

23:56

five, six modalities of quantum that are

24:00

demonstrating pretty good results,

24:02

right? You know, across trapped ions,

24:04

across, you know, photonic uh

24:06

approaches, spin uh approaches. So, you

24:09

now say modality is not an issue. Error

24:11

correction's been proven uh across them.

24:14

And you know, I think the race will be

24:16

on and my prediction is meaningful

24:18

results before 2030.

24:20

>> Wow. You realize that's about 40 months

24:22

from now.

24:23

>> Yeah. Okay. Meaningful results. Thanks

24:25

so much, Pat, for sharing all this

24:27

incredible uh

24:28

>> information and knowledge. Great to see

24:30

him.

24:30

>> Very good.

24:34

>> Your most valuable conversations rarely

24:36

happen at a desk. The hallway sink, the

24:38

dinner, the quick founder call. Plaude

24:40

no pins clips on and captures all of it

24:43

hands-free. Afterward, Plaude

24:45

intelligence turns the recording into

24:47

clean notes and clear next steps. You

24:50

stay in the room, Plaude handles the

24:52

rest. For people who live in meetings,

24:54

that's real leverage. Wear your Plaude

24:56

at plaud.ai.

25:00

>> Oika is one of my favorite founders.

25:03

He's the founder of Lovable. Why do I

25:05

love this founder? Uh well he's built a

25:08

product that people are addicted to

25:10

primarily Anton the people who work for

25:12

me and I uh love talking to you because

25:16

as a founder you have a northstar you're

25:19

incredibly laser focused on enabling

25:22

anyone to build great software. Yeah

25:25

it's the mission of the company. I'm

25:27

paraphrasing here but

25:28

>> essentially that's the mission of

25:29

lovable

25:30

>> mission I talk about empowering humans.

25:32

empowering humans

25:33

>> and the first gap is to build a product.

25:36

>> The second gap is to build a business

25:38

around that product, right?

25:39

>> And now at everyone at Lovable, we're

25:41

we're working on both of these two gaps,

25:43

right?

25:43

>> The first one, we got very far. We're

25:46

seeing a million new projects built

25:48

every single week on the

25:49

>> incredible. And on the on the second

25:51

one, we're investing a lot in making it

25:53

easier to run your business and to get

25:56

people to care, people to discover what

25:58

you build and the entire business of

26:00

what you're whatever you're doing as a

26:01

small business. As if you're a large

26:03

business, we're also getting a lot of

26:05

traction. Um, and uh we're actually

26:08

seeing as a proof of that more than 700

26:12

million visits to the applications every

26:14

month. So every month there's um extreme

26:17

growth in in the surface area of of the

26:19

entire

26:21

more than 50 million apps built on the

26:23

platform to date.

26:24

>> How many years has lovable been in

26:26

market or how many months now?

26:28

>> 20 months since 20. Yeah. And and again

26:31

we're seeing people who are first-time

26:33

founders. We're seeing enterprise

26:35

leaders move much faster together with

26:38

their teams on this platform that has a

26:40

lot of opinionated pieces in how you

26:44

should uh create software and how to

26:46

operate that software and how the

26:48

different applications in your company

26:50

connect to each other over time. So

26:51

that's what why we're seeing so much

26:53

growth also on the enterprise side which

26:55

where where we actually growing fastest

26:57

right now. This is really interesting

26:58

because 10 years ago, uh, people were

27:01

doing wizzywig software. Um, what was

27:05

the name for it? Before Vive, no code,

27:08

low code. Yes. And when I saw that 10

27:11

years ago in my incubator, you know,

27:14

every 20th company, somebody would come

27:16

in who was an MBA or not a developer and

27:19

they had vibecoded something and um not

27:22

vibe coded, they had no coded and they

27:25

were using these different software

27:26

platforms and the software didn't look

27:29

good. It didn't work perfectly well. It

27:31

was slow, but the promise was there. And

27:35

I guess it took LLMs and this new

27:38

intelligence

27:40

to make actually good software. So maybe

27:42

you could talk a little bit about

27:46

who is the customer because developers

27:50

uh do developers use lovable or is it

27:53

the other 95% of society that are your

27:56

customers? How do you think about who

27:57

your ideal customer profile is?

27:59

>> Yeah, we're seeing people use Lovable

28:02

both with a technical background. about

28:04

20% are technical or some type of

28:06

engineer and they they love that we're

28:09

quite opinionated. We put all the best

28:11

practices into how the software is

28:13

architected and we make it seamless to

28:16

um with one prompt get payment set up in

28:18

a very secure way and do things like run

28:22

security scans after every change even

28:24

now in the background monitoring the

28:26

projects. So it's actually quite

28:29

appreciated by the engineers in the

28:31

technical community. Um also because

28:33

it's a great bridge

28:35

>> from the nontechnical people which is

28:37

four out of five are are nontechnical uh

28:39

and they're building uh often first to

28:42

figure out what is the right thing to

28:43

build

28:44

>> which is where lovable has always been

28:46

exceptionally good and uh now what we're

28:49

seeing is that people are running

28:53

businesses making more than million

28:54

dollars of revenue on the on this

28:56

platform. So it's it's this we're

28:58

building for everyone. It's this entire

28:59

spectrum. And what's what's exciting to

29:01

see is often that if someone who

29:03

discovers lovable from their colleagues

29:04

at a large company, they go out and then

29:07

run a side hustle and some of those

29:10

those idols hustles really work. They

29:11

make hundreds of thousands of dollars

29:13

and then they become a founder after

29:14

that. So there's this crosspollination

29:16

from both.

29:17

>> Yeah. And this is like the really

29:18

interesting thing about vibe coding. If

29:20

we were sitting here last year, people

29:21

would look at it and say it's a great

29:23

way to make a mockup. like you said, a

29:25

great way to think about product and

29:27

maybe create wireframes or a workable

29:31

prototype. All of that's out the window

29:33

now. The whole concept of building

29:36

wireframes and building a mockup, well,

29:40

you can just go right to building the

29:41

product in a day or two days. And what

29:46

people I think don't appreciate about

29:47

what you're doing at Lovable is after

29:50

you've made a product that you're proud

29:52

of and that has some product market fit,

29:55

there are many more steps that are

29:57

required. You mentioned payments, you

30:00

mentioned security, uh making sure that

30:02

the data isn't lost or that it's not

30:04

leaked.

30:06

That's changed dramatically over the

30:08

last 12 months. Yeah,

30:09

>> very much so. So um I would say many

30:12

engineers they don't look at the code

30:14

they don't write code anymore and that

30:17

means that you don't need to be an

30:19

engineer to create software right um but

30:21

the the thing that lovable does for any

30:24

anyone also the non-technical people is

30:26

that it it um takes uh creates a

30:30

structure for the architecture of the

30:31

software that you build and it makes

30:33

sure that you don't go off a cliff um

30:36

and that things like setting up payments

30:38

emails things like getting discovered by

30:41

other AI chat engines and uh by Google

30:45

search those things are kind of taken

30:47

care of. So you don't have to know how

30:49

all these things work in the details you

30:52

trust you can trust the platform to take

30:53

care care of data security connecting to

30:57

other tools that you might be using in a

30:59

secure way and and that's really where

31:01

um us being opinionated from day one and

31:04

being focused on making this for the

31:06

99%. It's a it's a vast market right

31:09

from the from day one is what made us

31:11

very successful.

31:12

>> Yeah. And I can tell you internally I

31:14

gave my team all the different tools

31:16

they could possibly want to use and

31:19

somebody had started with lovable. I

31:21

think I told you the story when you were

31:23

on this week in startups a year ago like

31:25

and they made some interesting websites

31:28

and they were trying to make an

31:29

internet. They couldn't quite get it

31:31

done. Then I had some people who started

31:34

using you know cursor or clawed code.

31:37

They started vibe coding stuff but they

31:39

couldn't finish the product. And then

31:41

people tried to solve some problems with

31:43

codework. I really like perplexity

31:45

computer. And then my team came to me

31:48

and for one of our projects I was

31:51

talking to you about founder university

31:52

our pre-acelerator. They wanted to make

31:54

an internet.

31:56

Um, now this is something I would have

31:58

never okayed because it would have cost

32:00

$500,000

32:02

10 years ago to make it and we don't

32:04

have that kind of budget. You know, we

32:05

would rather put that towards the

32:06

founders in the program and getting more

32:09

people into the program. And in 4 to 8

32:12

hours, they made the whole internet and

32:15

they made a bunch of things I hadn't

32:16

asked for. And it was the person running

32:19

the um this founder university who made

32:23

it and she did it on her own without

32:27

uh permission in lovable. I said, "Whoa,

32:29

where how did you build this?" She said,

32:30

"Loveable." I was like, "Oh, we still

32:33

have lovable." And they're like, she's

32:34

like, "I just put it on my corporate

32:36

card." To your point, she made it. Now

32:39

that software is driving the program and

32:45

the reason people do the

32:48

uh the the program in their country, we

32:50

have it in Saudi and in Japan is because

32:52

it has economic impact.

32:54

>> So I said, "Hey, I have an idea. Can you

32:56

make for me an economic impact of the 50

32:59

companies that are in the program?"

33:02

She asked Lovable to do it. I gave her

33:04

some, you know, prompting, human

33:07

prompting boss to now it has the

33:09

economic impact in there and it

33:12

considered, you know, with our

33:13

prompting, well, how many people work at

33:15

each company? What are they paying

33:17

taxes? How much do they rent their home

33:19

for? What is their average salary? And

33:21

it built something that I would have

33:23

never been able to afford to build. And

33:25

lovable is 50 bucks a month, I think. I

33:28

don't know how much you charge, but it's

33:30

far too little. Like

33:32

>> $50 a month, I think.

33:33

>> Yeah. That's if you're on a business

33:35

plan. Yeah. It starts at 25.

33:37

>> Yeah. So, uh, the economic impact of

33:40

what you're building is I would equate

33:44

for what you built to us, it would have

33:45

cost me $500,000 2 years ago. It was

33:48

built in 4 hours by an employee, which

33:51

if you just put employees at 50, 60,

33:53

whatever, $70, uh, plus the cost of your

33:56

software, it got made for less than

33:58

$2,000

33:59

>> in a year. It's extraordinary.

34:02

I I'd love to hear more about the

34:04

progress of the of the internet.

34:06

Anything that you asked for that you

34:08

want to forward directed to me.

34:10

>> Uh well, right now, you know, my concern

34:13

was security and making sure that data

34:16

didn't leak and they talked to your team

34:18

and they went through it and

34:20

>> it's secure. So, we feel good about it.

34:23

>> Well, look, um I'm now asking people who

34:27

do penetration testing to say, I want

34:29

you to compare all the tools. Yeah. and

34:31

uh make sure that there's a all the work

34:33

that we're doing that's not visible on

34:35

security and trust. Yeah, there's a lot

34:37

a lot a lot of things um where we we

34:41

invest and spend money on that every

34:43

also free users get a lot of security

34:45

scanning running in the background that

34:47

that actually um translates to something

34:50

that security experts can can see. And

34:53

>> a year ago we were at mock-ups. Now

34:55

we're at functionality and secure and

34:58

super viable for deployment. Where will

35:01

you be in a year?

35:03

>> Yeah. So, what we're seeing is that

35:05

there's a gap in build being able to

35:07

build the product, right? And and you

35:09

built an entire internet on the

35:11

platform. That's great. Um, what we've

35:13

done since then is to have a new product

35:16

line basically the hosting part which is

35:18

both the AI and you know all the normal

35:20

hosting and that product line has been

35:22

going faster than the building uh thing.

35:24

I mention

35:25

>> AWS competitor.

35:27

>> It it lets you it lets you run all your

35:30

software and then we're working with

35:31

companies like AWS under the hood as

35:33

well. But but what you also want to have

35:36

is um to use lovable we're seeing by our

35:40

customers as an AI co-founder,

35:42

>> a partner that you talk to about

35:43

everything in your business. And if

35:45

you're running your apps, your tools are

35:48

on the platform, then just talking to

35:51

Lovable has access to all the data that

35:53

you might want to know about your about

35:56

your company, how it's doing. So, we're

35:59

we're working with some of our customers

36:02

in pre-release to give them access to a

36:04

co-founder that works for you even when

36:06

you're sleeping

36:07

>> and comes back to you in the morning and

36:09

says like, "Here are some strategic

36:11

directions you could go. here's some

36:13

optimizations you can do go in terms of

36:15

growing your business faster serving

36:16

your customers better uh faster uh and

36:20

and and that's um that evolution towards

36:23

operation and intelligence for towards

36:26

driving towards outcome

36:28

>> for your business

36:30

to build the software but you stay to

36:32

build the business

36:33

>> yes to operate your business and um what

36:36

we're already doing I've been doing for

36:38

a very long time is to compound from

36:40

everything we're learning every time

36:42

lovable makes a mistake. Uh it goes to a

36:44

gentic system with our engineers in it

36:46

improving it. That compounding

36:48

intelligence is of course applicable to

36:52

our our customers, our users running

36:54

their business on our platform as well.

36:56

>> Is software going to become

36:59

100% bespoke even like the internal

37:02

tools. I was looking at Slack and our

37:06

bill for Slack even on the highest

37:07

version is maybe $10,000 a year. It's

37:10

not a lot of money. It's well worth it.

37:13

But I was starting to think, well, maybe

37:15

I should vibe code my own Slack so it's

37:18

integrated into everything we do at a

37:20

deeper level. So how do you think the f

37:23

what do you think the future will look

37:24

like in terms of some of these

37:28

you know uh foundational pieces of

37:31

software that every startup every

37:32

enterprise uses Salesforce HubSpot

37:36

Slack

37:38

uh the Google suite Microsoft Office

37:41

will bespoke software

37:44

start to replace those do you believe

37:46

>> I I like this question let let me ask

37:48

answer it but I'll just give you a story

37:51

about someone I recently heard who's

37:52

going on this journey. They're quite

37:54

advanced. So,

37:56

>> NAD, he works at a pretty large company

37:59

in the US, Nursa, and uh he came to our

38:02

platform because he wanted to build out

38:04

a new product lines, nurse study for

38:06

educating more nurses, right? And and he

38:09

built out all the admin tools for the

38:12

program, the scheduling for the nurses

38:14

getting getting their licenses and their

38:16

certification management. and he was

38:18

able to build that into a product and to

38:20

take it to market because they have they

38:22

have had all that access to nurses

38:24

wanting their certification. What he

38:26

also did was he took it into the back

38:29

office internally and they've now

38:31

replaced more than 10 tools that they

38:33

had bespoke applications and um I think

38:38

in terms of your question you can do

38:40

that for multiple reasons. In their case

38:42

they're saving more than a million

38:43

dollars per year,

38:44

>> right?

38:44

>> So that's that's huge, right? But it's

38:47

also the case that in some cases you

38:50

have specific requirements where the

38:52

tools that you've been using to date

38:53

they aren't suited for those requirement

38:56

exactly and in those cases I think yes

38:59

>> you will have more more bespoke

39:01

solutions. Yeah,

39:02

>> but we're I also expect us to see that

39:06

lovable continues to interoperate with

39:09

all of those tools. And uh I'm not sure

39:12

if you tried this if if you ask for

39:14

connecting to anything in the Google

39:16

suite or now to anything in the

39:18

Microsoft suite or or Slack lovable

39:21

guides you through all the steps to do

39:22

that in a way where you can get a a very

39:25

good overview of exactly how the data

39:27

flows which is of course very important

39:29

that you don't give access to the wrong

39:31

person to the wrong data and you can

39:32

continue to use Salesforce um HubSpot

39:35

and all the tools that you kind of like

39:37

to use under the hood but with a bespoke

39:39

interface on top of H how have these new

39:41

frontier models they're in some ways

39:44

competitive but in some ways you can use

39:48

them to power lovable. So how do you

39:50

think about the competition with them

39:54

opensource

39:55

a and the future of lovable because

39:57

people have announced that lovable's

39:59

dead every 6 months since you started

40:02

and then every 6 months you go from 100

40:05

to 200 to 300 I think you're at 400

40:07

million in revenue something crazy. We

40:09

we we reached 500 in May.

40:11

>> Okay. Growth is a phenomenal.

40:13

>> So you're dying again by another 100

40:16

million in annual revenue.

40:17

>> Exactly.

40:18

>> So but underneath the hood you're using

40:21

some of these.

40:22

>> Yeah. Let me explain. Yeah. So we've

40:24

always had this strategy that we do

40:26

whatever is best for our customers. And

40:28

in terms of the intelligence that means

40:31

that we're using multiple models. And so

40:35

if you ask Lovable now, it's actually

40:37

routed to the model that's most suitable

40:40

to whatever you want to do. And that's

40:42

both the commercial frontier models. So

40:45

from multiple vendors

40:46

>> and increasingly it's open weight models

40:50

where our team when whenever it's get

40:52

gets routed to an to our own model that

40:55

model becomes more intelligent for our

40:57

agent harness. Yeah. especially on the

40:59

mistakes that it might be making in some

41:01

cases on which which tool to call, which

41:04

integration to create and how to guide

41:06

you through uh success for your

41:08

business.

41:09

>> Right. So, you're all in on open source.

41:12

You believe that's the future of

41:14

Lovable. I I'm reading into it. So we

41:17

have multiple partnerships and we're

41:18

investing heavily to be close with those

41:20

partners and it's the big the big labs

41:22

and it's also to make sure that um we

41:26

get the fastest performance at the

41:28

lowest cost for our customers when we

41:31

know that we can do that with our own

41:32

models

41:33

>> right

41:34

>> and uh we have a really really strong

41:36

research team up in Stockholm who is

41:38

working on what's called post training

41:40

so and we're applying all the best

41:42

practices to do that and scaling up that

41:44

team uh quite significantly since we

41:47

also believe it's a it's a part of the

41:49

European ecosystem to have that

41:51

capability in Europe specifically.

41:53

>> Are you doing or are you using any of

41:55

the data labeling data training

41:58

companies to help you understand the

42:01

most common businesses and build that

42:03

proprietary data? So, so what we're

42:06

doing is that we're looking at um the

42:08

mistakes that any of the models do right

42:10

now and then we we prioritize them by

42:13

what drives most impact for our

42:15

customers and then we make the models we

42:17

create data sets or we um we do did

42:19

something called reinforcement learning

42:21

specifically for the problems where the

42:23

frontier models are making mistakes for

42:24

us right now and um we have this

42:28

enormous token distribution right from

42:31

um a million new products being built

42:33

every every single

42:34

You're burning a lot of tokens.

42:36

>> We are. Yes. And that's and that's a lot

42:38

of signals for making the system both

42:41

the agent harness

42:43

>> and um what we've been refining over the

42:46

last two years which is the skills that

42:49

we have have this like internal type of

42:50

skills that the agent knows when to

42:53

remember the facts from our software

42:55

engineers that know how to build really

42:56

really good software. We're modifying

42:59

both of those on every every single

43:00

week.

43:01

>> It makes total sense. And somebody told

43:02

me some companies are doing token

43:05

dumping. They're, you know, selling $100

43:08

worth of tokens for $50. Um, you know,

43:12

basically they become token resellers in

43:14

some ways and they're money losing

43:16

businesses. You have to you're money

43:19

you're profitable I believe now or close

43:21

to it. Um, we we always monitor our

43:24

margins, but again um we're doing what's

43:26

best for our customers and that means

43:28

that often means more intelligence. So

43:30

we're not we're not looking at oh let's

43:31

use a we've never had the decision to

43:34

say let's use a cheaper model here if

43:37

it's measurably worse for our customers

43:40

and we can measure that what's best for

43:41

>> but are they is it unlimited for the 50

43:43

or you have caps now

43:44

>> we have caps

43:46

overages and caps are people starting to

43:48

hit them

43:49

>> yeah our customers definitely hit caps

43:51

and then you can top up you can have a

43:54

we have multiple subscription tiers

43:56

>> what number I'm just curious like what

43:57

percentage of people need to top up.

43:59

They're so addicted to it that they're

44:01

blowing past the the

44:02

>> so from the lowest subscription tier.

44:05

>> Yeah.

44:05

>> Um I I think it's the

44:08

>> uh m

44:10

it's something like 60% of our customers

44:12

I think

44:13

>> I'm hearing that more and more often

44:14

that people are willing to pay the

44:17

overages because they're getting so much

44:19

value. And I think that's the future of

44:21

the business is people are looking at it

44:23

going like I am. Well, if I'm paying

44:26

$600 and if you token max to 6,000 a

44:30

year, but this is a $500,000 piece of

44:34

software, I don't care. I'm still paying

44:35

somewhere between.1%

44:38

and 1% of what I would have paid 3 years

44:40

ago. Who cares?

44:43

>> Go for it. Um, so

44:45

>> yeah, what we're seeing is everything is

44:47

about moving moving fast these days and

44:49

and AI more AI usually lets you move

44:52

much faster. So the spend is usually

44:54

worth it.

44:55

>> Do your customers a final question for

44:57

you because I'm starting to see this now

45:00

where multiple people in the

45:01

organization try to solve the same

45:03

software problem and they're competing

45:06

with each other. So like this internet

45:08

I'm talking about, we built one for

45:10

Japan.

45:11

>> Yeah.

45:11

>> But somebody built the US one. So now I

45:13

have two pieces of software. So I said

45:15

to the two different people

45:18

or do we have did you guys fork each

45:20

other's code or they're like no we just

45:22

built two different lovable projects.

45:25

And I'm like is that the right thing to

45:28

do because you went faster and I had two

45:30

swings at bat two different intelligent

45:32

brilliant people making their version of

45:35

the software.

45:36

>> But you would never have done that

45:38

>> in the previous way of building

45:40

software. You would have one track of

45:41

software and you would be building

45:43

Franken software where you'd be trying

45:46

to get all the needs into it from the

45:48

two different groups. I Yeah, I I'm

45:50

actually a huge fan of very rapid

45:53

experimentation and I I have a story

45:56

where for a while I worked at a a place

45:59

called CERN where they do particle

46:01

physics. It's it's pretty here in

46:04

Europe, right? Uh and that's where I was

46:06

introduced to this concept of

46:07

co-opetition where they have two

46:10

actually quite isolated teams working on

46:13

the same um particle accelerator but

46:15

different places on it and then they

46:17

don't share the results until they

46:18

publish and that way they uh they can

46:22

kind of over time learn what's working

46:23

best in the different organizations but

46:25

you don't get stuck in a local minimum

46:27

and it's you know free markets work

46:28

extremely well because of competition

46:30

and they they they do that in academia

46:31

as well and now since the engineering is

46:34

less of the bottleneck. It's more the

46:35

question of what is the right thing to

46:37

build. I think it's a great thing to

46:39

have if you have the sufficiently many

46:41

humans right to do to try to attempt

46:45

solving the same problem in different

46:46

ways. And then if you do that on

46:48

lovable, what I like to do is I I take I

46:50

bring up a new project or one of the

46:51

projects and I I say, "Hey, can you go

46:53

and just check out this other one and

46:55

take this these three things that I

46:57

really like and and bring them bring

46:59

them over here and maybe even run an a

47:02

split test, run an experiment to see if

47:04

it's if it's improves improving the

47:06

metrics for for our customers we're

47:07

trying to serve.

47:08

>> Did you see somebody used Fable to build

47:10

Fortnite

47:12

>> and uh

47:12

>> I've seen the 3D some of the 3D games?"

47:14

Yeah.

47:15

>> Yeah. What is your take on, you know,

47:18

this latest version from Anthropic

47:19

Fable? I know they're a part or I assume

47:21

they're a partner. I don't know that.

47:22

>> Yeah, we use Fable as well as one of the

47:24

models.

47:25

>> What do you think of it in terms of

47:28

compared to the last generation faster,

47:30

better, both?

47:32

>> Yeah. Is it a massive step function?

47:35

Yeah.

47:35

>> What I've seen is that it can in the

47:38

first attempt create very sophisticated

47:41

things that look really good. Then when

47:43

as you're evolving right it's it's still

47:45

the same thing where you as a human you

47:47

have to think you often should be

47:49

planning together with your agent about

47:52

what is the right thing to do and and

47:54

that's more of that's again more of the

47:55

bottleneck uh whereas more intelligence

47:58

is on some tasks it's great yeah like it

48:01

creates really beautiful things 3D games

48:03

for example but on figuring what to what

48:06

to build figuring out figuring out what

48:08

are the right strategic directions or

48:10

experiments you should run to improve

48:12

outcomes for your business. That's um uh

48:15

that's not changing as fast is the

48:17

humans knowing how to use the tool to

48:19

get and to plug in all the right data to

48:22

be able to take the right decisions for

48:23

taking your product forward and to take

48:25

your business forward.

48:26

>> Um listen, I love the product, but even

48:30

more than I love the product and you as

48:31

a founder, I love the outcome. The

48:34

outcome for business is extraordinary.

48:35

So, anybody who's listening, Lovable is

48:39

absolutely worth your time. Don't wait.

48:41

Just put it on your corporate card and

48:43

start building. That's my message. Just

48:45

start building with Lovable. It's an

48:47

incredible product. And uh

48:49

congratulations on being reborn six

48:53

times cuz every 6 months you add 100

48:56

million in revenue it seems. And then

48:57

everybody says Lovable's dead because

49:00

the new foundation model is so good. But

49:02

you keep studying your customer and and

49:05

you keep somehow surviving and thriving.

49:07

So congratulations as an entrepreneur.

49:10

Thank you so much, Jason. I enjoyed that

49:12

chat. I hope you enjoy the rest of your

49:14

stay here in Paris.

49:15

>> It's pretty great. And the Palace of

49:16

Versailles is so impressive, huh? Uh

49:18

someday we'll be building this with

49:20

lovable and optimist robots. I

49:22

>> I'm looking forward to it. I'm going all

49:24

in.

49:39

I'm going all in.

Interactive Summary

The video features a two-part conversation. First, Pat Gelsinger discusses Intel's history, the strategic mistakes that led to its decline—specifically focusing on the shift away from technical leadership—and the critical role of foundries like TSMC. He also shares his perspectives on the semiconductor industry, supply chain risks regarding Taiwan, and the future of AI. Second, the founder of Lovable discusses the rise of AI-powered software development (often called 'vibe coding'), highlighting how his platform enables non-technical users to build functional, secure enterprise-grade software rapidly, effectively disrupting traditional software development models.

Suggested questions

5 ready-made prompts