HomeVideos

Why my team is pushing back on AI

Now Playing

Why my team is pushing back on AI

Transcript

337 segments

0:00

If you're pushing AI to your team, they

0:02

have reasons to push back. For the first

0:04

time in 200 years, we have a technology

0:07

that watches your team in order to learn

0:10

how to replace them. This is not

0:12

paranoia. I run three companies with a

0:14

team of 140 people, and this is what I'm

0:17

seeing.

0:19

6 months ago, the conversation was AI

0:21

changes everything. Now, what I'm seeing

0:23

is people pushing back against it, and

0:25

it's coming from inside my own team.

0:27

Last week, one of my full stack software

0:29

engineer sent me this on Slack as a

0:31

response to my latest video on hand

0:32

coders being angry. The more you use AI,

0:35

the more you depend on it. If it gets

0:37

bad enough, it can lead to someone

0:39

letting a model do most of the thinking

0:41

for them. It's making people stupid, and

0:43

that is what is making people angry,

0:46

including me. That is someone using AI

0:48

daily to build software, experiencing

0:51

the discomfort in real time, and his

0:53

frustration is pointing at something

0:55

that nobody's explaining properly. So,

0:57

let me explain it.

0:59

You've heard the numbers. AI makes

1:01

engineers 10 times faster. AI doubles

1:04

your team's output. Most of that is just

1:06

vibes. Some of the numbers are real. The

1:08

best measured number I've seen is the

1:10

median productivity gain across hundreds

1:12

of software engineers, and that is 7.8%.

1:16

7.8%.

1:18

I guess it's better than nothing, but

1:19

it's a long way from 10x. I'm not

1:21

telling you AI is a dead end. I use it

1:23

daily across my three companies. I'm

1:25

just telling you what the measured

1:26

number actually is, and the operators

1:28

signing the checks are reading it in the

1:29

same way. One CTO told the Pragmatic

1:32

Engineer survey, quote, "It is hard to

1:35

keep our CFO supportive of investing in

1:38

these tools because the productivity

1:40

benefits have proven difficult to

1:41

conclusively prove. CFOs cannot prove

1:44

the gain, and the developers are feeling

1:46

that same number from their side." Of

1:48

the engineers who saw their peak AI gain

1:50

in one quarter, 66%

1:53

saw it drop in the next quarter. The

1:55

early win doesn't compound. it fades.

1:58

But the productivity boost isn't the

2:00

only thing AI is doing to us. Think

2:02

about how you get better at anything.

2:04

Repetition, struggle, the friction is

2:07

the training. When you outsource the

2:09

struggle to a model, you outsource the

2:11

thinking and the skill development. A

2:13

2025 MIT Media Lab study found exactly

2:17

that. Heavy AI use leads to measurable

2:19

cognitive atrophy in the people that use

2:22

it most. The researchers called it

2:24

cognitive debt. We're not just less

2:25

productive than the marketing says. We

2:27

might be eroding the skills that made us

2:29

valuable in the first place. So the

2:31

productivity gain is small, the skill

2:34

cost is real. And people are being told

2:37

their jobs depend on adopting it. This

2:39

is all pointing at something deeper.

2:43

Here's what nobody's clear about on why

2:44

people aren't on board with AI. For the

2:46

last 200 years, every major technology

2:49

has eventually made everyone richer. The

2:51

factory, the electricity, the car, the

2:55

internet. The owners always saw the gain

2:57

first, but the workers eventually caught

2:59

up. Wages went up, living standards went

3:01

up, the gain spread. But AI is the first

3:05

widespread technology where the owner

3:08

sees a productivity gain immediately,

3:10

and the worker often doesn't see a gain

3:12

at all. In many cases, the worker is

3:14

helping train the thing that will

3:16

eventually replace them. There's a video

3:17

doing the rounds that you might have

3:18

seen. Factory workers in some plants are

3:20

being asked to wear cameras while they

3:22

work. The cameras record every motion,

3:25

every decision. The data trains an AI

3:28

that will eventually replace them. These

3:30

workers are being paid to teach the

3:32

machine that will take their job. And

3:34

it's not just factory floors. Last year,

3:37

Mark Zuckerberg announced that Meta

3:39

would be putting recording software on

3:41

its engineers' computers, so the model

3:43

could learn from them. Weeks later, he

3:45

laid off 8,000 people. 8,000 engineers

3:48

cut frees roughly 4 billion a year.

3:51

Meta's AI spend this year is 135

3:54

billion. The maths tell you where the

3:56

bet is placed and it's not on the

3:58

people. That asymmetry has always

4:00

existed. What's new is the speed. In

4:02

1900, the factory worker saw the boss

4:05

get rich first and waited a generation

4:07

for their own share to follow. The

4:08

worker wearing a camera in 2026 sees

4:11

that gain go into their boss before

4:13

lunch. So when people say something

4:15

feels off about AI, they're not

