Will Devin AI Take Your Job?

Web Dev Simplified
19 Mar 202412:35

Summary

TLDRThe video discusses the new AI tool, Devon, which has generated buzz for its software engineering capabilities. While Devon can learn to use new technologies, fix bugs, and even perform some real-world tasks, the video argues that it's not as revolutionary as it seems. Devon's abilities are showcased through a limited set of well-documented GitHub issues and it requires specific prompts to learn from resources. The video emphasizes that Devon is a tool to aid developers, not replace them, as it lacks the problem-solving skills and technical knowledge that human developers possess.

Takeaways

  • 🤖 Devon is a new AI tool developed by Cognition Lab, designed to mimic the functions of a software engineer, causing some concern among professionals.
  • 📈 Despite impressive claims, Devon's capabilities are not as overwhelming as they are portrayed, and it is important to analyze them critically.
  • 💡 Devon can learn to use unfamiliar technology by teaching itself using existing documentation, but this is not entirely autonomous learning.
  • 🔍 The AI can find and fix bugs, but it is not as autonomous as it seems; it requires specific prompts and does not actively seek out errors.
  • 📊 Devon's reported ability to solve 13.86% of GitHub issues is based on a limited sample and may not represent its full capabilities.
  • 🛠️ Devon's real-world job capabilities are showcased through carefully selected examples on platforms like Upwork, which may not be representative of its overall potential.
  • 📖 The AI's learning process is facilitated by specific instructions and existing scripts, rather than independent discovery and understanding.
  • 🐞 Devon's bug-finding process is more about writing and refining tests based on developer prompts, rather than independently identifying and fixing issues.
  • 🔢 The AI is not fast; tasks can take hours to complete, and it is not as efficient as other tools like ChatGPT or AI Code Pilot.
  • 🔧 Devon is best seen as a tool to assist developers by speeding up workflows and handling tedious tasks, rather than replacing the need for human problem-solving skills.

Q & A

  • What is Devon and who created it?

    -Devon is a new AI tool designed to act and work like a software engineer, created by Cognition Labs.

  • How much funding has Devon raised according to the script?

    -Devon has raised $21 million in funding.

  • What are some of the capabilities of Devon mentioned in the script?

    -Devon is capable of learning how to use unfamiliar technology, finding and fixing bugs autonomously, and accomplishing real-world jobs on platforms like Upwork.

  • What is the 'thiswe bench' and what does it measure?

    -The 'thiswe bench' is a benchmark used for testing AI against GitHub issues, specifically looking at how well the AI can address issues in 12 popular Python repositories.

  • According to the script, what percentage of GitHub issues can Devon solve?

    -Devon is able to accomplish 13.86% of GitHub issues, based on the 'thiswe bench' benchmark.

  • Why is the claim that Devon can solve 13.86% of GitHub issues considered misleading?

    -This claim is misleading because it only considers a very small subset of issues from 12 Python repositories with exceptionally well-documented and structured issues, not the entirety of GitHub.

  • What does the script suggest about Devon's ability to learn from resources like blog articles?

    -While Devon is said to learn from blog articles and resources, the script suggests that its ability to do so may be limited, and in the example given, it largely relied on existing scripts and instructions rather than generating new knowledge.

  • How does Devon's performance in writing tests and finding bugs compare to human developers?

    -Devon can write tests and identify bugs through that process, but it requires specific instructions to do so. Its ability to autonomously find and fix bugs is not as advanced as it might initially appear.

  • What is the significance of Devon's performance on Upwork tasks according to the script?

    -Devon's ability to accomplish work on Upwork, particularly tasks involving the implementation of existing AI models, is highlighted as impressive. However, these tasks are carefully selected and do not represent the full spectrum of freelance work available.

  • What is the main argument against the fear of Devon replacing software engineering jobs?

    -The script argues that while Devon is a powerful tool, it cannot replace the core problem-solving skills and creative thinking of software engineers, highlighting that AI tools are meant to empower rather than replace human developers.

Outlines

00:00

🤖 Introduction to Devon AI and Addressing Concerns

