HomeVideos

Most Valuable Skill of 2026: Managing AI Agents

Now Playing

Most Valuable Skill of 2026: Managing AI Agents

Transcript

1137 segments

0:00

I don't think it's crazy to say that the

0:01

people who know how to run teams of AI

0:03

agents are going to be able to

0:05

outperform everyone else in this AI age

0:07

we're in. So, how do you actually run

0:10

teams of AI agents? What does this mean?

0:12

What's the stepbystep way to actually do

0:14

this? And what are the tools you need to

0:17

know like Devon AI to actually go and do

0:19

this? Well, on today's episode, I

0:21

brought on Ryan Carson, and he clearly

0:23

explains all of this for you. even gives

0:26

you a tour of his insane setup for how

0:30

he manages uh his AI agent. So, by the

0:34

end of this episode, you're going to

0:35

understand what cloud agents are, how

0:37

you can set up automations, how you can

0:39

create a software factory that creates

0:41

software 24/7, and you're going to be

0:43

able to understand it just really

0:45

clearly because he does such a good job

0:47

at explaining all this. So, enjoy the

0:49

episode. I'll see you at the end, and

0:51

have a creative [music] day.

1:00

Ryan Carson back on the pod by the end

1:02

of this episode. Ryan, what are people

1:05

going to get out of this?

1:06

>> So, you're going to do be able to do

1:09

three things really well. You're going

1:10

to be able to run cloud agents. You're

1:12

going to be able to do automations. Uh,

1:15

and you're going to be able to ship

1:18

faster. So whether you're a founder, a

1:20

soloreneur, a stay a stay-at-home

1:22

parent, you're just going to become an

1:24

agent pro by the time we're done.

1:27

>> Okay? Cuz I think a lot of people

1:29

listening to this might have they've

1:31

played with agents, cloud agents. Um,

1:34

but you're going to help them just get

1:36

the confidence basically to be world

1:38

class. You know, I think that's what I'm

1:40

trying to that's what I've been thinking

1:41

a lot about. It's like okay there's you

1:44

know a bunch of people who have played

1:46

with agents but how do we become

1:48

worldclass agent operators?

1:50

>> Yeah essentially you are a manager of

1:52

agents now. So what no matter what you

1:55

used to do, whether it was a people

1:56

manager, an IC, you are going to become

1:59

a manager of agents now and you need to

2:02

be the best in the world. And it doesn't

2:04

matter whether you're a VC, a founder,

2:06

uh an IC, a mom, a dad, like a college

2:10

student, you should manage agents and be

2:13

the best at it. And we're going to show

2:14

you some tips for that.

2:16

>> Okay. So where do we start?

2:18

>> Okay, so let me give some context,

2:20

right? So people understand where is

2:22

this coming from. So, I've been a

2:24

founder CEO for like 25 years. Um, uh,

2:26

I'm working on my fourth company now.

2:28

Um, at my, uh, last company, Treehouse,

2:31

which was acquired, we had, you know, I

2:34

think up to like 110 full-time

2:35

employees, taught a million people how

2:37

to code, you know, so I've done the

2:39

whole build organization thing and

2:40

manage organization thing. Um, and you

2:43

learn a lot about managing people on

2:44

that. Um, and now this startup which I'm

2:48

running it, I am one employee right now.

2:51

Um, so we've raised a seed round. We're

2:54

scaling really fast. Our revenue

2:55

probably is going to 4x this month. Um,

2:58

and I'm probably going to be hiring my

2:59

first employees. Um, we are essentially

3:02

an AI divorce agent for divorce firms.

3:05

So, uh, we we we do the the dirty topic

3:08

that no one seems to want to want to

3:10

tackle, which is family law. So, I've

3:11

learned a lot about how to scale me,

3:13

right? Um, and so I'm going to help

3:17

folks understand how do you manage a lot

3:18

of agents well? Um, how do you check the

3:21

work? How do you automate things? How do

3:23

you work from your phone? Um, you know,

3:25

I do almost 50% probably more of my work

3:28

from my phone. Um, and uh, it's pretty

3:32

wild. So, that's where we're going to

3:34

take you. And and and I will say as

3:36

well, like this is going to change every

3:39

3 to 6 months. Um, so, uh, we're going

3:43

to share a lot with you. Get your hands

3:44

dirty. Try it. Um, and, uh, the best way

3:47

by to learn is to do. Cool. Yeah, I'm

3:50

actually I'm particularly interested in

3:52

the phone stuff because I actually do

3:54

zero% of my stuff on the phone.

3:56

>> What? Yeah. Okay, let's [laughter] talk.

3:59

>> So, uh let me start by just showing you

4:01

well when I'm at my desk, what is the

4:04

world like? Right. So, right now I'm in

4:05

my home office. Um I I I I work from

4:09

Connecticut. Um and I do all my desk

4:12

work here and I've got this big 52-in

4:15

Dell monitor. Um, I used to have like a

4:16

couple monitors and I was like, screw

4:18

it. I just want a huge monitor. So, uh,

4:21

let me share my screen and, uh, all

4:24

right. So, what I do is I set up eight

4:28

screens on my monitor and, uh, I also,

4:32

uh, enjoy food, uh, and snacks as as I

4:35

code. Um, but the key is to have eight

4:38

things up at once because I have to

4:40

multitask a lot of agents at once. Um, I

4:44

also use a paper system to keep track of

4:46

some of my to-dos, which is a little bit

4:47

weird. I use the UG Monk system, which

4:50

is kind of fun. And I've got a killer

4:52

Razor mouse. Um, I was getting a lot of

4:55

wrist pain, actually. Um, so I decided

4:57

to go uh vertical mouse on that. Um, I

4:59

also uh have a button uh which actually

5:03

is connected to Whisper Flow. So, I

5:05

almost uh use Whisper Flow for all of uh

5:08

all of my stuff. So, I've got Slack in

5:10

the top left. That's where I get

5:12

