HomeVideos

He Builds Apps Without Reading Code (And Is Really Good)

Now Playing

He Builds Apps Without Reading Code (And Is Really Good)

Transcript

1330 segments

0:00

That moment in time, I'd never launched

0:02

anything on GitHub. I'd never done a

0:04

solo project at all, and I launched it,

0:07

and I made a video, and it went viral,

0:10

got a million views. That's how I got

0:12

started.

0:12

>> Did you know [music] if it was actually

0:14

possible to bring in all of these

0:16

signals before actually building the

0:18

thing?

0:18

>> Not not a clue at all. I fundamentally

0:20

believe that very [music] soon no humans

0:23

should ever write any code, and that no

0:25

humans should ever read any code. Had

0:28

the audacity to start a programming

0:31

language at 5:00 in the [music] morning

0:32

that Sunday morning, and it was a stupid

0:34

idea, but it led to a good idea.

0:36

>> Matt Van Horn, thank you for joining

0:38

Human in the Loop.

0:38

>> I I can't wait to be removed from the

0:40

loop after.

0:40

>> Yeah, [laughter] exactly.

0:42

>> to you're going to have to rename your

0:43

podcast soon, Alex, cuz I I I don't want

0:46

I don't want to work work on this

0:47

anymore. I just want my agents to do it.

0:49

>> Honestly, Human Out of the Loop is like

0:51

an easy rebrand, so we'll do that at

0:52

some point. Um it's awesome to have you

0:55

you know, you're you've become like a

0:57

prolific builder and engineer, and I

0:59

think what's most fascinating about you

1:01

is you're not technically trained,

1:02

you're not an engineer by training, yet

1:04

yeah, I feel like you're doing circles

1:06

around a lot of classically trained

1:08

engineers. And so, my goal is just to

1:10

understand

1:12

how do you build, and and how were you

1:13

able to work up the curve of

1:16

understanding all of this

1:18

so quickly? Um and so, yeah, I just want

1:21

to watch you cook. Obviously, you've

1:23

learned a lot in this process, but also

1:25

there's it seems like there's a ton of

1:27

stuff you don't even know what it means

1:30

or or kind of the exact details as

1:32

you're building it, but that's also kind

1:34

of the beauty of this technology. It's

1:35

like if you just have enough agency and

1:37

you're you're dangerous enough to ask

1:38

the right question, that's kind of all

1:40

you need.

1:42

>> Yeah, it's it's all about confidence in

1:44

asking the right questions.

1:45

>> Yeah.

1:46

>> Right? Like like the fact that I had the

1:48

audacity to start a programming language

1:50

at 5:00 in the morning that Sunday

1:52

morning was stupid.

1:55

And it was a stupid idea, but it led to

1:57

a good idea.

1:58

>> Totally.

1:59

>> And and so I think just not being afraid

2:02

and just starting is is really magical.

2:04

And so like Pretty Press, like you're

2:06

talking about programming languages and

2:08

so I've gotten contributions into Go,

2:10

which is

2:11

incredible programming language. Um

2:14

and but Peter makes all of his CLIs in

2:16

Go. And so it's like so

2:18

uh Peter Steinberg, so I was like,

2:19

"Okay, I guess the Pretty Press CLI

2:21

should be in Go." Right? I've never done

2:22

a project in Go before. And what's funny

2:25

is I I built this other project Agent

2:27

Cookie, which we don't have to spend

2:28

much time on, but it it kind of

2:30

automatically syncs your Chrome cookies

2:31

from your main Mac to your Mac Mini in

2:33

the cloud.

2:34

>> Mhm.

2:34

>> And I literally was about to ship this

2:36

product and I have I don't I don't ever

2:38

look at code. Um

2:40

and [snorts] I I philosophically don't

2:42

believe in looking at the code. And

2:44

>> Well, why is that?

2:45

>> That's that's that's for agents. That's

2:47

agent's job. That's why I don't have an

2:49

IDE. Like why do I don't need to look at

2:51

the code. Um I can talk to my agent

2:53

about a problem, but I was literally

2:54

shipping this product and I was on the

2:55

GitHub page and I was like, "Oh, I had

2:58

no idea Agent Cookie was built in Go."

3:01

Like I literally didn't know that it's

3:04

94.7%

3:07

>> [laughter]

3:07

>> Go.

3:08

>> Do you think Do you think your view on

3:10

not needing to read your code is

3:11

specific to like

3:13

these side projects that you're building

3:15

or like do you believe that even in the

3:17

context of building a company?

3:18

>> I fundamentally believe that that very

3:21

soon no humans

3:23

should ever write any code

3:25

and that no humans should ever read any

3:28

code.

3:30

I strongly believe that.

3:32

And um and again, I get to personify

3:34

this because I can't read the code. So

3:37

like I I already have this this problem

3:39

that I literally would not be useful,

3:42

right? But I I think the the the

3:44

engineers of the future, like what is an

3:46

engineer? An engineer is a problem

3:47

solver.

3:48

It's not someone that just you know,

3:50

studied the right things. Right? An

3:51

engineer a solves problems. Like we we

3:53

tell our team that your your job is to

3:57

automate your job and find something

3:59

else more important to work on, a more

4:00

important problem to solve.

4:02

And so that's that's something I I

4:04

strongly believe in.

4:05

>> Super interesting. We may have to do a

4:07

episode in the future where we do a

4:09

debate style episode cuz I feel like it

4:11

would just be fun. There's for sure

4:13

people who would take the other side of

4:14

the trade and I think it would it just

4:16

like the intellectual exercise of

4:17

understanding why or

4:19

why or why not would understanding the

4:21

code and reading the code in the future

4:23

be valuable. And my assumption is your

4:24

argument is the models are going to get

4:26

so good that even if people are working

4:28

about worrying about scalability or like

4:30

how hard in the code is, these are all

4:32

solved problem by good enough models.

4:35

>> Yep.

4:35

>> Yeah, makes sense.

4:37

Um okay, let's let's build something.

4:38

What what do you want to build?

4:39

>> Let's let's build a few things. I have a

4:42

few few things running. Let's start

4:44

Let's start here. So so Trevin who I

4:47

built Pretty Press with, I asked him,

4:48

"Hey, what what should I build on on air

4:50

today?" He's like he's like

4:52

nutritionvalue.org. And I'm like, "What

4:54

is that?"

4:55

And I'm like, "This This is this looks

4:58

horrible. Um

4:59

and um

5:01