This paragraph introduces Devon, a new AI tool that has been creating a buzz on social media platforms like Twitter and YouTube. The speaker, Kyle, aims to address concerns that Devon might replace software engineers' jobs. He explains that after researching and analyzing the claims made about Devon, he believes the AI is not as intimidating as it's portrayed. Kyle plans to discuss what Devon can and cannot do, debunking some myths around its capabilities.

05:02

💡 Analyzing Devon's Marketing and Real Capabilities

In this section, Kyle scrutinizes the marketing strategies of AI companies like Cognition Lab, the creators of Devon. He points out that the company's blog article and other promotional materials highlight the best-case scenarios to attract funding. The speaker expresses skepticism about the claim that Devon can solve 13.86% of GitHub issues, noting that this figure is based on a small, cherry-picked subset of data. He emphasizes the importance of evaluating these claims critically and understanding the limitations of AI in real-world scenarios.

10:04

🔍 A Closer Look at Devon's Learning Process and Bug Fixing

Kyle delves deeper into specific capabilities of Devon, such as its ability to learn from external resources and fix bugs in code. He critiques the way these features are presented in promotional videos, arguing that they might be misleading. For instance, while Devon can generate code based on instructions from a blog post, it doesn't demonstrate true self-learning across all situations. Similarly, its bug-fixing abilities are more about writing tests that fail and then adjusting the code to pass those tests, rather than independently identifying and fixing bugs in existing code.

🚀 Devon's Real-World Application and Speed

The speaker discusses Devon's application in real-world tasks, such as solving problems on Upwork, but notes that the tasks chosen are carefully selected to showcase the AI in the best light. Kyle also highlights that Devon operates at a slower pace compared to other AI tools, taking hours to complete tasks. He emphasizes that while Devon can automate certain coding tasks, it still requires technical knowledge to use effectively. Kyle concludes that Devon is a tool to assist developers rather than replace them, as AI is currently incapable of the complex problem-solving required in software engineering.

Mindmap

Keywords

💡Devon AI

Devon AI is an artificial intelligence tool developed by Cognition Labs, designed to perform tasks similar to those of a software engineer. In the video, it is discussed whether Devon AI can replace human software engineers and the capabilities it claims to have, such as learning to use unfamiliar technology and fixing bugs autonomously. The video aims to demystify these claims and provide a balanced view of the tool's potential and limitations.

💡GitHub

GitHub is a web-based hosting service for version control and collaboration that allows developers to store and manage their code repositories. In the context of the video, Devon AI's capabilities are evaluated based on its ability to solve issues on GitHub, with a claim that it can address 13.86% of GitHub issues. However, the video clarifies that this percentage is derived from a limited and well-documented subset of issues, which may not represent the full scope of real-world coding challenges.

💡Unit Tests

Unit tests are a type of software testing that focuses on individual components or units of code to determine if they are fit for purpose. In the video, it is mentioned that Devon AI can write code that passes unit tests associated with specific GitHub issues. However, passing these tests does not necessarily mean the code is perfect or optimal; it only means the AI's code meets the predefined criteria set by the tests.

💡Bug Fixing

Bug fixing is the process of correcting errors, flaws, or faults in software code. In the video, it is suggested that Devon AI can find and fix bugs autonomously, but the video host argues that this claim is misleading. Instead, the AI assists in the process by writing test cases and identifying where the code does not meet the test criteria, which can lead to the discovery and correction of bugs, but it is not an autonomous bug-finding process.

💡Self-Learning AI

Self-learning AI refers to artificial intelligence systems that can acquire knowledge or skills without being explicitly programmed. In the video, Devon AI is presented as having the ability to learn from blog articles and resources, but the video host questions the extent of this capability, as the AI seems to follow specific instructions and relies on existing scripts rather than independently learning from the content.

💡Upwork

Upwork is a platform that connects freelancers with clients who need specific tasks completed. In the video, Devon AI is shown completing a task from Upwork, which is used as an example to illustrate the AI's potential to perform real-world jobs. However, the video host points out that the task was carefully selected to showcase the AI's strengths and may not represent the full range of tasks that could be automated in this way.

💡Software Engineering

Software engineering is the application of engineering principles to software design, development, testing, and maintenance. In the video, the concern is raised that AI tools like Devon might replace software engineers. However, the video host argues that while AI can assist with certain aspects of software engineering, such as automating repetitive tasks, it cannot replace the core skills of a software engineer, including problem-solving and critical thinking.