notifications and things about what my

5:14

agents are doing or what is happening.

5:16

Um that that's the primary thing I use

5:18

Slack for. Uh and then what I do is I

5:22

lay out uh various other screens. So

5:23

I've got a one password always set up.

5:26

It's very important to keep your keys uh

5:29

safe, secure, and separated from the

5:33

agent. Right? So I've got all my prod

5:35

write keys in one password. I do not

5:38

give my agents uh prod keys. Um, so

5:41

production writing is dangerous, right?

5:43

And your agents will do something bad.

5:45

Um, and so you need to set up a system

5:47

where they uh ask you for the key when

5:50

they need to write to prod and then you

5:51

go into one password, you copy and paste

5:53

it into the session and you're both very

5:56

clear about what you're doing. So uh

5:58

that's one tip. Um, keep your keys

6:00

secure. And then I use Devon. So uh

6:04

Devon is is created by Cognition. I

6:06

think it's one of the best software

6:08

factories in the industry. It's not

6:10

cheap um but it's good. Um the things

6:13

I'm going to talk about today are are

6:14

not Devon specific. Uh but they do work

6:17

very well in Devon. And one of the keys

6:19

is cloud agents. Um then I usually have

6:22

two screens set up where I'm testing um

6:26

my app. It's just a lot of testing. And

6:28

then of course I've got X in the top

6:30

left and top right. And then on the

6:32

right I've got codeex um which we'll

6:35

talk a little bit more how I do most my

6:37

work in in cloud in Devon. Uh, and a lot

6:40

of that work, like we talked about, 50%

6:42

is probably on my phone. Um, and then

6:44

whenever I do desktop or whenever I'm

6:46

doing, uh, things locally, I'll do it in

6:48

codecs. Uh, usually that's in the bottom

6:51

right. So, that's kind of my when I'm at

6:54

my desk, uh, my setup, um, and what I do

6:58

when I'm here. But the truth is I do a

7:01

lot of work, you know, from this my

7:04

iPhone. This is my beautiful wife. Um,

7:06

uh, it's just I get a lot of stuff done.

7:09

You know, I I'll be in the shower and

7:10

I'm thinking, okay, I need to check on

7:12

that PR or maybe I want to land that PR,

7:14

right? You know, grab it, talk to Devon,

7:17

which is just done in a browser on my on

7:19

my mobile and I get a lot of stuff done

7:20

that way. So, that's my setup.

7:24

So I I keep hearing this that Devon is

7:28

is almost you know it's the most

7:30

powerful coding agent and you know can

7:33

you just for folks who haven't heard of

7:35

Devon or or who haven't played with it

7:37

like why is that what is going on? So,

7:40

um, so about 2 years ago, maybe two and

7:43

a half years ago, Devon came out and

7:44

they pitched it as this idea of like

7:46

it's a software engineer, right? And

7:49

honestly, it didn't work very well,

7:50

right? The the models were just not good

7:53

enough. And no matter how good the

7:54

harness was, the models just weren't

7:56

there. Um, and then fast forward to, you

7:59

know, 2026, um, the models are

8:02

definitely good enough. And when you

8:04

have a good harness that is cloud-based,

8:08

um, it's really good. So, think of it as

8:10

you've got your choices, right? So, if

8:12

you're using agents to build things,

8:14

you're probably using codecs, you know,

8:15

from OpenAI or using Cloud Code from

8:18

Anthropic or you're using one of the

8:21

indie, I call them the the indie uh,

8:23

agent harnesses. You've got AMP, you've

8:25

got Cursor, which is not independent

8:27

anymore, but sort of own owned by Elon.

8:31

Um, and then you've got cognition which

8:33

makes Devon. You've got factory uh as

8:36

another one as well. So you've got these

8:37

choices, right? And so I thought, okay,

8:41

I want to scale myself horizontally.

8:46

Like I want to be able to run as many

8:47

agents as I possibly can and I don't

8:50

want to be working on my laptop and

8:52

trying to figure out

8:55

which code is colliding, you know, which

8:58

work tree am I on? all a lot of

9:00

technical stuff that really

9:01

[clears throat] it's it keeps you from

9:03

shipping. Um, and you know, I know

9:06

there's a lot of different folks that

9:07

listen to the show. You might have

9:09

soloreneurs who are are are newer to

9:12

coding. They don't have computer science

9:13

degrees. They're not super technical,

9:15

but they're building things. Then you

9:16

may have, you know, software engineers

9:18

who are multiplying themselves 10 to

9:20

100x. They they they have deep

9:22

understanding of software and

9:23

architecture. And then you have founders

9:26

who are coding but are abstracting

9:28

themselves. and you have VCs who are

9:29

coding, you know. Um, but, uh,

9:33

everybody's going to learn a couple

9:35

skills. Um, and what's interesting is

9:37

I'll sort of, uh, zoom out for a second.

9:40

I think we all thought that engineering

9:43

and being technical was going away, but

9:46

actually what's happening is the more

9:48

you become a better agent manager, um,

9:50

actually the more technical you become.

9:53

uh and I I think it a good analogy is

9:56

that you are basically an engineering

9:59

manager right and so to be a good

10:02

manager of many agents you do need to

10:05

become technical right there's this

10:07

reality of you have to understand what

10:09

Postgres is you have to understand a

10:11

production environment versus a dev

10:13

environment you have to understand

10:14

migrations like but the truth is you'll

10:16

learn all that by using agents right and

10:20

so I am way more technical than I have

10:23

ever been in my whole life. Um, and so I

10:26

think the idea is become more and more

10:28

technical. Therefore, okay, so let's

10:29

back up. Why Devon? What is it? It's a

10:32

really good agent. They have uh their

10:35

cloud environment really nailed down. So

10:37

that's the first takeaway I want to talk

10:38

about today is cloud. Okay. Um, how can

10:42

you run more agents, get more done? Uh,

10:46

and the answer is you work in the cloud,

10:48