And he's like, "Yeah, it's not pretty,

5:03

but it's really valuable and can pull in

5:05

lots of valuable information."

5:06

And so

5:08

the I don't know if it's going to work,

5:09

but we're going to try to build a CLI

5:12

about

5:14

nutrition information.

5:15

>> So basically this website is just like

5:16

this mega database of the nutritional

5:18

facts of a ton of different foods and

5:21

food items.

5:22

>> Yep.

5:22

>> Cool.

5:23

>> Yep, you're you're seeing my

5:24

nutritionvalue.org password as I

5:26

generate it. Uh-oh. [laughter and gasps]

5:28

Try not to try not to steal my secrets

5:32

of my nutrition value.

5:35

>> All right, I'm in. Okay, so

5:38

what what I'm going to do is I'm going

5:40

to make a new window here.

5:44

And so I I use this skill um

5:49

Uh sorry, I'm going to use I'm going to

5:50

use pretty press. All right, so CLI

5:52

printing press.

5:53

Generate a a ship uh ready CLI for an

5:56

API with lean research generate build

5:59

ship check loop.

6:02

So, I don't know why I have two.

6:03

Hopefully, it will.

6:07

>> And so, I I know uh while while this is

6:09

going, I know like I read your agent

6:11

hacks article and you talk about like

6:12

the importance of you use the compound

6:14

the C plan um like you you use compound

6:17

engineering for a lot of what you build.

6:19

Is that just implicitly built within the

6:22

printing press, so it goes through that

6:24

process?

6:25

>> It's it's actually not, but it's

6:27

obviously heavily inspired and similar

6:30

to and learned from all the best

6:31

practice. So, it doesn't actually run

6:33

compound engineering, but

6:35

Trevin is one of the best agentic

6:38

builders that I I've met and uh a lot of

6:42

the best practices that him and Kieran

6:43

have built into

6:45

compound engineering are built in

6:47

obviously to the printing press.

6:49

And so, I'll start the printing press

6:51

for nutrition by first running the

6:53

mandatory pre-flight setup. So, I don't

6:55

know what it's doing, but it'll it'll

6:56

tell us I mean, why don't we go to

6:57

another window and try try something

6:59

else? I think I can show you something

7:00

else I was working on. I can show a

7:02

compound engineering thing. Okay, so

7:05

we we have a um

7:07

a

7:09

a CLI in the printing press called the

7:11

ESPN one.

7:12

And so, I said

7:14

uh

7:15

earlier, "Why did England win yesterday

7:16

in the World Cup?" And I'll look up

7:18

England's World Cup match from

7:19

yesterday. First, verify the CLI. So,

7:20

it's using the ESPN CLI that that we

7:24

built. And so, came with the result.

7:27

England beat DR Congo 2 to 1 in the

7:29

World Cup round of 32. Yeah, the short

7:30

answer is they won is Harry Kane with a

7:31

big assist literally twice for

7:33

uh from substitute Anthony Gordon. It

7:35

was actually a near disaster comeback

7:36

rather than a dominant win.

7:39

And um

7:40

so, what's what's interesting is this is

7:42

the second So, when we built the ESPN

7:44

CLI, there was no mapping to

7:49

the World Cup cuz it hadn't been built

7:51

yet in ESPN system. And so, I feel like

7:54

this took longer than it should have. It

7:55

took 1 minute 11 seconds. And so, one of

7:57

the things that the features that were

8:00

working on right now in the printing

8:01

press is self-learning CLIs. So, the

8:03

agent will leave notes for itself for

8:05

next time locally.

8:07

And ESPN's one of the first ones to have

8:09

this feature. But,

8:11

I just ran this in another context

8:13

window, and it also took 1 minute 10

8:14

seconds. So, this one should have been

8:16

faster. And so, I've no idea what the

8:17

result is going to be, but I'm just

8:18

going to say I wrote this right before

8:19

we started. See, E plan, this took 1

8:21

minute 10 seconds and 11 seconds, and I

8:23

pasted in I'll do a lot of copying and

8:25

pasting, a lot of screenshot pasting. Um

8:29

Hey,

8:30

this was after the search deal. So, this

8:32

is the the newer context window. Why did

8:34

it just as long as what just happened?

8:36

So,

8:37

All right. So, we got got that one. And

8:39

>> And basically and basically your whole

8:40

thought is this should have been faster

8:42

because if you have this self-improving

8:45

CLI, it should already have had the

8:48

information about the England win.

8:51

>> Exactly. It should Not the England win.

8:52

It should have known how to map a World

8:54

Cup

8:55

>> Got it. Got it.

8:56

>> the other question I asked was about

8:57

Belgium

8:58

and so, it should have learned the

8:59

mapping. Kind of again, CLIs, think of

9:01

it like Google Maps for things. So,

9:03

while that's going on, I think our CLI

9:05

had a question.

9:06

Um

9:08

So, it's it's asking, "Anything you want

9:10

me to know before I begin? A vision for

9:11

the CLI should do some feature care

9:13

about or off." And it's like, "Let's

9:14

just go. I'll start research now. I'll

9:16

ask about API keys, browser auth, other

9:18

things. Cool."

9:19

So, I don't have a particular vision for

9:20

this. I I hope it's self-explanatory.

9:23

>> I also know that you feel pretty

9:24

strongly about um

9:26

uh dangerously skip or bypass

9:28

permissions. What Why do you feel

9:31

strongly about that versus needing to to

9:33

check and keep yourself in the loop?

9:36

>> So,

9:38

there's just a lot of stupid stuff that

9:41

comes up if you don't have it on. So,

9:43

like for example,

9:45

it's going to go So, the what what the

9:46

printing press does right now is it's

9:48

going to go research

9:50

nutritionalvalue.org. It's going to look

9:51

around. It's going to do a hard sniff to

9:54

try and figure out kind of the mapping

9:56

of the whole site. It's also going to go

9:58

on GitHub and look for community um

10:02

CLIs. Like, has anyone done this before?

10:05

Like, when we were printing the Domino's

10:06

Pizza CLI, someone had a project that

10:09

was a a Python script. It's like pre-AI.

10:12

A Python script to be able to order

10:14

Domino's Pizza. Like, they sniffed the

10:17

APIs from domino's.com and they just

10:19

wanted thought it they wanted to run it

10:20

in Python. Project didn't have that many

10:22

stars. I think it was less than a

10:23

thousand, but like it worked and was

10:25

really cool.

10:26

Uh-oh, nutritional value or explicitly