💡AI Tool

An AI tool refers to software or a system that utilizes artificial intelligence to assist with tasks or decision-making processes. In the context of the video, Devon AI is presented as a tool for software engineers and developers, designed to help streamline and enhance their workflow. The video emphasizes that AI tools like Devon are meant to empower developers, not replace them, by making certain tasks easier and more efficient.

💡Funding

Funding in the context of the video refers to the financial resources provided to a company or project, often to support research, development, or expansion. Cognition Labs, the creators of Devon AI, have reportedly raised $21 million in funding, which the video suggests may be linked to the marketing and hype surrounding the AI tool to attract further investment.

💡Problem Solving

Problem solving is the process of finding solutions to difficult or complex issues. In the video, it is emphasized that while AI tools like Devon can automate certain tasks, the core skill of a software engineer is their ability to think critically and solve problems, which AI is currently not capable of replicating. This highlights the importance of human intelligence in software development and innovation.

💡Technical Knowledge

Technical knowledge refers to the understanding of technology, its principles, and its application. In the video, it is stressed that using AI tools like Devon AI requires a certain level of technical knowledge to effectively interact with and guide the AI. The video suggests that without this foundational understanding, users may struggle to apply the AI's output to practical scenarios.

Highlights

Devon is a new AI tool by Cognition Lab that's causing a buzz for its potential to work like a software engineer.

Despite the hype, Devon may not be as revolutionary or threatening to software engineering jobs as some think.

Devon has raised $21 million in funding, highlighting the significant interest in its capabilities.

One of Devon's touted capabilities is learning to use unfamiliar technology through existing resources.

Devon's bug fixing feature is shown to be less autonomous and more limited than initially suggested.

Devon's real-world job accomplishment on Upwork is highlighted, but with a note on its selective showcasing.

A benchmark claims Devon can solve 13.86% of GitHub issues, but this is based on a specific, small dataset.

The dataset for the benchmark consists of 12 popular Python repositories and 2300 issues with associated pull requests.

Devon's self-learning capability through blog articles and resources is questioned based on the detailed prompting required.

The process of Devon writing tests and finding bugs is more iterative and requires specific prompts from the developer.

Devon's execution of real-world tasks, such as on Upwork, is not as quick or seamless as might be expected.

Devon is viewed more as a tool to aid developers rather than replace them, emphasizing the importance of human problem-solving skills.

The video concludes that Devon, while impressive, is not a threat to software engineering jobs due to the core skills required in problem-solving and creativity.

Devon's potential is seen in empowering developers, making certain tasks easier, rather than in taking over their roles.

The analysis stresses that understanding and interpreting complex problems remain a uniquely human skill outside Devon's current capabilities.

Transcripts

play00:00

if you've been on Twitter or YouTube

play00:01

over the last week you've definitely

play00:03

heard of Devon the brand new AI tool

play00:05

that supposedly acts and works just like

play00:07

a software engineer and a lot of people

play00:09

are worried that this is going to be the

play00:11

thing that takes over your job as a

play00:12

software engineer and there's a lot of

play00:14

really impressive claims that Devon is

play00:15

making but how true are they actually

play00:18

and how impressive is this AI tool I've

play00:20

gone through I've done the research read

play00:22

the papers looked at all the different

play00:23

claims that they're making and I really

play00:25

think Devon is not nearly as impressive

play00:27

or scary as people are making it out to

play00:29

be and in this video I kind of want to

play00:30

talk about what Devon is what it

play00:32

actually can accomplish and some of the

play00:33

things that it really cannot

play00:37

do welcome back to web def simplified my

play00:40

name is Kyle and my job is to simplify

play00:42

the web for you so you can start

play00:43

building your dream project Center and

play00:44

today we're going to be talking about

play00:46

cognition lab's newest AI which is Devon

play00:48

and this is pretty much a brand new

play00:49

company that really hasn't released

play00:51

anything at all before until releasing

play00:53

this Devon AI now they put out a Blog

play00:56

article which I'm going to link in the

play00:57

description of this video and this blog

play00:58

article goes through quite a few

play01:00