not on your local machine. Now,

10:52

for the folks that aren't super

10:53

technical, I'll sort of explain what

10:54

does that mean. So, when you're writing

10:56

code or you're building things, you are

10:58

editing code, right? That code has to be

11:00

edited and then hosted somewhere, right?

11:03

Uh and and usually what we used to do is

11:06

we used to all work on our Macs and

11:08

that's called local development. And you

11:10

have to set up your whole local

11:11

development environment. You have to

11:12

have your database, you have to have

11:13

your authentication, you have to have

11:15

everything local, you have to have your

11:17

dev server set up. Um, and then what

11:20

happens if you want to do two things at

11:22

once? You have to either use get work

11:25

trees, which is pretty technical and

11:27

hard to understand, or you have to

11:29

literally make another copy of your code

11:32

in another directory. And then, so then

11:34

to work on two things at once, you have

11:35

to have two copies of your code, which

11:36

is hard. And then what about three or

11:38

four? What if you want to do five or 10

11:39

things? It just doesn't work. So what

11:43

Devon does and and I think a lot of good

11:45

uh independent agent harnesses like

11:47

cursor is doing this now um I think

11:50

codeex is starting to do this okay is

11:54

they create what's called a VM or a

11:56

virtual machine in the cloud and it's

11:59

it's basically a little server and it is

12:02

your development environment and you

12:04

click a button and it spins up and all

12:06

of a sudden you can code in there and

12:09

the beautiful thing is if you can you

12:11

can create infinite numbers of these

12:13

things. So I often have, you know, at

12:16

least five uh uh cloud agents working at

12:20

once, often 10. And there's no risk that

12:23

the code is going to collide. So what it

12:25

does is it takes away all of the mental

12:28

overhead of trying to coordinate these

12:30

things. Like I want to work in this part

12:32

of the code, but what if it overlaps

12:34

this part of the code or what if, you

12:36

know, I want to do that? Have I

12:38

synchronized and pulled the latest? like

12:41

I don't know. And when I work in the

12:43

cloud, I literally just open up my

12:45

browser and I click new session and a

12:48

new and a new VM spins up and I never

12:50

ever have to think about it. So I think

12:53

if you are working locally, I honestly

12:55

think you are a caveman. Like I I think

12:58

you're you are holding yourself back and

13:01

you are shipping 10x less than you could

13:04

be. And it is not smart. No matter if

13:09

you think the cool people work locally

13:10

and that all the smart ends, it's not

13:13

true anymore. You work in the cloud.

13:15

>> Yeah. I mean, there are a lot of people

13:18

like on X who are sort of like local

13:20

maxis who look at people

13:24

who spin up virtual machines and cloud

13:27

agents as sort of like amateur-ish. What

13:30

do you say to people like that?

13:32

>> They they are not they are not doing

13:35

real work.

13:36

>> [laughter]

13:37

>> Um, here's the deal, right? So, as soon

13:40

as we hit PMF with Untangle and we and

13:43

we started acquiring real customers and

13:44

having to ship real fixes, real

13:46

features, like I had to

13:49

probably 50x my output, right? Um, and

13:53

you just can't do it if you're working

13:55

locally. So, I think it's it's nice to

13:58

work locally and sometimes you have to

14:00

if you're doing heavy front-end stuff.

14:01

So, say say you're shipping a brand new

14:04

feature with a lot of UI, like a lot of

14:06

new UI, right? Then yes, of course,

14:10

you're probably going to spin up a local

14:12

agent and you're going to do some light

14:14

front end, you know, probably

14:16

wireframing. Um, but as quickly as you

14:19

can, you want to move that into the

14:20

cloud and then let a cloud agent take

14:22

over. Um, so I think this is happening

14:25

to a lot of people. I think a lot of the

14:27

traditional

14:30

knowledge of how to work is is is out of

14:34

date. Um that's where we're at.

14:37

>> Okay. So if you do start using cloud

14:40

agents and you do 50x output, you know,

14:43

in some ways that is a little stressful

14:45

because you have so much stuff going on,

14:48

right? And now all of a sudden you have

14:49

to manage more. So how do you how do you

14:53

structure a system so you don't go

14:55

absolutely crazy?

14:56

>> So it's interesting I think first of all

15:00

you have to shift your expectation of

15:03

what your work is and what your work is

15:07

now is making high stakes decisions

15:09

almost all day. So in the past like we

15:12

all had the luxury of making probably

15:15

you know at most maybe two to three

15:17

highstakes decisions per day right you'd

15:19

have an important meeting with your key

15:21

team or with a customer and you'd make a

15:24

couple important decisions and you would

15:26

communicate those decisions and then

15:27

they would get done over you know two

15:29

weeks. Um, you know, I think you have to

15:33

sort of mentally pace yourself to say

15:35

probably by lunch you're going to have

15:38

made, you know, 10 to 20 high stakes

15:42

decisions.

15:44

Um, and so you have to learn how to do

15:47

that. So, which is your question, how do

15:49

you do that? Um, and I think there's a

15:52

couple simple things, right? Um, so when

15:55

I'm working with my agents, I actually

15:56

have to organize my threads by and I pin

16:00

the ones that are the most important

16:02

work we're getting done today, right?

16:04

Cuz there's a lot of quick buck bug

16:06

fixes or, you know, small things you're

16:08

shipping and you kind of learn to

16:10

separate two into two buckets buckets.

16:13

What are the big big important things

16:14

I'm getting done today?

16:17

Pin those. And and then the other things

16:19

just let them rip and get back to them

16:21

when you can. Um, and then set yourself

16:24

this kind of uh almost timer, right,

16:26

where you're like, "Okay, I'm going to

16:29

go crazy if I just click through my

16:31

threads like this all day." You just get

16:35

completely wiped out, right? And so,

16:38

it's almost this discipline of saying,

16:40

"I'm actually, you know, that the

16:42

phrasing smooth is uh slow is smooth and

16:45

and smooth is fast."