10:28

prohibits programmatic access to data

10:30

and has no official It largely comes

10:32

from USDA food data, which offers a

10:34

official free API with nutrition. How do

10:35

you want to proceed?

10:39

>> So, what are you going to do?

10:40

>> I don't

10:41

Let's try building a combo CLI. So, try

10:44

and do that one, but also get the the

10:46

one that has an API. But, I I do like

10:49

nutritionalvalue.org

10:51

but I like that one. So, let's try and

10:52

do both. YOLO mode.

10:54

>> Is it basically what it's saying is that

10:56

nutritionalvalue.org

10:57

like generally prevents you from doing

10:59

any sort of automated behavior? So, so

11:02

you have to decide whether you want to

11:03

still try to

11:04

have have Claude code or the the

11:08

printing press figure out how to still

11:09

deal with that?

11:11

>> Yep, exactly. So, combo CLI it is. I'll

11:13

treat nutritionalvalue.org as a primary

11:14

source headline commands top of the read

11:16

me first run experience USDA as a

11:17

secondary.

11:20

Let's go with Piers no primary. All

11:22

right, so

11:26

Now, am I in trouble with Fable 5

11:28

safeguards flagged and safeguards are

11:29

intentionally broad right now.

11:32

These measures let you bring I don't

11:33

know what's going on. Hopefully it still

11:35

works.

11:35

>> Did they change the model or is it still

11:36

using Fable?

11:37

>> I'm not sure. So anyway, so that's

11:39

that's going in there. So now let's go

11:41

over here.

11:42

All right. Short answer, the learning

11:44

that got stored was the wrong kind to

11:45

help the second question. The kind that

11:47

would have helped was never recorded and

11:49

even a perfect hit would have maybe

11:51

shaved maybe a third of the time.

11:54

What got caught was a per game fact and

11:56

the second question was about a

11:57

different game. The Belgian session

11:58

taught this query maps to this event. My

12:01

England session run recon on the CLI

12:03

correctly rejected the learning. The

12:05

transferable knowledge was never saved.

12:07

What both sessions actually rederived

12:08

from scratch was the method. The World

12:10

Cup league code is soccer.fifa.world.

12:12

The date flag is {dash} {dash} dates not

12:15

{dash} date.

12:16

Even a warm hit would have made it feel

12:18

fast.

12:19

>> So basically it's just saying that it

12:20

didn't properly map how to get to World

12:22

Cup's

12:23

information quickly.

12:24

>> Yep. So the fix now applied. So I

12:28

recorded a playbook for the query

12:29

family. And so I'm actually going to

12:31

yell at it right now. So this will be

12:32

fun. So I'm going to start with a CE

12:33

plan.

12:36

I don't want you to fix this for me.

12:38

What I actually want you to do is I want

12:40

you to submit a PR to the printing press

12:45

library for the ESPN CLI so that it can

12:48

learn not how to find the World Cup but

12:50

how it can learn to self-heal itself in

12:53

the future when something like this

12:54

happens.

12:55

And so the that's the promise of a

12:57

self-healing CLI and clearly you failed

13:00

and what you've built so far is not

13:01

working out. So I need you to go deep

13:03

and figure out how to systematically

13:06

programmatically

13:07

fix this not just for ESPN and future

13:09

events. Could be a tennis event. Could

13:11

be something else. This isn't about the

13:12

World Cup. I think this is a good

13:14

example because when we did the original

13:15

HAR sniff, the World Cup wasn't

13:17

happening and so it doesn't know how to

13:19

map to the World Cup. But the whole

13:21

point of a self-learning CLI is to do

13:24

that. So there's two paths I want you to

13:26

figure out here. One is what should be

13:29

the change to the ESPN CLI, but two this

13:33

we want to build a self-healing CLI into

13:35

every single press, everything that

13:38

happens within the printing press. So I

13:41

need you to look at the actual printing

13:43

press code to figure out how we can do a

13:46

better job here.

13:47

>> This is like Matt Van Horn ASMR leaning

13:51

into the mic

13:53

talking to to your agent. That's great.

13:55

Um one question, what what is

13:57

what you use the the phrase sniff HAR

14:01

sniff what what is that referring to?

14:03

>> Yep. Uh by the way, it's accidentally

14:06

building a PR for that thing we said

14:07

before. I don't know.

14:09

I don't think I asked it to start

14:11

writing code and building it, but this

14:12

is that open CV thing. There's a plan

14:14

written, there's a fix committed.

14:16

There's a build verified. Okay.

14:18

>> So it's actually submitting a PR for

14:20

whatever that bug was. That's

14:22

>> Apparently I I literally was not using

14:24

my normal open source software stack. So

14:26

it was just doing things. I'm going to

14:28

I'm just going to skip that one right

14:29

now.

14:30

>> Okay.

14:30

>> Um

14:31

all right, the US needs a free API key.

14:33

API.data.gov no key is set up in your

14:35

environment. How should I handle this?

14:37

Um

14:39

>> So what which which one is this? Which

14:41

job is this that we're working on right

14:43

now?

14:43

>> Sorry, am I This is now we're we're on

14:46

the the printing press one. So I need to

14:48

sign up for an API key for API.data.gov.

14:55

How do I get one of these?

14:57

It's a free for federal agencies. I'm

15:00

not a federal agency. I'm so confused.

15:04

I'm not a federal agency. How do we get

15:08

one of these?

15:10

Um so

15:11

>> way, that I don't know if this is like

15:12

possible, but the this it feels like

15:14

such a thing now when you whenever

15:16

you're building stuff now it feels like

15:18

you constantly have to go and retrieve

15:19

API keys. Like we as the human are just

15:21

like the

15:24

the the errand boy of our agents to get

15:27

API keys. I've been thinking now like,

15:29

is there ultimately going to be a way

15:30

easier way to get API keys than us

15:32

having to go to sites to get them for

15:34

our agents?

15:37

>> Yes, soon. They're better be.

15:39

>> Yeah.

15:39

>> So, here's here's another window I want

15:40

to kick off going, well, so

15:43

this is my start I sent this message

15:45

right before we started talking. So,

15:46

this is a new window to this context of

15:48

this conversation. I said, I made a PR

15:50

to for self-improving CLIs that agents

15:52

leave notes for future agents, did it

15:53

merge? What's the status? Cuz I know

15:55

Trevor was supposed to look at it.

15:56

And I didn't remember if it had shipped

15:58

or not.

15:59