different things about Devon what it's

play01:01

capable of what it can all do and really

play01:03

is showcasing all of the best case

play01:05

scenarios for Devon because they want

play01:07

this to look as good as possible and

play01:08

that's because most of the time these AI

play01:10

companies what they're trying to

play01:11

accomplish is actually getting tons and

play01:13

tons of funding if we actually scroll to

play01:15

the top of this page you can see that

play01:16

they've already raised $21 million in

play01:18

funding pretty much immediately from

play01:20

announcing this and all of that stuff

play01:21

going along with this so really the goal

play01:23

of these types of blog articles and all

play01:25

this information is to really drum up as

play01:27

much hype as possible to get as much

play01:28

funding as possible in into these

play01:30

particular AIS so they want it to look

play01:32

as good as possible on paper now there's

play01:34

a few different things I want to talk

play01:35

about in this video that specifically

play01:36

are the things people are most scared of

play01:38

so if we scroll down to this Devon's

play01:39

capabilities there's a bunch of

play01:40

different videos that we can go through

play01:42

that talk about the different things

play01:43

Devon can do and I want to focus on some

play01:44

of the main ones and why they're maybe

play01:46

not as scary as you think the first one

play01:47

here is that Devon can learn how to use

play01:49

unfamiliar technology this one is scary

play01:51

to a lot of people because the AI

play01:53

essentially can teach itself using

play01:54

existing blog articles videos

play01:56

documentation and so on which sounds

play01:58

really scary but honestly we'll deep

play02:00

dive into this it's not that bad another

play02:02

thing that we want to talk about is how

play02:03

it can actually find and fix bugs for

play02:05

you autonomously which is very

play02:07

misleading compared to what they

play02:08

actually do in the video again I'll dive

play02:10

deeper into why this is not nearly as

play02:12

scary as they make it out to be

play02:13

especially based on the video that they

play02:14

show you and then finally here if we go

play02:16

down a little bit further we can see

play02:18

that Devon is actually able to

play02:19

accomplish Real World jobs on epor which

play02:21

is again something that's really scary

play02:22

for people because it's like replacing

play02:24

essentially jobs that people could do

play02:26

but again this may not be as scary as

play02:27

you think it is now if we scroll all the

play02:29

way down to the bottom here you may see

play02:30

this chart this is probably something

play02:31

you've seen if you've heard people talk

play02:33

about Devon and essentially it's saying

play02:34

that Devon is able to accomplish 13.86%

play02:37

of GitHub issues and that's how a lot of

play02:40

people present it but essentially it's

play02:42

just using thiswe bench which is

play02:44

essentially a paper a benchmark for

play02:46

testing AI against GitHub issues and if

play02:48

we go to the actual site for this you'll

play02:50

notice that this is actually much less

play02:52

of a scary thing than people think they

play02:54

may think that okay it can solve

play02:55

essentially what is it 13.8% of all

play02:58

GitHub issues but really what this does

play03:00

is it takes just 12 GitHub repositories

play03:03

if we scroll all the way down here you

play03:04

can see it's 12 popular python

play03:06

repositories and it's only pulling 2300

play03:09

different poll request issues so the way

play03:11

that this works is it takes 2300 issues

play03:14

and the associated poll request that was

play03:16

generated for that issue and each of

play03:18

these poll requests has test data that

play03:20

was written for it for unit test and in

play03:22

order to be considered passing for the

play03:24

AI model all it has to do is write code

play03:26

that passes the unit test that were

play03:28

written to go along with that P R it

play03:30

doesn't actually mean that the code is

play03:31

100% correct or that it does things

play03:33

exactly like it's supposed to it just

play03:35

has to pass those unit tests which is

play03:36

generally a good idea to say that the

play03:38

code is most likely correct now if we go

play03:40

ahead and we look at an example of one

play03:42

of the issues that is used inside of

play03:44

this data set you'll see that this is an

play03:45

issue for some python library for

play03:47

something where new lines were being

play03:48

added in wrong places and you'll notice

play03:50

something really important about this is

play03:52

that the issue is very well documented

play03:54

you can see here is exactly what I

play03:55

searched for here is exactly what's

play03:57

happening you can see the expected

play03:59