16:46

>> Yeah. I I think there's a little bit of

16:49

of that where you realize I can only

16:51

check on my agents and make highstake

16:54

decisions probably every 25 minutes.

16:58

Um and so what you might do is settle

17:00

into this cadence where you check on

17:02

your high stakes threads like every 25

17:04

minutes just so you can like literally

17:05

mentally rest. Um uh and then the other

17:10

side is that is just understand that

17:12

this is the world we live in and it is

17:14

kind of exhausting. Um uh and and that

17:17

is kind of where we're at. And in in

17:20

order to survive in this new world,

17:21

you're you're going to work a lot more,

17:23

not a lot less. And on that note, I'll

17:25

share my screen because there is

17:28

essentially

17:30

uh a world we live in now where you're

17:32

going to ship probably,

17:34

you know, so this is

17:37

my PRs, right? And we're looking, these

17:40

are days, right? And you can see, you

17:42

know, the average here is is sort of

17:45

this 22 to 25 PRs a day, right? And and

17:50

sometimes, you know, 40 a day. Um most

17:54

of these are being, you know, merged,

17:56

right? A couple are being closed. And

17:57

what's funny is what happened this day.

18:00

Um I went uh hiking with my son.

18:03

>> Which day is that? I can't see your

18:04

cursor.

18:05

>> Oh, it's uh the was the 18th.

18:07

>> 18th. Um, and so we went to climb Mount

18:09

Washington and I literally couldn't

18:11

access my my phone. Um, but notice

18:14

immediately the morning of, right? You

18:16

know, while he was sleeping, I I shipped

18:18

what is that, you know, eight PRs.

18:21

[laughter]

18:22

Um, so this is kind of, you know, the

18:24

world we live in now. Um,

18:27

and we could talk about that. Um, but

18:30

let's zoom out to the the lessons here.

18:32

You've got to go cloud, right? You have

18:35

to understand in order to compete in

18:37

this new world, you're going to be

18:38

working half the time from your phone.

18:41

And it is tiring. Um but but but it's

18:46

like going to the gym. Okay, I have this

18:47

new muscle like I never had to exercise

18:49

before and it turns out this weird back

18:51

muscle. It turns out like that's the

18:52

most important muscle in the world.

18:54

[laughter]

18:55

And if you don't do it, you're not going

18:56

to win. So the way to do that is then

18:59

set some sort of cadence for yourself.

19:01

Pin your most important threads. Write

19:04

it down. So, this, you know, what I'm

19:05

going to sort of flash up on the screen

19:07

here is my written to-do list. Um, every

19:10

day, you know, I use this hilarious

19:13

analog system to like to remind myself

19:16

what are the most important things we're

19:18

going to ship today because there's

19:20

going to be 10 probably PRs that we ship

19:22

that are fire, you know, putting out

19:24

fires. Um, and and you can get

19:27

distracted and exhausted. So, so cloud

19:29

and then exercise this new weird back

19:32

muscle which is making high stakes

19:34

decisions all day. Um,

19:37

>> including on your phone, right? What

19:38

you're basically saying is like

19:40

>> you're going to because of the velocity

19:42

of

19:43

uh

19:45

of you know do knowledge work and you're

19:50

you're just you'll have [sighs]

19:52

>> stuff going on and you will need to be

19:55

there to say yes. know actually this,

19:58

you know, giving feedback in real time

20:00

and

20:00

>> you know why your point is why wait

20:04

until you're in front of your Mac to

20:06

give feedback.

20:08

um

20:08

>> it makes no sense

20:10

>> if you're trying to hit product market

20:11

fit and if you're trying to 4x revenue

20:14

in you know in a month or whatever it is

20:17

um you know why

20:18

>> got to be available

20:19

>> got to be available

20:20

>> it and you know I think it just it's

20:22

easy to think of these things as humans

20:24

right like you have a team now that is

20:27

infinitely scalable they're going to do

20:29

work very fast and they're going to be

20:31

blocked by you making important

20:32

decisions right um and you can't

20:36

delegate the decisions Yet I think we're

20:38

still very much even if you use Fable

20:40

like this is a trick is is use a Fable

20:43

thread as kind of the manager and then

20:46

ask it to spin up children and I do this

20:48

a lot. So, you know, I'll spin up a

20:49

Fable thread and I'll say, "Okay, um,

20:52

you know, we want to accomplish these

20:53

five things. You know, spin up five, you

20:55

know, child Devon sessions. Don't use

20:57

Fable. I use Fusion for that, which is a

20:59

cheaper model or it it's cool. It's like

21:01

their their new model where they've got

21:04

um Fable is kind of the parent and

21:06

they've got a sidekick.

21:08

Point is, you're not going to it's not

21:09

viable to run Fable or any super premium

21:12

model all the time, but have a a sort of

21:15

a parent, you know, very intelligent

21:17

model run children. You can do these

21:19

things, but in the end, you're going to

21:22

have to pay attention. Um, and it's just

21:25

like if you ran a big team and you were

21:27

out to lunch on your boat all the time,

21:30

you got to get in the office, and the

21:32

office is your phone. Um, and so get it

21:36

done. And so, Greg, this is my homework

21:37

for you. Next time we talk, I want you

21:39

to be doing more than 50% of your work

21:41

on your phone.

21:42

>> Yeah. I mean, that's why that's why

21:44

you're here, right? Like, you're a lot

21:46

of people ask me like, "How do you

21:47

choose guests?" And and why do you

21:50

explore topics, certain topics over

21:52

other topics? And it's it's really it's

21:55

for everyone. Like, I love arming people

21:58

with the information, the tactics, the

22:00

systems, but I'm also everyone. Like,

22:02

I'm a part of that, right? Like a part

22:03

of that is like I know that you're

22:05

you're doing this and I want to

22:07

understand why you're doing it. And I

22:09

also want to understand like you know

22:11

one of the takeaways I have is your

22:13

system for dealing with tasks is not is