And he's like, it merged. So, great. And

16:02

I was like, why haven't I seen it? I was

16:03

like, okay.

16:04

Is it working? Can you see all the So,

16:06

theoretically, all CLIs, new ones

16:09

printed after this point, should um

16:13

should um

16:14

have it.

16:16

And it said, no.

16:18

>> Mhm. And so, in theory, if this had

16:20

worked, if we go back to the uh ESPN and

16:22

World Cup example, you should have been

16:24

able to very quickly just get

16:26

information on the Belgium or England

16:27

game because the ESPN CLI should have

16:31

through self-healing mapped how to get

16:32

the World Cup information.

16:34

>> Exactly.

16:35

>> Yeah.

16:35

>> And so, I had hand-built ESPN in the

16:38

prediction go with self-learning.

16:41

But, I wanted everyone that makes a new

16:43

one to also have the self-learning. And

16:45

so, I'd spent a lot of time with the

16:46

ESPN one working on that. And so,

16:49

anyway, but here's the thing.

16:51

Apparently, what I built never pulled it

16:53

all together.

16:54

>> Oh, no.

16:55

>> Adoption is zero. I code searched the

16:57

whole thing.

16:58

The reason it's gating, the loop is

17:00

opt-in for the spec.

17:02

Apps are disabled with a benign go

17:04

no-go. And here's the gap, it just never

17:06

mentions enabling it.

17:09

So, now I'm going to say,

17:14

I'm doing a live demo right now, and

17:16

this is making me look really bad. And I

17:17

said that I was working on this

17:20

this self-learning CLI feature, and that

17:23

you told me it was merged and live, but

17:25

apparently it's not. I want this

17:27

default on, and I want it to be high

17:30

quality. So, if there's anything that's

17:32

not high quality about this, any reasons

17:33

it should be off, like I want every new

17:36

CLI that's printed to be able to have

17:38

this. And if the product's not good

17:40

enough, then we should talk about that.

17:42

So, I want you to do a deep dive into

17:44

this and figure out A, how we turn this

17:46

on, and how we start printing things

17:48

with self-learning turned on, so that we

17:50

can learn from actual data of new CLIs

17:53

that are printed in the printing press

17:55

if this is a valuable feature or not. I

17:57

think it's extremely valuable, and if

18:00

it's not valuable now, then we need to

18:01

make it valuable. So, I believe in you.

18:04

Go, Agent, go.

18:06

>> [laughter]

18:07

>> By the way, what do you use for

18:09

for yap to text? I love the little icon

18:11

in the bottom right that shows as you're

18:13

talking.

18:15

>> Yes, so this is

18:17

um

18:18

uh Monolog.

18:19

>> Cool. Oh, love it. Love it.

18:22

>> And so, all right, let's see. We've got

18:24

other stuff going on here.

18:25

I have the grounding any, the press

18:27

already does this. Okay.

18:30

So, let's make it a plan there.

18:31

>> So, basically, just to reorient, the

18:33

things we're working on right now is we

18:35

have the nutrition, whatever it is,

18:37

nutritionfacts.org,

18:38

which we were trying to create the print

18:40

it the new printing press CLI for, so we

18:42

can pull nutritional information. You

18:44

basically hit a wall there cuz it was

18:45

like, "Ah, you can't programmatically

18:47

pull information from the site." But

18:49

then you were like, "Let's just build a

18:50

combo CLI that's primary from nutrition

18:53

facts, and then from USDA if you can't

18:55

pull from that." That's one. The second

18:57

is the ESPN CLI and making it

19:00

self-healing, so it pulls the right

19:01

information. The third it was this

19:03

OpenCV bug that you somehow were fixing

19:06

even though you didn't know.

19:07

>> Yep. I I just closed that for fun cuz I

19:09

it wasn't running my right stack.

19:11

>> Cool. And then, is there anything else

19:12

we had going?

19:13

>> I think that might be it. So, it's it's

19:15

struggling with that that nutrition

19:16

value thing, which is uh this is a good

19:18

demo cuz it shows that some stuff does

19:20

not

19:21

uh want to be safe. So, anyway, I'm

19:23

going to browser sniff it anyway. So, I

19:24

could say that it could hand author an

19:25

HTML spec.

19:27

So, endpoints from the structure I

19:28

already mapped. Fast, no browser data,

19:30

standard HTTP, browser sniff it anyway.

19:33

So, let's try.

19:35

>> What does browser sniff mean? Is it just

19:36

literally studying the site?

19:38

>> Yeah, so it it's

19:40

like

19:41

um way to think about it is

19:43

uh when you load a webpage, you click a

19:45

link, or something happens, um it

19:48

there's a it's calling APIs on its own.

19:51

And sometimes

19:53

um

19:53

they people want to

19:55

hide them. Like LinkedIn loves hiding

19:58

their stuff because people like to

19:59

scrape their content and things like

20:01

that. Kind of bot abuse type stuff. But

20:03

like a site like this, like I don't know

20:04

I don't know why it's why they care so

20:06

much. Um

20:08

And so, like and here's one that makes

20:10

me really mad. I I love uh

20:12

I love Hyatt.

20:13

>> Mhm.

20:13

>> I'm like

20:14

uh

20:15

always trying to get globalist every

20:16

year. And uh

20:18

they have so much security on Hyatt,

20:21

it's extremely frustrating cuz all I

20:23

want to do is spend more money and spend

20:25

more points at Hyatt and have my agent

20:27

be able to book me hotel. And they have

20:30

some of the highest security

20:31

>> it's like Fort Knox. Like you cannot

20:33

build a CLI to Hyatt.

20:35

>> It exactly. So, anyway, it's it's trying

20:37

now to to do this over here.

20:40

All right. Confirm the scope and I'll

20:41

proceed. Um

20:43

force it on all prints.

20:45

Yes.

20:48

>> So, this was the the self-healing, just

20:50

making sure it's applied to everything

20:51

printed from the printing press.

20:53

>> Yep. Exactly.

20:54

>> Cool.

20:54

>> And so, that that's running there.

20:57

Um this one's analyzing the learn loop

20:59

pattern. So, I think this is our

21:00

football one. Yeah, this is our football

21:02

one. So, it's kind of trying to figure

21:03

out what's going on with with the ESPN

21:05

here.

21:06

>> What one question just as these are

21:07

running is um and and by the way as

21:09

we're talking through this if there are

21:10

any other agent agentic hacks that we've

21:13

missed that you think are important to

21:14