4:17

imagining it. And here's where it gets

4:18

sharper. In March, Jensen Huang stood at

4:22

the stage at Nvidia GTC and told his

4:24

engineers that they should be spending

4:26

50% of their salary on AI tokens. Half

4:30

of their salary in addition to their

4:32

wages. Where do you think that money is

4:34

coming from? Not from end user revenue.

4:36

Quick one before I go on. If you find

4:38

this content useful, hit like,

4:40

subscribe, and give the video a hype. It

4:42

really helps.

4:44

The main issue people have with AI is

4:46

not this technology is bad. It's more my

4:48

boss is pushing this on me. They are

4:50

profiting from me using it and I'm not.

4:53

Look at how the layoffs are being

4:54

framed. Cloudflare CEO sent a memo

4:57

recently announcing he was laying off

4:59

20% of his workforce despite record

5:02

revenue. He called the people being laid

5:04

off the measurers. He labeled them as a

5:06

function and then he deleted that

5:08

function. You stop being a person and

5:10

you start being a job description that

5:12

AI can do. So people are asking

5:14

themselves a different question. Am I

5:16

not more valuable than ChatGPT with all

5:18

the judgment and experience that I've

5:20

built up? The data confirms what they're

5:22

feeling. A survey of 2,400 executives

5:25

and employees this year found 60% of

5:27

companies plan on lay off people who do

5:30

not adapt and embrace AI. The same

5:32

survey found that 48% of executives are

5:35

calling their own AI adoption a massive

5:38

disappointment. So people are being

5:39

forced into a tool on a threat of losing

5:42

their job where the return isn't clear

5:45

even to the people mandating it. Now,

5:47

zoom out. That's one extreme. Let's look

5:49

at the other. Uber rolled out Claude

5:51

code to 5,000 engineers and burned

5:54

through their entire 2026 AI budget in 4

5:58

months. Per engineer costs hit $2,000 a

6:01

month. And the AI companies that all

6:03

that money is flowing into, most of them

6:05

aren't profitable. Anthropic just

6:07

reported its first-ever profitable

6:10

quarter. It's the first time any major

6:13

AI lab hits profit. OpenAI isn't

6:16

expected to be profitable until 2029.

6:18

So, where is all this money actually

6:20

coming from? Nvidia recently agreed to

6:22

put a hundred billion dollars into

6:24

OpenAI, and OpenAI uses that money to

6:26

buy Nvidia chips. That's not a customer

6:29

relationship. That's Nvidia subsidizing

6:31

its own sales. Even Jensen Huang admits

6:34

it's fragile. In a leaked all-hands

6:36

meeting last November, the day after

6:38

Nvidia beat their earnings, he said, "If

6:40

we delivered a bad quarter, if we were

6:43

off by just a hair, if it just looked a

6:46

little bit quicky, the whole world would

6:48

have fallen apart." That is Nvidia's own

6:50

CEO. The whole world. Michael Burry, the

6:54

guy from The Big Short, says Nvidia is

6:56

like Cisco. Most people remember the

6:58

dot-com bubble as pets.com vaporware.

7:01

Burry's argument is that it was actually

7:03

Cisco. Cisco in 2000 was a real

7:06

profitable company whose equipment ran

7:08

the early internet. The bubble was that

7:10

the infrastructure got built years ahead

7:13

of demand. The technology was real. The

7:15

build-out was real. The market was just

7:18

way ahead of revenue. The demand for AI

7:20

is real. I see it inside my own

7:22

companies. The question is, how much of

7:24

it is organic and how much of it is it

7:26

Nvidia paying its own customers to buy

7:28

its own chips? So, the bubble is real,

7:30

but it's a financial bubble. The

7:32

technology underneath it is not. And

7:33

because we're so early in this, what AI

7:35

looks like inside my companies is

7:37

different from the marketing version.

7:39

Let me show you.

7:41

At We UC with our 20 engineers, the

7:43

productivity boost reality is probably

7:46

closer to seven to that 7.8% not the

7:49

10x. But I don't think this 7.8% is a

7:51

ceiling. I think it's the cost of being

7:53

early. Let me give you two examples. One

7:55

of how AI has worked for me and one how

7:57

it's not worked out well. A few months

7:59

ago, my coffee machine broke. It's an

8:00

integrated machine, complicated one.

8:02

Normally, I'd email the manufacturer,

8:04

wait for their response, probably call

8:06

them because they haven't responded to

8:08

my email, wait on hold, try to book a

8:09

service, get passed to different

8:11

departments, and eventually get through

8:13

to someone and and try and book a

8:15

service for somebody to come and see the

8:16

machine. The whole thing will probably

8:17

take me, I don't know, half a day's

8:19

work. Instead, I took a photo of the

8:21

machine that included the model number

8:23

and the serial number. I gave it to an

8:24

AI agent, in this case Perplexity

8:26

computer, and I told it what the problem