22:16

not too dissimilar to a a very organized

22:19

person pre- AI right

22:21

>> like the idea of like pinning you know

22:24

your most important things like it's on

22:27

one hand it's pretty obvious but on the

22:28

other hand if no one tells you like

22:31

>> hey you know the way to to do this so

22:33

you stay sane is via that system you're

22:37

you it's overwhelming. Right.

22:39

>> Yeah, it is funny. It's like back to the

22:41

basics, right? It's just in an agent

22:44

age. Um, and it turns out like being a

22:47

very very good engineering manager is is

22:49

probably one of the most valuable skills

22:51

you can you can teach yourself. And you

22:54

know, I'm uh have the honor of sort of

22:56

mentoring uh my nephew right now and and

22:59

he's coming to me and asking me how do I

23:01

win? You know, he's just come out of

23:02

college soon. How do I win in this new

23:05

world? Right? And you know, I'm

23:07

basically teaching him what we're

23:08

talking about in the show. It's like,

23:10

okay, your job is going to be managing

23:11

as many agents as you possibly can. Get

23:14

good at that, right? Which means, you

23:17

know, you need to start to adopt these

23:19

these these behaviors, right? Work in

23:21

the cloud, prioritize what you're doing,

23:24

learn how to make high stakes decisions

23:26

quickly, get technical. Um, you know, it

23:30

it is a farce that engineering is going

23:32

away. Like if anybody tells you

23:34

engineers are going away or becoming

23:36

less technical, they're just not doing

23:38

the work, right?

23:39

>> Um and it's like being a carpenter. Like

23:42

say you had robot carpenters around. If

23:44

you were a real carpenter, you'd be a

23:46

much better manager of those robot

23:48

carpenters because you understand how to

23:50

make the cut. You know where to put the

23:52

nail. Um and so and so it's important.

23:56

So, to back up and if you're listening

23:58

to the show, like the thing I want you

24:01

to walk away is is cloud agents. Get

24:04

your reps in, figure out how that works.

24:07

Try it a couple times. Um, do it from

24:10

your phone and get comfortable, you

24:13

know, looking at your small phone

24:14

interface and and learning how to work

24:17

that way. Um, so I think that's that's

24:20

thing one. Uh, it's very important. The

24:22

second thing I want to dive into is

24:23

automations.

24:25

Okay, so say you're working in the

24:26

cloud. Well done. Um, you know, you're

24:29

starting to separate yourself from the

24:30

crowd. The second thing is automations.

24:33

Um,

24:34

you need to sort of think about things

24:36

that you would have normally had a

24:38

meeting with, uh, you know, once a week

24:40

with your team, uh, where you check on

24:42

something or daily you check on

24:44

something and build an automation. What

24:47

does that mean? Um,

24:49

so the first thing to do is go back to

24:52

your agent, start a session, and say,

24:54

"Okay, I want you to automate this task

24:58

every x amount of days." And so, one of

25:01

them that I do, it's really simple, is

25:03

that I want to automate the test of

25:06

signing up for Untangle, um, creating a

25:09

case, onboarding a client, having that

25:12

client go through discovery, you know,

25:14

basically our user experience. But I

25:16

want that to be automated in a browser.

25:18

Like this is not rocket science. This is

25:20

basic user testing, right? Um but it

25:24

turns out that good agents can do this.

25:26

And so the big unlock is uh set up your

25:31

agents so that they can make themselves

25:34

better um uh instead of you trying to

25:37

build these systems. Um and so I set

25:40

that up and then in Devon it's really

25:42

cool. It's called a playbook. But the

25:44

idea is it's it it's it's sort of like

25:46

here's how to do this thing. It's

25:48

different than a skill. It's more of a

25:50

list of things to do, how to do them

25:52

correctly. Um, and I have a uh it's

25:56

called endtoend

25:58

uh signup test and that runs three times

26:00

a week. Um, because it is expensive.

26:03

It's it's probably 60 bucks in tokens.

26:06

Um, because it's doing a lot of it's

26:08

doing a lot of browser testing. Um, and

26:12

uh, I think that's sort of a side point

26:14

I want to explain here is it's it's now

26:18

vital that your agent can can properly

26:21

brow browser test. Um, and it really

26:24

should work out of the box, right? This

26:26

is part of the reason I used Devon is

26:29

because they've been using cloud agents

26:32

that can do browser testing for 2 years

26:34

now. It's so good. It records a video.

26:38

It annotates the video. it it then looks

26:41

at its own video and it fixes bugs that

26:43

it sees, right? So you have this agentic

26:46

loop that is specifically around browser

26:48

testing that then is automated three

26:50

times a week, right? And then what what

26:54

what do you do with that? And then you

26:55

need to trigger a triage based off of

26:58

that. So say that it's like, oh wow,

27:00

during this the the third test failed in

27:04

this automation, I'm going to spin up a

27:07

Devon session or an agent session to

27:08

then fix it. Um, and then you have to

27:12

figure out where do you know that that

27:13

failed? How do you know? Did the agent

27:16

just kind of f, you know, silently fail

27:18

and then fix itself? What about the PR

27:20

that was created? So you have to start

27:22

thinking about how do you see these

27:24

things when they happen, right? as the

27:27

manager of all these agents, how do you

27:30

know uh what's failing, what's not? And

27:32

and that's again where you should talk

27:34

to your agent and say, "Okay, we've got

27:35

this end to end test. You know, I

27:37

understand it runs Monday, Wednesday,

27:39

Friday. Um I understand it, you know, it

27:42

it triggers a child triage session if

27:45

anything goes wrong. How do I know about

27:47

it?" And it and then your agent might

27:48

say, "Well, you know, why don't I post

27:50

in Slack?" You know, and and you can

27:52

say, "Well, okay, how are you going to

27:53

do that?" Well, we need to connect the

27:55

MCP. you know, how am I going to know to

27:57

look in that channel? There's just all

27:59