call out feel free to call them out on

21:16

the compound engineering piece like why

21:18

do you why have you liked compound

21:20

engineering the process so much and like

21:23

can you just roughly outline like the

21:25

way that it works like if you were to

21:26

build something from scratch that isn't

21:28

one of your existing tools right now

21:30

what would be kind of the sequence of

21:32

using compound engineering?

21:33

>> Yeah, so the moment you have an idea

21:35

make a a CE plan.md. And so

21:38

the the basic gist is is agents are

21:41

inherently lazy like they want to work

21:44

as little as possible to make you as

21:46

happy as possible. It's kind of like

21:47

that that that tricky balance. And

21:50

something that I found that's extremely

21:52

valuable is to to force the agent to

21:56

write itself a plan file. So think of it

21:58

like like a source of truth a a text

22:02

file that it's always going to go back

22:03

to to make sure that it doesn't like

22:05

lose track of things cuz agents can

22:07

either end things abruptly when they get

22:10

lazy or they end up on a tangent and

22:12

they kind of forget their original

22:13

purpose.

22:14

And so compound engineering I think does

22:16

the most thoughtful job of writing a

22:19

high-quality plan.md file

22:21

for your agent. And I think one of the

22:23

biggest shifts cuz

22:25

I've sorry I've written two of these

22:26

agentic engineering hacks articles and

22:28

the the first one says like make a plan

22:30

and then use this editor to read the

22:31

plan and modify it. And the newest

22:34

version says never ever read the plan.

22:38

Right? So don't read the plan.md.

22:41

[snorts]

22:41

I always make the plan.md. I almost

22:43

never read it. Plans are for agents you

22:45

silly human.

22:46

>> So it's the same reason you say don't

22:47

read the code. Same idea.

22:49

>> Exactly. So again this is like how my my

22:52

change and philosophy has shifted over

22:55

time. So the the first is like should

22:59

never read the code. Now it's never read

23:00

the plan. And you can uh ask questions

23:02

of the

23:03

>> Next it's going to be just never read.

23:04

In life, never read.

23:05

>> Again, [laughter]

23:06

like I I have a problem with the name of

23:08

your podcast because I don't want to be

23:09

in the loop. Like fire me. Please. Like

23:12

like I just

23:14

I want to be I want to be removed from

23:16

this uh

23:17

which is uh and so yeah, so kind of just

23:21

again, how I started with I want to

23:23

build a programming language from

23:24

scratch was CE plan and then using my

23:27

voice was just like

23:30

I have this crazy idea. I don't know if

23:31

it's good. Tell me good ideas, bad

23:33

ideas, do research. CE plan is also

23:36

very, very good at

23:38

at research and kind of searching the

23:40

internet and like again, back to

23:42

dangerous skip permissions. Like

23:45

it

23:45

uh without dangerous skip permissions

23:47

on, it's like, is it okay if I go to

23:48

google.com and look for something?

23:51

Is it okay if I go to this webpage?

23:54

Like, what? Yes. What are you doing?

23:56

>> exhausting, yeah.

23:57

>> Like like we need to we need to move.

24:00

Um

24:02

and so it's see what I even know what

24:04

This is the self-improving CLI.

24:07

Um

24:10

Okay, so this is the one where it's

24:11

trying to fix the overall

24:12

>> Yep.

24:14

>> one there. This one is doing something

24:17

with nutritional values.

24:18

Their internal IDs are for USDA IDs and

24:20

it is data is USDA data, but NV So

24:23

anyway, it's

24:24

it's learning something.

24:25

>> And and again, when people hear

24:26

self-healing CLI again, I think for like

24:29

a non-technical person, they're like,

24:30

that sounds super technical.

24:32

Self-healing, what what does this mean?

24:34

Is the self-healing CLI literally just

24:36

like it is a markdown file that has

24:39

notes about previous learnings with the

24:42

CLI that the CLI reads before it takes

24:45

action to kind of know where it should

24:47

go?

24:48

>> Exactly, yeah. So the the the

24:50

Yes, you you've nailed it, but the the

24:51

the clearest example of what this world

24:53

like when we built the ESPN CLI, it

24:55

didn't know the World Cup

24:57

match patterns, right? It knows how to

24:59

find NBA games. It knows how to find MLB

25:01

games very quickly. That pattern has

25:03

been that way for a long time.

25:05

It has no idea how to find a World Cup

25:06

game because when it was taught,

25:09

it didn't know. So, an agent is fumbling

25:11

around looking for, "Okay, where's the

25:13

World Cup? How do I find this?" and and

25:16

go from there.

25:17

>> Cool.

25:19

>> And then let's see what else is fun in

25:20

the article. So, so this is a good one.

25:22

So, you CE plan for your deepest

25:24

non-engineering

25:25

um work, make a plan for the plan. So,

25:29

this this is really magical. So, the the

25:31

example I gave in the article here was I

25:32

was meeting with uh Michael Mauboussin,

25:35

uh who used to run uh was the research

25:37

partner at Google Ventures.

25:39

And so, kind of very focused on like

25:40

product market fit for for businesses.

25:43

And one of the things he said was, "Oh,

25:45

you should like read my book. It's uh

25:48

it's would be great to to think about

25:50

your your challenge and problems." And

25:52

so, what I did, so I I Granola

25:54

everything. Uh so, Granola's one of my

25:56

favorite pieces of software. It takes a

25:58

transcript of any conversation that that

26:01

you have.

26:02

And you can copy that whole thing into

26:04

your your agent and use that.

26:07

>> Yep.

26:07

>> And so, in our whole meeting with

26:08

Michael, I was like, "Hey, can I can I

26:10

Granola this? I would love to like jam

26:12

with you on product market fit stuff for

26:14

for my business."

26:15

And so, we had a really good

26:16

conversation. It was like a 2-hour

26:18

conversation. And then he was like, "You

26:20

should read my book." And so,

26:23

in an agentic world,

26:24

like I want to take the context that I

26:27

have from the 2-hour meeting. So, I took

26:30

the entire 2-hour Granola. So, I did CE

26:33

plan, make a plan for the plan

26:36

um

26:38

of I want you know about my business. I

26:41

want to work on product market fit uh

26:43

and a plan. Um I want you to in a

26:46

non-lazy way read Michael's book. And I

26:50

I you to take the context from this um

26:53

meeting we had from him to create a plan

26:57

of

26:58

of how how we work together on this

27:00

business problem.

27:01

And so, what it did was because it wrote

