HomeVideos

Will AI REPLACE Software Developers..?

Now Playing

Will AI REPLACE Software Developers..?

Transcript

212 segments

0:00

Software developers in the US get paid

0:02

around $113,000 to $200,000 per year

0:06

with a median at around $150,000.

0:08

While the US government actually puts

0:10

the range closer to $132,000

0:13

compared to the Stack Overflow survey,

0:16

other countries like Australia, Canada,

0:18

UK, and Germany all fall behind the US

0:21

when it comes to wages for developers.

0:23

But when we look at job postings across

0:25

countries, Australia and Canada are

0:28

actually showing stronger numbers in

0:30

comparison to preandemic levels. And

0:33

meanwhile, the tech industry overall is

0:35

still recovering from the massive layoff

0:38

that started around the end of 2022 to

0:41

early 2023. And as the industry is still

0:44

recovering, the demand shifted away from

0:46

pure software developer roles to machine

0:49

learning and data engineering roles as

0:51

AI becomes more dominant. All of this

0:54

points back to the reality that while

0:56

there are 47 million developers in the

0:58

world, more than half of the developers

1:00

are in the age bracket of 18 to 34 years

1:03

old. And that is the exact demographic

1:05

for software developers that are

1:07

suffering the most when we look at the

1:09

headcount for current employment in the

1:11

industry. Welcome to kale writes code

1:13

where every second counts. Quick shout

1:15

out to Cotlin sponsoring this video.

1:16

More on them later. You probably have

1:18

seen this chart from Indeed hiring lab

1:21

before where it shows you an index of

1:23

software developer job postings across

1:25

time. But unfortunately there's a huge

1:28

misunderstanding when it comes to this

1:29

very chart. The chart here shows you 100

1:32

in the y-axis as a prepandemic level

1:35

baseline anchored in February 2020. And

1:38

relative to that point, we measure the

1:41

variance at each data point adjusted

1:43

with seasonality. In other words, around

1:46

February 2022 where the index showed a

1:48

value of 234, which means even in

1:52

consideration of trailing three-year

1:54

seasonality was about 134% higher than

1:57

the baseline. Meaning here we hire 24

2:01

people as opposed to hiring 10 people

2:03

for example. Now when we fast forward

2:05

from this peak to today, the most recent

2:08

data point shows that the US is at 69,

2:11

the UK is at 63, Germany at 58, Canada

2:15

at 78, and Australia at 122. So what we

2:19

are seeing here in the US is a slow

2:21

recovery towards the quote unquote

2:24

normal baseline at 100 in comparison to

2:27

February 2020. Now when we overlay this

2:30

with major flagship models starting with

2:32

GPT 3.5 in November 2022 that launched

2:35

ChachiPT to the world GBT4 in March 2023

2:39

and the first commercial reasoning model

2:42

01 announced in September 2024 followed

2:45

by the Deepseek moment that happened in

2:47

January 2025 along with many other

2:50

breakthroughs like Sonnet 3.5, Opus 4,

2:53

Gemini 2.5 and Gemini 3 all played a big

2:56

part in the industry. We also have many

2:58

coding agents mainly in 2025 that took

3:02

these models to disrupt the software

3:04

development industry and tools like clot

3:06

code, open code and more recently openi

3:10

codeex app really started to poke at the

3:12

industry whether we really needed all of

3:15

47 million developers that we have

3:17

currently in the world. So as you can

3:19

see there's a bit of a tugofwar between

3:21

where the baseline should be now that AI

3:24

is changing the industry. In other

3:26

words, is this an early sign that maybe

3:29

we will never reach back to the

3:31

prepandemic level and we now need a

3:33

different baseline than February 2020?

3:35

When we look at the Dora report, while

3:38

some early adopters of AI coding go all

3:40

the way back to 2022, a large majority

3:43

of developers actually started to use AI

3:46

coding at around 2024 and onwards, which

3:49

is pretty recent. And as the underlying

3:51

coding agents became more and more

3:54

complex, there's been this K-shaped

3:55

divergence between developers who

3:58

orchestrate their work entirely using AI

4:01

and developers who use AI merely as a

4:04

tool. And leading experts in the dev

4:05

industry like Uncle Bob started to

4:07

notice how when he goes from two agents

4:10

to three agents, he started to become

4:12

the bottleneck in coding. And similar

4:14

sentiment has been shared with Andre

4:16

Karpathy where he shared how he felt

4:18

behind as a programmer using AI coding

4:21

agents. As you can see, given this lag

4:23

in the AI adoption among developers, the

4:26

K-shaped adoption between coders who

4:28

embrace the tool and coders who say that

4:31

AI only moderately automates their task.

4:34

Now, all of this crescendos into the

4:36

split between entry-level developers who

4:39