this machinery that you need to to to

28:01

automate and figure out and and work

28:03

through um to build that system um of

28:07

automation so that you are doing less of

28:09

the work.

28:10

>> So this specific automation is this more

28:13

of a like bug testing QA automation or

28:17

is it more of a um

28:22

you know UX QA perspective? Th this one

28:26

is more about um uh finding bugs that

28:29

have been introduced to prod that

28:31

somehow uh we missed in our in our user

28:35

tests um

28:36

>> in our automated test suite.

28:38

>> So that one in particular is like hey we

28:40

just can't have signups go down and not

28:42

know about it. Um, but you know,

28:45

sometimes your your automated test suite

28:47

just it it doesn't catch everything. Um,

28:50

but a good oldfashioned clicking through

28:52

the site in a browser catches that.

28:55

>> Um, it is not really about the UX. Um, I

28:59

think that there's there's no one thing

29:02

I will say is there's no substitute and

29:06

we probably won't have a substitute for

29:08

a while of you using your own app. there

29:12

just isn't a good substitute right now.

29:15

So, right now, every every so often, I

29:18

literally go through our entire app

29:20

myself. Um, and then I obviously quickly

29:23

spin up, you know, sessions to fix bugs

29:25

I find. But, um, we're we're just so far

29:28

from agents still. you the the smartest

29:31

models in the world still lack this

29:33

sense of obvious

29:36

you know uh intelligence where you're

29:40

like why did you think that was okay?

29:42

Well, yeah. I think the bigger question

29:44

is, you know, if if there's a division

29:46

of labor between human beings and

29:48

agents, what are the tasks that you as

29:50

the human being are going to be doing?

29:52

What are the sets of tasks? And what are

29:54

the sets of tasks that the agents are

29:57

going to be doing that you're okay with

29:58

them doing and keeping you in the loop?

30:00

So, my question for you around

30:01

automations is beyond beyond QA, what

30:04

are some other automations that you know

30:08

a founder could be implementing? So um

30:11

let me pull up my list for you. So the

30:15

kind of automations that I have are uh

30:19

clearly uh uh QA bug fixine. Um the

30:23

other is what I call my production

30:25

watchdog. Um so we've got a lot of real

30:30

law firms using Untangle. got a lot of

30:32

real clients, you know, going through

30:34

discovery and we've got just a huge

30:37

amount of activity and and honestly I

30:39

can't keep track of it uh you know

30:41

mentally by just looking through logs.

30:43

And so what I do is every day at 9:00

30:45

a.m. I have what's called a production

30:46

watchdog automation which what it does

30:49

is it goes through all of the events in

30:52

the database um that happened for our

30:55

paid customers and it summarizes that in

30:59

uh a JSON file and then that JSON file

31:03

is in our admin and then I I you know

31:05

know every morning I go in and I click

31:07

on uh the production watchdog and I read

31:09

through the summary of what the

31:11

customers did um and it's so valuable.

31:16

Um, so it's sort of like you can

31:17

imagine, you know, your chief of staff

31:19

showing up and saying, you know, all

31:20

right, Greg, here's the important stuff

31:22

that happened yesterday for our

31:23

customers, right? Um, and I'm going to

31:26

roll it up and explain, you know, the

31:28

things that went well and a couple bugs

31:30

that we saw. Um, so that's an

31:32

automation. Um, essentially what

31:35

happened yesterday that was important.

31:37

Um, so that one

31:38

>> that's a big one.

31:39

>> Yeah,

31:39

>> that's honestly a big one. like it's

31:40

it's like one of those ones that sounds

31:42

small but is a big one because you're

31:43

going you think you know what's going on

31:46

but you don't really

31:48

>> you don't I mean and it's it's so

31:50

shocking to me like yeah the amount of

31:52

times I'm like oh uh and this is the

31:55

other trick man so use a production

31:58

watchdog automation pick your most

32:00

important customers and then make sure

32:02

that in that report it's like the

32:04

customer did X here's a link to view

32:07

that right and so I actually have a

32:10

production instance where you click it

32:11

and you actually see what the customer

32:14

was doing and then I'll be like whoa

32:17

that's weird like and we have this

32:20

amazing ability that you know over you

32:23

know uh you know millions of years of

32:26

evolution in very quickly picking up

32:28

things that are off. [laughter]

32:30

And so there's a couple times I'm like,

32:32

"That's weird." And I click into it and

32:34

it turns out, oh, the user experience um

32:37

that the agent built on that wasn't was

32:39

wasn't quite what I thought it was. Um

32:42

and so yeah, production watchdog

32:44

automation that links out to real UI um

32:49

is just man, it's a game changer. So

32:52

that's a big automation. Um this is a

32:54

really important a self-improvement

32:56

loop.

32:57

How does this work? Okay, everyone's

32:58

talking about self-improvement, right?

33:00

>> Um, so in Untangle, we have an agent

33:03

called Grace, and she is essentially a

33:05

parallegal. Um, and she has a lot of

33:09

chats with both uh our customers who are

33:11

attorneys, our customers who are

33:13

parallegals, and our customers and their

33:15

customers who are clients that are

33:17

getting divorced. Um, so how do I

33:20

actually grade those chats and then

33:22

improve them uh without managing the

33:26

fine details? So what I do is I every

33:28

day I have an automation that looks at

33:31

these chats and then grades them on a

33:33

rubric. And so you and again just talk

33:36

to your agent about this. You pick the

33:38

most important part of your app that you

33:39

want to self-improve and say here's how

33:42

you agent judge whether this thing that

33:45

happens is good or bad. Um and then

33:48

every day I want this automation to kick

33:50

off. Look at those things for us.

33:53

They're conversations that Grace is

33:54

having. and then I want you to grade

33:56

them. And then if anything is bad or

33:59

below this score, I want you to kick off

34:00

a child session and fix it. And it is

34:04

shocking to me the number of small, you

34:07

know, fine UX details that have been

34:10