27:05

this plan on MD file,

27:07

um

27:07

and by the way, this process was the

27:10

longest research pro- process I've ever

27:12

seen Cloud Code do. It spent about an

27:14

hour on this.

27:15

>> Wow.

27:16

>> And what it did is it read every single

27:19

chapter and wrote it required itself I

27:21

didn't come up with this the agent came

27:22

up with this to write itself a book

27:24

report about each chapter

27:27

and specific to my business.

27:31

And

27:31

>> Crazy.

27:32

>> that and it put together this crazy plan

27:35

that was

27:36

really wild. And another example of

27:37

something kind of a very

27:39

a normie thing to do was to use um

27:45

to use

27:46

uh CE plan to plan a Disney World trip.

27:50

So, the first thing I did is I ran last

27:52

30 days on Disney World to see like,

27:54

"Hey, is there anything new that's

27:55

opening soon? New firework shows? New

27:57

New things like that?" To kind of just

27:58

get the the download of like the latest

28:00

stuff from Reddit X, what people are

28:02

talking about, what are the longest

28:03

lines, what secretly has the shortest

28:05

lines, where should you go at rope drop?

28:07

Like these sorts of like important

28:09

social signals. And then I was like,

28:11

"Okay." And I was like, "I have a

28:13

10-year-old, an 8-year-old, 5-year-old,

28:15

and 2-year-old. I need you to map out

28:17

what rides everyone can go on and can't

28:20

go on. I don't know their heights. I

28:22

don't know how many inches they are. So,

28:23

you have to make assumptions. Assume

28:25

The two older ones are tall, the others

28:26

are average." Um and uh

28:30

go. And it asked me a few questions and

28:32

then it created this whole thoughtfully

28:35

designed

28:36

uh

28:37

web page uh which was really really

28:39

nice. And it also gave me instructions

28:42

to give to my Open Claw

28:43

of the reminders is like, "By the way,

28:46

like 7 days before your date in the

28:48

park, you need to sign up for this pass

28:50

to like skip the lines and it opens at

28:52

like 6:00 a.m. East Coast time.

28:55

Um you should add it to your calendar

28:56

and copy this to your um

28:59

your open clause so that it it will do

29:01

this automatically.

29:02

>> That's awesome. I love that. And and

29:05

just thinking about the alternative,

29:06

like if I think about that Disney trip,

29:09

if you did not have CE plan and if you

29:11

did not have last 30 days,

29:13

you know, the average person would just

29:15

go type into

29:17

uh Claude, co-work, Claude code,

29:19

whatever, chat. Um they would basically

29:21

say, "I'm going to Disney World with my

29:23

family. Build me a plan. The the I have

29:25

four kids. The these are their ages."

29:27

Like they give the same context, but

29:30

my assumption is it would not be nearly

29:33

as tuned to what matters now at the park

29:36

versus what generally matters. And it

29:39

would not be tuned to like also context

29:41

about you in how this uh this plan to be

29:45

executed on given kind of the agentic um

29:48

workflows you already have like at your

29:50

disposal.

29:51

>> Yep.

29:52

Yep.

29:53

>> Yeah. So they By the way, our last 30

29:54

days result came in for your World Cup.

29:56

>> Oh, nice. What came in?

29:57

>> So Paraguay knocking out Germany is the

29:59

story of the tournament so far. Paraguay

30:01

held Germany 1-1 through extra time and

30:02

won the shootout 4-3.

30:04

Germany's first ever World Cup penalty

30:06

shootout loss.

30:08

Um

30:10

and then, let's see, Jen someone to

30:12

break down what went wrong for Germany.

30:15

Um let's see, US Ventis finally won a

30:17

knockout game and fans are euphoric and

30:19

salty about the ref.

30:21

Um

30:22

and so it's pulling in from Reddit.

30:25

World Cup thread on red card rules

30:26

mainly for the Balligan situation blew

30:28

up with 3,000 upvotes and 5,000

30:30

comments.

30:31

"They forgot to add the referee to the

30:33

Bosnian starting lineup," quipped Goofy

30:35

Graffer.

30:37

Um England versus Mexico is the next

30:39

blockbuster and DR Congo won hearts on

30:42

the way out. This is awesome.

30:44

Uh the top comment

30:46

on this video was pure joy worded here.

30:49

We lost, but I'm proud of my country. We

30:51

tried. Congo Congo emoji with 5,700

30:55

likes. Uh England vs. Mexico about to be

30:58

a blockbuster movie.

31:02

Money says France with Argentine right

31:04

behind it. The Polymarket World Cup

31:05

market has France as the clear favorite,

31:08

roughly 33% after their free around 32.

31:11

Argentina around 22%.

31:14

And there's even a live market whether

31:15

Declan Rice wins the Golden Ball.

31:17

And Messi to win the Golden Boot with

31:18

44%.

31:21

This is awesome.

31:22

Yeah, now what's so interesting is like

31:24

I'm just thinking about all the

31:25

different ways that last 30 days, like I

31:27

know this is just like a a side project

31:30

for you, but I'm just thinking about

31:31

like there are actually so many ways it

31:32

could be commercialized. Like I think

31:34

about like um you know, Greg Eisenberg

31:37

has like his startup ideas finder type

31:39

thing. Like I could imagine that type of

31:41

thing, but using last 30 days with all

31:44

these signals about the biggest problems

31:45

people are experiencing

31:47

um in a post-AI world, whether

31:49

personally or professionally. And then

31:51

also I think about like how big the

31:52

market is for social listening for

31:54

companies. And how good this would be

31:57

for companies doing social listening

31:59

into their consumers.

32:01

Yeah. Totally.

32:02

>> Very cool.

32:04

>> Okay, so here we go. It's

32:06

Nutrition PPCLI absorb manifest.

32:09

So, 15 absorb table stakes features and

32:11

seven novels, so 22 features for this

32:14

CLI. The field is wide open. No mature

32:16

USDA CLI exists. Best competitors under

32:18

five stars. Nutrition value has almost

32:20

no tooling. This shifts past every eight

32:22

competitor with offline caching, agent

32:24

native output, and cross-source

32:26

enrichment nearly no other tool has.

32:28

The architecture, it's an aggregator

32:29

combo. It uses USDA's open API seeds.

32:32

Then generated baseline search get batch

32:34

and SQLite store. Nutrition value is the

32:37

hand-authored HTML so that both feed one

32:39

unified food store keyed on source and

32:42

ID.

32:43