are early in their career, who seem to

4:41

be suffering the most. And with that we

4:43

need to talk about cotlin. Intelligent

4:45

idea is an environment that lets you

4:47

build while working with whichever

4:49

coding agent that fits your workflow.

4:51

Whether it's codex app, clot code or jet

4:53

brains juni. I created a very simple

4:55

code that allows you to spin up a

4:57

backend system that could read customer

4:59

log documentation that I have here in

5:01

this file. And as easy as the code

5:03

looks, I can now use curl commands to

5:05

reach the endpoint to fetch information

5:07

contained in it. And now with their Juni

5:09

AI coding agent, you can easily use it

5:11

to continue coding by asking it to

5:13

further implement my project by adding a

5:15

new route that could access file by

5:17

file. Try out Cotlin's easytouse

5:19

back-end system and their Juni AI coding

5:21

agent that helps you ship products

5:23

faster. The common sentiment out there

5:25

is that AI will take away all

5:27

entry-level positions to start.

5:29

Enthropic CEO Dario Amade famously said

5:32

that in a few years 50% of entry-level

5:34

white collar positions will be impacted

5:36

by AI. While claims like this certainly

5:39

needs to be analyzed more thoroughly, it

5:41

does speak to at least some uncertainty

5:43

in the industry whether companies should

5:45

hire more developers, which is reflected

5:47

here where we're still behind the

5:49

prepandemic level. And looking at other

5:51

countries like Australia and Canada,

5:53

where they're nearing back to where they

5:55

used to be or even above the level in

5:57

Australia, the US still seems to be on

5:59

the fence about how hiring should look

6:02

like with AI in the mix. At the moment,

6:04

however, machine learning engineers saw

6:06

a nearly 40% jump in demand, data

6:09

engineers seeing 10% jump, while

6:11

front-end and mobile engineers actually

6:13

shrunk more than 5% going from 2024 to

6:17

2025. And meanwhile, the pace of how

6:20

fast AI is being used is not stopping.

6:22

According to the semi analysis report,

6:24

more than 4% of public repos in GitHub

6:27

use clot code, which goes to show how

6:30

fast AI is being adopted to those who

6:32

actually embrace it. And this kind of

6:34

acceleration will likely continue

6:37

causing the split between 52% of

6:39

developers who don't use AI agents while

6:42

the rest are trying to learn how to best

6:44

incorporate AI into workflow as fast as

6:47

possible. I think it's worth mentioning

6:49

why this K-shaped adoption is occurring

6:52

among developers. One of the biggest

6:53

components comes down to trust where a

6:56

large majority of developers simply

6:58

don't trust AI's response in their

7:01

coding needs. But this sentiment will

7:03

certainly improve as the underlying

7:05

model gets better in time. But the

7:07

biggest issue is when it comes down to

7:09

workflow. Just like how Uncle Bob

7:11

mentioned in his tweet, how when you go

7:14

from working with two agents to three

7:15

agents, he becomes a bottleneck. Coding

7:18

with AI, and I mean actually letting AI

7:21

do the majority of the work requires a

7:23

complete change in how you actually

7:25

work. And there's a big resistance when

7:28

it comes to this change. Using coding

7:30

agents like clot code and codex app is

7:32

vastly different than copying and

7:34

pasting code into a chat or even using

7:37

an extensionbased coding assistance like

7:39

client and rue. While client and rue

7:41

will assist in the actual implementation

7:44

task by task. Cloud code and codeex is

7:47

meant to abstract away the

7:49

implementation which changes the rule of

7:51

the game from coding to what's called

7:53

specdriven development or just

7:55

orchestrating between tasks. The codeex

7:57

app for example doesn't even show you

7:59

the code in the application and viewing

8:02

diff edits is done outside of the main

8:04

chat window. So given this underlying

8:07

change we're going through in terms of

8:09

AI adoption among developers lack of

8:11

trust in AI's response continual layoff

8:14

but hiring still being below the

8:17

baseline. Do you think this progression

8:19

will lead to AI replacing software

8:21

developers or do you think AI will

8:23

create even more demand for software

8:25

developers?

Interactive Summary

The software development industry is experiencing significant shifts in compensation, job demand, and the impact of AI. While US developers generally earn higher salaries than their global counterparts, job postings in the US are still recovering slowly towards pre-pandemic levels, unlike some other countries. The rise of AI has redirected demand from traditional software developer roles to machine learning and data engineering. This transition disproportionately affects younger, entry-level developers. A 'K-shaped divergence' in AI adoption is evident among developers, with some fully integrating AI into their workflows (spec-driven development) while others are hesitant due to a lack of trust and resistance to significant workflow changes. This evolution questions the future baseline for developer demand and the very nature of the developer's role.

Suggested questions

8 ready-made prompts