Behavior what the observed Behavior

play04:01

should be how to reproduce this all the

play04:03

different stuff with versioning

play04:04

configuration files I mean this is an

play04:05

incredibly well-written issue much

play04:07

better than 99% of GitHub repositories

play04:10

out there and this is actually a

play04:11

recurring theme between pretty much all

play04:13

these different GitHub issues that are

play04:14

tested they have very good documentation

play04:16

in the issue side of things now if we

play04:18

look at the poll request that was

play04:19

submitted by an actual user this is not

play04:21

generated by AI you notice that the

play04:23

amount of files changed was 10 it's not

play04:24

a huge amount of data that was changed

play04:26

and if we go all the way down to the

play04:27

test you can see that this person wrote

play04:28

a few different test cases inside of

play04:30

here so if we look at a few of these

play04:32

different tests you can see there's just

play04:33

a couple tests that are being written

play04:34

and modified so this is essentially what

play04:36

the data is being test on is these like

play04:38

two or three different test cases that

play04:39

were added or modified so really as long

play04:41

as the AI model is able to actually

play04:43

correctly write some code that passes

play04:45

these tests that's the only thing that's

play04:46

being checked on but in general that's a

play04:47

pretty good indicator that they were

play04:49

able to solve the problem and it's still

play04:50

impressive that they're able to solve

play04:52

essentially 133% of these different

play04:53

problems but another thing to worry

play04:55

about here is if we scroll down you'll

play04:57

notice that Devon was evaluated on a

play04:58

random 25% % subset of the data now I'm

play05:01

not sure why they decided to go with

play05:03

only 25% of the data instead of doing

play05:05

100% of the data it makes me a little

play05:08

bit concerned because since there's no

play05:09

way for us to actually test with Devon

play05:11

right now since it's a closed off system

play05:13

currently it's not open to the public

play05:14

it's a little bit scary for me to think

play05:16

maybe they kind of randomly chose 25%

play05:19

until they got a 25% that gave them this

play05:21

good number for their announcement to

play05:22

try to raise money they could have just

play05:24

continually tested a random 25% until

play05:27

they landed on a random 25% that gave

play05:29

them the best best possible number

play05:30

because obviously some issues are going

play05:32

to be easier than others to solve so

play05:34

it's a little bit strange they didn't do

play05:35

it with 100% I don't know if there's

play05:36

certain resource constraints or if there

play05:38

was a different data set they used or

play05:39

what it was but it would be much more

play05:41

comforting to actually see that they did

play05:42

this on 100% of the data instead of only

play05:44

25% of it especially because like I said

play05:47

there's only 2,300 issues so doing 25%

play05:50

versus 100% is not that big of a

play05:52

difference so if you see this type of

play05:53

chart being thrown around where it's

play05:54

like they can solve 14% of all issues on

play05:56

GitHub that's very misleading it's 14%

play05:59

of issues ues in a very small subset

play06:00

across a very few select repositories

play06:03

that have very good documentation and

play06:05

very good issue support now the other

play06:07

things I talked about one thing is that

play06:08

this AI can learn for itself this is the

play06:10

video that they mentioned that

play06:11

specifically that the AI can actually

play06:13

learn from blog articles and resources

play06:14

out there so in this particular video

play06:16

this person is asking Devon they're

play06:18

pasting in a link to a Blog article and

play06:19

they're saying hey this blog article

play06:21

says that it can do X Y and Z and it

play06:23

even mentions in the blog article a

play06:25

script that you can use to do this

play06:27

that's what they tell Devon and they say

play06:28

hey can you set this up and generate

play06:30

images for me with these specific

play06:32

criteria so if we go over to that blog

play06:34

article at the very bottom you'll see

play06:36

that it has this try it-yourself section

play06:38

and it even has a link to a GitHub

play06:39

repository with that script if we open

play06:41

up that script you can see right here is

play06:43

the GitHub repository with all the

play06:45

information you need to be able to set

play06:46

this up it even tells you the exact code

play06:48

you need to use obviously it has the

play06:50

script files and everything so

play06:51

essentially all the code to do this is

play06:53

already written it's just giving you

play06:54

instructions on how to get set up with

play06:56

that so Devon's not really writing too