8:27

was and to go fix it. I genuinely

8:29

expected nothing to happen. The agent

8:32

read the model number from the photo,

8:34

found the manufacturer's service

8:35

partner, used my Gmail connector to

8:38

email them, waited to for replies, and

8:40

when they did, it kept going back and

8:41

forth communicating with them until it

8:43

came back to me with a list of

8:45

appointment options. I approved one of

8:47

them and a price, and the manufacturer

8:48

called me an hour later to confirm the

8:50

appointment. The engineer then turned

8:52

up, machine was fixed. End to end, they

8:54

probably spent five minutes on it. The

8:56

agent did the rest. Second example, and

8:58

this one is a bit messier. We built our

9:00

own AI code review bot. It reads every

9:03

merge request and it provides comments

9:05

through Claude. When it works well, it's

9:07

genuinely excellent. But last week it

9:09

ran 10 reviews and cost us about 100

9:11

quid. And on one of them, it recommended

9:13

to restrict its own permissions. Then on

9:15

the next run, it couldn't post comments

9:17

cuz it revoked its own access away. One

9:19

of my engineers described it as a

9:21

brilliant five-year-old with a a

9:23

doctorate and amnesia. The capability is

9:25

there, but the economics aren't quite

9:28

there yet. So, that's what AI actually

9:30

looks like up close in my world. One

9:32

clean win that saved me half a day, one

9:34

expensive bet still being tuned. The

9:37

7.8% is only cuz we're still learning.

9:41

This video sponsored by Palantir AI.

9:43

They do real-time translation that keeps

9:45

your voice. 60 plus languages translated

9:48

in under a second. Not a robot voice,

9:50

your cloned voice. And that's not a

9:52

small thing when you've grown up between

9:54

two languages like me. I'm half Spanish,

9:56

half English. I actually worked as a

9:57

translator when I was a teenager. So

9:59

this hits close to home for me. My dev

10:01

team is mostly based in Ukraine. Their

10:03

English is great, but when something

10:04

gets technical, they'll switch to

10:06

Ukrainian to explain it properly. And

10:07

Palantir handles that instantly both

10:09

ways. You can use it for online

10:11

meetings, broadcasts, in-person events,

10:14

or straight through their API. And

10:16

normally a human interpreter at a live

10:17

event would cost you about a grand a

10:19

day. This is a fraction of that, does

10:21

the job just as well, and doesn't get

10:23

tired. Scan the QR code or use the link

10:25

in the description and use my discount

10:27

code axelmollist30

10:29

to get 30% off and start your free 3-day

10:33

trial on me. Actually on them, but you

10:35

get the idea.

10:37

The people pushing back on AI, I get it.

10:41

They're not Luddites. They're seeing the

10:43

asymmetry. They're being asked to wear

10:45

cameras or have their screens recorded

10:47

so they can train the thing that's going

10:49

to replace them. And they're all feeling

10:51

the cognitive cost, the skill atrophy

10:53

that my own engineers are warning each

10:55

other about on Slack. And the people who

10:57

are deeply convinced that AI is going to

10:59

change everything, I get that too.

11:01

Because every time I see an agent do

11:03

something in a minute that used to take

11:05

me half a day to do, I see what they're

11:07

seeing. The technology is real. The

11:09

capability shift is real. It's just

11:12

smaller and slower than the marketing

11:14

version for now. Both things are true at

11:16

the same time. The bubble is real. The

11:18

technology is real. The frustration is

11:21

legitimate. The opportunity is

11:23

legitimate. There's a lot of AI noise,

11:25

but there far fewer real outcomes. How

11:28

are you seeing this play out? Is your

11:30

team resisting? And if they are, is it

11:32

the cognitive cost or the economic

11:34

asymmetry? This is what I talk about on

11:36

this channel. If this is the kind of

11:37

thing you want more of, hit like, hit

11:39

subscribe, give this video a hype.

11:42

Really helps. And if you want more of

11:44

this kind of thinking, the stuff that

11:45

doesn't fit in a video, what's actually

11:47

working inside my companies, what's

11:49

breaking, I share it in my newsletter

11:50

every week. Head over to axelmolisto.com

11:53

and enter your email to subscribe. Your

11:55

team's frustration is real. The

11:57

technology is not the issue. The issue

11:59

is the billions chasing what AI might do

12:02

tomorrow, not what it does today. And if

12:05

you've not seen what 6 months of AI

12:06

coding does to my dev team or did to my

12:08

dev team, that one's right here. See you

12:10

in the next one.

Interactive Summary

The video explores the friction between AI adoption and workforce sentiment. While the marketing claims massive productivity gains, real-world data suggests modest improvements, often paired with legitimate employee concerns regarding job displacement and cognitive skill erosion. The speaker distinguishes between the valid, transformative potential of the technology and the current financial bubble surrounding AI infrastructure investments.

Suggested questions

3 ready-made prompts