picked up by this loop and have been

34:12

fixed. And honestly, there are things

34:14

that I just wouldn't bother doing.

34:16

Either I didn't know about them or I'd

34:18

be like, me, you know, it's a paper cut.

34:20

Like, are we really going to, you know,

34:22

ship a fix to that? But because the

34:24

agent already identified it, spun up a

34:26

PR, and it's ready to ship, I just go

34:29

ship it. [laughter]

34:31

And you know, we probably ship I would

34:33

say probably three of these a day.

34:35

>> Wow.

34:36

>> That's that's huge.

34:38

>> And you know, a lot of a lot of the

34:41

backlash on on loops is is just that

34:44

it's expensive. Um, how how how have you

34:48

with with Devon specifically, has it

34:50

been like absurdly expensive? Like what

34:52

are we talking? No. So he Well, so

34:54

here's the thing. So last month I spent

34:57

probably 20 grand in in tokens, uh,

34:59

which is just too much. Like it's not

35:01

viable. I I think all of us are in a

35:03

place where we we're getting to the spot

35:06

where it's realizing, okay, for real

35:08

engineering work per employee, you're

35:09

looking at probably 5 grand a month.

35:12

Like that's probably where we're going

35:13

to shake out here. And anything more

35:15

than that, you you really need to figure

35:17

out model routing. Um and so thankfully

35:21

Cognition knows this and every

35:23

everyone's figuring this out like yeah

35:25

whether it's cursor cognition

35:28

>> I would say factory AMP all of the

35:30

independent agent labs understand like

35:32

[laughter] we our customers have a limit

35:35

like they're not going to pay infinite

35:37

token budgets

35:38

and then you have the this is me ranting

35:40

a bit but it's like you have cloud code

35:42

and codeex who are just severely you

35:44

know fund they're they're funding tokens

35:48

and making it seem cheap, but this is

35:49

not going to work long term. And so what

35:52

I do is basically I have learned how to

35:55

use the right model for the right task.

35:57

And so these reinforcement loops, they

36:00

use what's called SUI 1.7. It's a

36:03

fine-tuned model that Cognition has

36:05

specifically built for coding. It's

36:06

super cheap um compared to, you know,

36:10

Opus 48, you know, GPT56. And so a lot

36:13

of these loops happen with this uh you

36:15

know cheaper you know finely tuned model

36:18

and we're just going to see more of

36:20

that. So you're talking I don't know it

36:22

you know actually I could probably I

36:24

could probably look and dig it out but

36:25

you're t probably talking like five

36:26

bucks a session on that.

36:27

>> Okay that's not bad.

36:28

>> I mean and if you're not willing to pay

36:30

15 bucks a day

36:31

>> to improve one of the core you know

36:33

feature sets of your like what are you

36:35

doing? Like either it's not a real

36:36

company or you don't care.

36:38

>> Yeah.

36:40

>> Totally. spend the money like and and

36:43

then you know figure out the the system

36:47

uh to reduce your token cost. I will say

36:49

this is why I don't understand why

36:52

anybody would build their engineering on

36:55

a frontier lab stack. Like I'm just

36:58

going to call it out like if you are if

37:00

your whole engineering uh you know

37:02

motion is happening inside of cloud code

37:04

or inside of codeex what are you doing

37:07

like because they are not incentivized

37:10

to make it reasonable for you long term

37:14

right they're going to lock you in to

37:15

their models to their process whereas if

37:18

you use an independent agent lab you

37:21

know like an AMP like a Devon like a

37:23

factory like sort of a cursor but

37:25

they're kind of weird now those systems

37:27

are going to optimize for affordable

37:29

engineering long term. Um, and uh, I

37:34

don't think you want to be locked in to

37:37

anthropic or or open AI, you know,

37:40

solely.

37:41

>> I mean, to be clear, you can still use

37:43

their models within some of these

37:46

products, right? So, you're not

37:47

abandoning ship.

37:48

>> No, it's actually so it's it's yes and

37:51

right. So the beautiful thing is if you

37:52

pay you know an independent agent lab

37:55

like a factory like a cursor like a

37:57

cognition like an amp you know etc

37:59

they're incentivized to figure out how

38:01

do I give you the best results for the

38:04

lowest price. So they'll they'll say,

38:05

"Okay, we're going to use GPT56 soul on

38:09

extra high for this type of task, and

38:11

then we're going to route, you know, to

38:12

a uh you know, to a SWE 1.7, you know,

38:16

and then we're going to have it checked

38:18

with a Fable." Like, they're going to

38:19

figure out that hard stuff.

38:21

>> Um, and the other thing I will say is if

38:23

you're trying to build a software

38:25

factory for yourself, stop. like it, you

38:28

know, the reason why you see, you know,

38:31

Ramp launch, Inspect, which is their

38:33

custom in in-house agent, is because

38:35

they got to a size where they had to

38:36

build their their software factory

38:38

in-house. And if you get to a certain

38:41

size, you will do that. But now, if

38:44

you're a oneperson shop and you're just

38:45

building something that's just you, you

38:47

can probably get away with this $200 a

38:49

month uh, you know, angle on a pick your

38:53

frontier lab. But as soon as you

38:55

graduate into, okay, we're building a

38:56

real product. We have product market

38:58

fit. We're going to start hiring people.

38:59

You got to build a software factory. And

39:01

at that point, you want to be on an

39:03

independent agent lab. Like otherwise,

39:08

you're going to have to build it

39:09

yourself, which is stupid, or you're

39:10

going to pay and be locked into, you

39:13

know, a walled garden. Um, and you can't

39:16

do that. The the analogy I use for it

39:18

is, you know, working with an

39:20

independent lab is sort of like a uh

39:24

like working with like a mortgage broker

39:26

or travel agent. Like they're going to

39:28

make a lot of calls to make sure to

39:29

[laughter] get you the best price and

39:31

stuff like that. Um

39:34

>> that's an Yeah, to me I use both. You