play06:58

much custom code it's just mostly

play07:00

following these instructions that are

play07:01

set up in this blog article and set up

play07:03

in this GitHub repository and it's able

play07:05

to generate these things based on the

play07:07

code that's already been written by

play07:08

other people and I noticed something

play07:10

really specific about this prompt they

play07:12

give it they specifically in the prompt

play07:13

say here's the blog article and they

play07:15

mention that there's a script in the

play07:16

blog article that is supposed to be used

play07:18

to generate those things so they're

play07:20

specifically telling this AI hey look

play07:22

for this script inside this blog article

play07:24

they maybe ignored everything else in

play07:26

the blog article went straight to the

play07:27

script and looked at this actual GitHub

play07:29

reposit itory with all the information

play07:30

and code to be able to do what it needs

play07:32

to do so it says that it can teach

play07:34

itself based on these different things

play07:35

and sure there may be some degree of

play07:37

that to it but the fact that they had to

play07:39

specifically prompt telling it where the

play07:41

script was telling it where the blog

play07:42

article was and having that blog article

play07:44

pretty much already have all the code

play07:46

inside of it makes me a little bit leery

play07:47

saying that it can really learn for

play07:49

itself in all situations it seems rather

play07:51

Limited in its capabilities in this

play07:53

regard at least based on this particular

play07:55

video example now the next one that I

play07:57

think is kind of scary for a lot of

play07:58

people is that this AI is able to find

play08:00

and fix bugs in your specific code and

play08:03

if you go through and that you watch

play08:04

this video you'll realize that it's

play08:06

really actually not finding and fixing

play08:08

these bugs for you so if you watch this

play08:10

video essentially what happens is this

play08:11

guy wrote some particular code to do

play08:13

something inside of his repository and

play08:15

he wrote that code but he didn't want to

play08:17

write any test cases for that code so

play08:19

there's no test at all for this code and

play08:20

he comes to Devon and he says hey Devon

play08:22

I would like you to write a test for

play08:24

this code it's specifically asking in

play08:26

the prompt I would like you to write

play08:28

test for this particular code and it's

play08:30

going to write out that test case and

play08:32

what happens is that he goes back and

play08:34

forth a couple times with Devon asking

play08:36

it to write more and more test based on

play08:37

more specific things and finally Devon

play08:39

writes a test that actually fails and

play08:41

Devon isn't necessarily finding this bug

play08:44

per se he's telling it to write test

play08:46

then Devon is going ahead and it's

play08:47

writing out these test and in the

play08:49

process of writing out the test that

play08:51

this developer specifically told Devon

play08:52

to write out it is then finding that

play08:54

these tests do not pass now the cool

play08:56

thing about Devon in this regard that I

play08:58

will give a credit for is that when when

play08:59

it finds this bug in the code

play09:01

essentially it says hey this test does

play09:02

not pass it actually goes through and

play09:04

finds where that bug is in the code to

play09:05

make the test pass and is able to solve

play09:08

the bug which is essentially one line of

play09:09

code that needs to be added to the

play09:10

actual thing as you can see right here

play09:12

on line 36 he adds this one single line

play09:14

of code and that essentially fixes the

play09:16

bug so Devon is able to go through it's

play09:17

writing these tests and it's finding the

play09:19

bug it's really cool but as you can see

play09:21

it's not just looking at a code

play09:22

repository and saying hey I found the

play09:23

bug for you instead it's kind of a very

play09:25

step-by-step process of hey write these

play09:27

tests for me this test failed so

play09:28

obviously there must be a bug it's a

play09:30

very cherry-picked example and they're

play09:32

really kind of blowing it out of

play09:33

proportion a little bit with the

play09:34

language they're using it's not

play09:36

necessarily finding bugs in your code

play09:37

it's just writing these tests and

play09:39

through that process happens to stumble

play09:40

upon the bug now the last one I want to

play09:42

talk about is honestly the one that is

play09:43

probably the most impressive and that is

play09:45

that Devan is able to accomplish work on

play09:47

upwork so if we look at this particular

play09:48

upwork task obviously they very much

play09:50

cherry-picked it they chose the one

play09:51

thing that is obviously going to work

play09:53

for them there's probably hundreds of