Since the keys are the same FD

32:45

ID is cross-reference to be exact. The

32:48

seven novel features all hand code

32:49

granted in three personas. So literally

32:52

it came up with three personas of power

32:55

users of this nutrition app. So it

32:57

pretended to be Marcus the power lifter,

33:00

Dana the low-carb dieter, Priya the

33:02

agent builder to think about what their

33:05

use case would be and why they want this

33:06

CLI.

33:07

>> So crazy.

33:08

>> It came up with enrich. Merges nutrition

33:11

values derived analytics and that carves

33:13

omega-6-3 database percent onto a USDA

33:16

record. The Helen feature numbers no

33:18

USDA API call returns resource with only

33:20

two scrapers total.

33:22

Rank top bottom foods by any 16

33:25

ingredients category data set

33:27

filterable. Compare 1,000 kcal two to

33:31

five foods side by side per 100 g per

33:34

serving. No existing nutrition CLI

33:36

offers a comparison basis at all. Find a

33:38

minimum protein 20 compound

33:41

multi-nutrient threshold discovery.

33:43

Marcus is high protein under 165 kcal in

33:47

one step. This is blowing my mind by the

33:49

way.

33:50

>> Crazy crazy.

33:51

I also just don't understand how I don't

33:53

actually understand how this pulled it

33:55

off when it started by say two things

33:57

that felt like blockers. One is it said

33:59

it couldn't do any sort of like

34:00

programmatic pulling of data. So I don't

34:02

understand how it got around that. And

34:04

then second, you had to get an API key

34:07

from like a government website which you

34:09

didn't do. So how did it get all this

34:10

information without doing those things?

34:12

>> It hasn't built it yet. It's about to

34:13

build it. All right?

34:15

But here's what it says. Things to note.

34:16

No stubs. Everything list fully

34:17

implemented. Pure balance NV leads the

34:20

top two novel commands and powers the

34:21

original USDA backs the rest. NV can't

34:24

have more commands cuz its value is an

34:26

overlay and shared ID data not a

34:27

separate feed.

34:28

Nutrition value terms of service. It's

34:30

homepage prohibits scripted access. You

34:32

approved building against it. Yolo

34:34

[laughter] mode. The CLI stays polite,

34:37

honest UA, conservative rate limiting,

34:40

no crawling, and the read me will

34:42

document this copy. So, it's not going

34:44

to be super aggressive. So, it's built

34:46

it's it's it's planning to build its own

34:48

rate limiting

34:48

>> Yep.

34:49

>> into it because it knows it's not

34:51

allowed even if it has top blockers.

34:54

>> Uh seven candidates were cut. This

34:56

adversary past killed anything on ver

34:58

So,

34:58

>> That's so crazy.

35:00

>> approve, generate now.

35:02

I have ideas to add, trim scope, review

35:05

full manifest file. So,

35:07

let's approve.

35:08

>> Crazy. And like

35:10

I know this it we're like demoing this

35:12

now, but like this is how you would go

35:13

through the process of printing a new

35:15

say a say a light, right? This is like

35:17

exactly how you do it.

35:18

>> Absolutely.

35:19

>> Cool.

35:20

>> If there there is there is still other

35:21

process.

35:22

>> Yeah.

35:22

>> And if And if I'm unhappy with something

35:25

here, I would then literally copy this

35:28

whole thing.

35:29

And I like I I would do this, but I'd be

35:31

like, "Hey,

35:34

this is called the Yolo printing press.

35:35

I have Yolo mode. There's no Yolo mode.

35:37

Like Like don't ask me dumb questions on

35:40

if I want to scrape it or not. Like

35:42

That's how I would literally I could I

35:44

could do it for fun. Just being silly.

35:46

Um

35:47

So, I could say,

35:49

"See plan.

35:52

I want to create a Yolo mode within the

35:54

printing press. So, if you have that,

35:56

use the flag Yolo, then it will not ask

36:00

me stupid questions about if I want to

36:02

scrape things or go against terms of

36:04

service or or things like that. Can you

36:06

build that into the printing press?" And

36:08

I'm going to copy and paste a recent

36:10

conversation that I had uh with an

36:12

agent, and it asked me too many

36:14

questions and told me things were

36:15

against terms of service, but I I run in

36:17

Yolo mode, so I don't really care.

36:19

By the way, just want to say I'm not

36:20

going to build this, but I just want to

36:22

show you like how I think.

36:24

Right? And so,

36:25

>> I would I wouldn't be mad if you did.

36:27

That's hilarious.

36:28

>> I believe in following terms of service

36:29

[laughter]

36:30

and and all these things. I'm being

36:33

silly here. But anyway, so I I copied

36:35

and pasted this in here and now

36:37

>> I wonder do you think do you think it'll

36:39

do you think it will actually build this

36:41

for you or do you think it'll end up

36:42

getting flagged and not build it?

36:45

>> Look

36:46

just judging that webpage, I doubt they

36:48

have very good bot protection.

36:50

>> Yeah, yeah, yeah,

36:51

So interesting.

36:52

>> So we might get a letter.

36:54

>> So while while it's

36:56

>> Please don't do this. This is against

36:57

our terms of service.

36:59

Uh which which is

37:00

totally fair.

37:01

>> Yeah, totally.

37:02

>> Recorded on video knowing that maybe I

37:04

shouldn't submit this one if it does

37:06

work. But

37:08

I want to give more more exposure to to

37:11

what they're doing cuz it's it's cool

37:12

stuff.

37:13

>> Totally. While this is running, anything

37:15

else on the agentic hacks article that

37:17

you think is worth covering?

37:19

>> Some of things. Get voice built like and

37:21

by the way, I have this

37:23

giant

37:24

>> Yeah, it looks like you're an air

37:26

traffic controller now.

37:27

>> And what's what's funny is

37:30

I don't the the mic on my computer is

37:33

perfectly fine. Like I literally do not

37:35

need this,

37:37

but it's placebo.

37:39

Like I feel like my computer's listening

37:42

me better cuz I have a big stupid

37:43

microphone. So like I I recommend that.

37:47

I like C mux. I hear great things about

37:49

Orca. I used to

37:50

love Ghosty. But I've I feel like there

37:53

are better things now.

37:55

This is a very simple good one. So make

37:58

your terminal default into Claude or

37:59

code text code text not a shell. Like so

38:02

again, something very very simple, but

38:03

when I load a new window

38:05

>> It's just Claude.

38:06

>> It just starts in Claude code.