39:37

know, I I'm in cloud code, but I'm also

39:40

I use cursor personally. Um, although

39:43

Devon I'm interested in I might if

39:45

people are interested I might just do

39:46

like a whole

39:48

breakdown on Devon if people if people

39:50

want to want to do that.

39:51

>> Devon's so good now. Um, you know

39:54

>> I just it's so good. It it's amazing.

39:56

Um, but I will say I do use codecs,

39:59

right? The the the the Mac app is so

40:02

beautiful like

40:04

>> and there's and they are subsidizing the

40:06

tokens so much that if you want an agent

40:10

on your machine just to do really cool

40:12

helpful stuff, open browser tabs and

40:14

create Google Docs and check your email

40:16

and and do all this information work and

40:20

and basically get it for free. I mean,

40:22

you're paying 200 bucks and you get

40:23

almost infinite tokens. like awesome,

40:26

but don't build your company software

40:27

factory on that. Like it I just think

40:31

it's bonkers to do that.

40:32

>> Mhm. We've covered a lot today. Is there

40:34

anything else you wanted to uh

40:37

[laughter] cover?

40:38

>> I feel like I'm just vomiting, you know,

40:40

all all the stuff in my head that

40:42

>> Well, no, I it's important that like

40:46

this is what I wanted. I wanted you just

40:47

to vomit everywhere because like it's

40:50

sort of like advice that you you you

40:53

would give to your to your nephew I

40:55

think um or 22-year-old um

40:58

>> you know a 22-year-old fresh out of

41:00

college. It's like what are the minds I

41:02

need to know in terms of

41:04

>> managing agents? So is there anything

41:07

else that people need to know? Cloud

41:08

agents, automations.

41:11

Yeah, cloud

41:13

automations like th those are the two

41:16

that I want people to walk away from. I

41:18

guess the third is is really you will be

41:21

using a software factory like and what I

41:23

mean is the agents are going to be

41:24

writing 100% of your code, reviewing

41:26

100% of your code, shipping 100% of your

41:28

code. Like that's where we're going. Um

41:30

and so the the more you can get there,

41:34

the the better. thing one uh thing two I

41:37

think you know thing three is um it it

41:40

is important to build um uh a credible

41:44

reputation for yourself right and I will

41:47

say you know the work I put in over you

41:50

know the last 20 years on X like it

41:54

really pays dividends and what I mean by

41:56

that is if you if you share what you're

41:59

learning publicly and you generally give

42:01

like write very helpful articles on X.

42:05

Um, and obviously the ALGO really does

42:07

reward articles still. So, you should be

42:10

writing articles on X. Um, you should

42:13

absolutely be on X, no matter how you

42:14

feel about Elon. Um, uh, because sharing

42:18

your knowledge really does build up

42:19

credibility, which will pay dividends.

42:22

And I don't mean just like getting paid

42:23

to post. I mean the the the the network

42:26

and the relationships. I mean, the

42:27

reason why I'm on the show is because we

42:29

built a relationship over X. Um, and so

42:32

I would encourage people take the time

42:34

to share what you're learning. It

42:36

doesn't have to be super polished. Um,

42:38

but get out there and be useful to

42:40

people. Um, and it will open up doors.

42:43

Um, so, uh, you know, more than you

42:45

think. Just get out there and share it.

42:47

Um, and, uh, and you'll reap the

42:49

rewards. Not immediately, but

42:51

eventually.

42:51

>> I mean, even if you don't know, you can

42:53

just say, "I don't know." And that's

42:54

your and that's your strategy, right?

42:56

And that's interesting, too.

42:58

>> Amen. And if you don't know, then ask an

43:00

agent to help you.

43:01

>> Yeah. So,

43:02

>> I mean, my original co-host of this show

43:05

was Sahel Bloom. Sahil Bloom worked in

43:08

private equity and during COVID he just

43:12

started writing about topics he was

43:14

interested in like he would be like just

43:17

finance topics or you know particular

43:20

individual who was interesting and it

43:22

like it it it read as like Wikipedia

43:25

articles but really focused on Twitter

43:28

specifically like optimized for Twitter

43:30

and and that was his thing and he wasn't

43:32

saying I know everything he was just

43:34

saying like I'm learning this thing.

43:36

Here's the thing I'm learning. He grew

43:38

his audience over a million Twitter

43:40

followers, wrote a bestselling New York

43:41

Times bestselling book, started

43:43

companies on top of it, raised a fund on

43:45

top of it. So, anything is possible for

43:48

sure. Uh on on X.

43:52

>> Yep. Just just get out there and do do

43:55

and learn. Um

43:56

>> uh you know, there there's no try.

43:59

There's only do as Yoda says, right? So,

44:02

>> totally. Uh Ryan Carson, I feel smarter

44:06

and that's that was my goal. Um

44:10

and uh speaking of X, you're a wonderful

44:13

follow. I'll include links where you can

44:16

follow Ryan across the internet,

44:18

including X. Um he's a mustf follow, so

44:21

please do that. Thank you for coming on,

44:23

sharing your generous uh thoughts,

44:27

incredible setup, and uh is there

44:30

anything you want to leave people with?

44:32

No, thanks Greg. Thanks for having the

44:34

show. I appreciate you putting out the

44:35

constant knowled uh constant knowledge

44:37

and sharing. Um it really makes the

44:39

internet a better place. So happy to be

44:41

here and thanks for having me.

44:43

>> All right, I'll see you next time.

44:45

Take care.

Interactive Summary

This episode features Ryan Carson, a seasoned founder and AI operator, discussing the paradigm shift in software development and management through AI agents. Ryan emphasizes the transition from local development to cloud-based agent environments to scale productivity and highlights the importance of implementing automation for QA, production monitoring, and self-improvement loops. He argues that becoming a technical manager of these agents is the defining skill for success in the current AI era, and advocates for sharing knowledge publicly to build long-term career capital.

Suggested questions

3 ready-made prompts