play09:54

upwork examples that do not work for

play09:56

them but this one is very simple for

play09:58

them because essentially all that this

play09:59

person is asking is hey all I want you

play10:01

to do is to take this model that already

play10:03

exists and I want you to be able to

play10:04

implement it and use it for me an AI

play10:06

model specifically so in this video

play10:08

essentially the person goes through and

play10:09

they tell Devon hey here's this thing

play10:11

this model that I want you to implement

play10:12

and start using and it goes through and

play10:14

it implements that model and it starts

play10:15

using the information from it and it

play10:17

ends up generating some results now one

play10:19

important thing to note about pretty

play10:21

much everything that Devon is doing is

play10:22

that it's not particularly fast this

play10:24

example for this upwork thing I think

play10:26

took about two maybe 3 hours to actually

play10:28

accomplish and a lot of the these other

play10:29

things are taking an hour two hours to

play10:31

actually run through and generate this

play10:32

code so it's not like chat jpt or AI

play10:35

Code Pilot or something like that where

play10:36

it's really quickly giving your

play10:37

responses this is a relatively slow

play10:39

process and it might be very iterative

play10:41

where you're working directly with it

play10:42

trying to help prompt it along which is

play10:44

another reason why I think that you

play10:45

shouldn't really be super worried while

play10:47

it can do these really cool things where

play10:48

it generates some code based on

play10:50

different GitHub repositories or

play10:51

articles which is really cool to see

play10:53

it's something that still requires

play10:55

technical knowledge in order to use if I

play10:57

were to give my wife this tool and tell

play10:58

her hey you can use this to solve upwork

play11:00

problems or something like that she

play11:02

would maybe be able to solve some really

play11:03

simple things but as soon as that Devon

play11:05

ran into a snag or didn't really know

play11:07

what to do she would obviously be

play11:08

completely underwater not know where to

play11:10

go because she doesn't have that

play11:11

technical background so you still need

play11:13

those problem solving and technical

play11:14

skills in order to actually use a tool

play11:16

like this and I keep using the word tool

play11:18

because really this is a tool this is

play11:20

something that software engineers and

play11:21

developers are going to be able to use

play11:23

to speed up their coding workflow maybe

play11:25

make certain things easier for them

play11:26

maybe make some tedious tasks not be

play11:28

something that you need to manually do

play11:30

just like things like AI autocomplete

play11:32

like chat GPT and co-pilot have made

play11:34

doing certain things in coding a lot

play11:35

easier they haven't replaced your job

play11:37

they just modified how you work and made

play11:39

certain things easier I think Devon is

play11:41

just another example of a tool that's

play11:43

going to make actually working in

play11:44

programming a little bit easier it's

play11:45

going to clean up certain things for you

play11:47

make certain learnings a little bit

play11:48

easier but the actual knowledge of being

play11:50

a developer where you actually need to

play11:52

think about how to solve real world

play11:53

problems and you to develop custom

play11:55

solutions to complex problems and just

play11:57

be a problem solver that is something

play11:59

that AI is really not capable of

play12:00

replacing currently and something I

play12:02

don't think it'll be able to replace in

play12:03

the future these tools are really cool

play12:05

and they have a lot of potential but

play12:07

really their potential is to empower you

play12:08

as a developer and not to replace you

play12:10

now don't get me wrong I think these

play12:12

tools are really impressive and really

play12:14

cool but if you're worried about Devon

play12:15

replacing your job you really don't have

play12:17

to worry about it because you as a

play12:18

developer knowing how to think like a

play12:20

programmer are the core skills you have

play12:22

and being able to write out like code

play12:24

for certain things is not your core

play12:25

skill it's your ability to problem solve

play12:27

and so on that these AI tools really

play12:29

struggle with and are probably never

play12:30

going to be able to replicate now with

play12:32

that said I really hope you enjoyed this

play12:34

video and have a good day

Rate This

5.0 / 5 (0 votes)

الوسوم ذات الصلة
Devon AISoftware EngineeringAI CapabilitiesTech IndustryGitHub IssuesCode TestingLearning TechnologyUpwork TasksProgramming ToolAI vs Human
هل تحتاج إلى تلخيص باللغة الإنجليزية؟