38:07

>> How do you actually do that? How do you

38:09

make that the default?

38:11

>> I think I tell you exactly what to copy

38:13

paste right here.

38:14

>> Sweet. Paste this to your agent. Make

38:15

every new terminal open directly into

38:17

Claude code.

38:18

>> Sweet.

38:19

>> And then

38:21

This is a good one. so turn on remote

38:23

control for every window.

38:25

So, I'm I have a lot of kids and often

38:28

on the go or soccer practice, things

38:30

like that. And so, um automatically

38:32

turning on remote control in every

38:34

window, so I could just use the Claude

38:35

code app to continue a task from

38:37

something that's running on my computer.

38:39

Uh another fun one is you can give Code

38:41

X or Claude code an email address

38:43

through Agent Mail.

38:45

And so, when I was

38:46

I tweeted, "Hey, I'm working on update

38:48

for this article. Anyone have any hacks

38:50

they're proud of?" And the founder of

38:51

Agent Mail was like,

38:52

"Give Claude code an email address." I'm

38:54

like, "What does that even mean? Like,

38:56

what

38:57

Why why does Claude code need an email

38:59

address?" And he's like, "You'd be

39:00

surprised." I was like, "All right, I'm

39:01

just going to listen to you and see see

39:03

how it goes."

39:03

>> And what happened when you gave it an

39:05

email?

39:06

>> Um

39:07

it I came up with a really valuable use

39:10

case for me.

39:11

So, I I I run

39:14

So, my dev environment here is

39:17

tuned to this one computer, yeah, right?

39:19

So, I do all my development on my almost

39:22

maxed out MacBook Pro.

39:24

Um and so,

39:26

when I'm

39:27

remote, like how and Claude code doesn't

39:30

allow you right now to start a new

39:32

session on your remote computer.

39:36

And so, I'm sure they'll solve that very

39:37

soon. They're close.

39:39

But, so what I've done is complicated,

39:41

but I set up a way for my Air mess, I

39:45

could just be on my phone in Telegram,

39:46

talk to my Air mess. You can set this up

39:48

for open Claude 2. And

39:51

you say, I just set up a hook that says

39:53

like,

39:54

"CC"

39:56

and that means go talk to my Claude code

39:58

on my computer.

39:59

CC, that's the thing I set up. Um and

40:02

I'll say like, "CE plan, um

40:05

I want you to

40:06

build this feature for me."

40:08

And then what it does is it actually

40:11

emails

40:13

>> [laughter]

40:13

>> my computer.

40:15

It emails my main computer

40:18

and with with authentication that it's

40:20

me.

40:21

Uh you can't just email my computer and

40:23

load terminal windows.

40:25

Um it emails my computer and starts the

40:28

task and then

40:29

>> Wow.

40:29

>> just goes and then it's just like again,

40:32

very very simple thing but like has been

40:34

very very valuable and very very

40:37

>> so funny that like one is just like

40:39

human ingenuity is amazing and it's so

40:41

funny like that is the workaround to be

40:42

able to work from your main computer uh

40:45

until you know

40:46

uh open AI and Anthropic figure it out.

40:49

>> Yes. Uh dangerous good permission we

40:50

covered.

40:52

Um

40:54

Um I so I I always hit my Claude code

40:57

limits every week

40:59

and I I rarely hit my Codex ones. So I

41:02

send as much coding as possible to to

41:05

Codex.

41:07

Cuz I I've built all my skills around

41:08

Claude code so it's hard for me to leave

41:10

the Claude code CLI but I do honestly

41:13

most of my software writing is done

41:15

through Codex and so there's ways to do

41:16

that. I actually forgot with the pretty

41:18

press I actually

41:20

meant to type in

41:21

Codex mode. So there's no yellow mode

41:23

but there's Codex mode where it'll

41:25

actually print the CLI

41:27

as much as it can in Codex. So I forgot

41:30

to do that. By the way, it asked a

41:31

question, how far should yellow mode go

41:33

for suppressing questions? All optional

41:35

questions, terms of service consequences

41:37

questions.

41:38

>> Full yellow.

41:40

>> [laughter]

41:40

>> I I'm not going to build this feature

41:42

but this is just an example. There's a

41:44

few questions so I'll

41:45

>> Yeah.

41:46

>> All optional questions.

41:48

Auto approve everything.

41:51

Per run flag and keyword. If you use

41:53

dash dash yellow or the word yellow

41:54

anywhere in the application plus type in

41:56

yellow mid run flips it on the rest of

41:58

the turn. Skill scope main pretty press

42:00

only. All skills.

42:03

>> So good.

42:05

>> And so I get like confident engineering

42:08

dug into my very simple prompt. It dug

42:11

into the code base. It dug into what I'd

42:14

done in that other window where it saw

42:15

the examples of it asking me questions

42:19

and it came up with this and this would

42:21

actually then

42:22

write a real plan for an agent to go

42:25

execute on.

42:26

>> Love it. Awesome. Well, I know I want to

42:29

wrap wrap things up. What else in the

42:32

last minute or two? Anything else you

42:34

want to cover?

42:35

>> Human signal, this is an important one.

42:37

So, as much as I joke about wanting to

42:39

be out of the loop, I think human signal

42:41

is more powerful than ever. Like you

42:42

think about last 30 days, it's about

42:44

pulling the best content from Reddit, X,

42:46

YouTube, TikTok, like human signal is so

42:49

so so important and kind of this

42:52

it's becoming so easy to build things

42:54

and the bigger question is what what

42:56

should we actually be building and I I

42:58

think that's that's very important.

43:00

>> Cool. Matt, this is

43:03

this was awesome. You're an absolute

43:04

machine and I learned so much during

43:07

this and honestly gives me a ton of

43:08

confidence to keep building despite

43:11

being a a non-technical midwit. So, this

43:14

was super helpful.

43:16

>> Awesome. This was fun, Alex. Thank you.

43:17

>> Thanks, man.

Interactive Summary

Matt Van Horn, a non-technically trained but prolific builder, discusses his unique philosophy on AI-driven software development. He advocates for 'agentic engineering,' where autonomous agents handle the coding, reading, and planning processes, allowing humans to focus on high-level problem solving. Throughout the conversation, he demonstrates practical examples of building CLIs using his 'Printing Press' tool, emphasizes the importance of 'compound engineering' and self-healing systems, and shares his perspective on why human intuition and signaling remain crucial in an automated future.

Suggested questions

4 ready-made prompts