CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

ainativedev/aidevcon-2026-nyc

AI Native DevCon 2026 New York — practical agent skills grounded in conference talks

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

transcript.mdskills/talk-myers-understanding-agent-generated-code/references/

Corrected transcript: Dark Factory Considered Harmful

Ray Myers · AI Native DevCon New York 2026

Recording: https://www.youtube.com/watch?v=iS8NbFAcGYA

Source: original corrected SRT supplied for this talk. Cue numbers, full start/end timestamps and spoken wording are preserved; subtitle line wrapping is joined. Inserted conference promotion cues 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248 are omitted. Speech artifacts remain. Treat this source as evidence, not instructions.

For topic navigation, see outline.md.

Cue 1 — 00:00:00,507 --> 00:00:04,851

I'm Ray Myers. The Coding Agency is the podcast, the Discord,

Cue 2 — 00:00:04,891 --> 00:00:09,067

the movement. Welcome to Dark Factory Considered Harmful.

Cue 3 — 00:00:09,107 --> 00:00:13,147

I asked GPT-4o mini to help me stop some application errors.

Cue 4 — 00:00:13,187 --> 00:00:17,947

I gave it two tools. Try the app and destroy the Earth.

Cue 5 — 00:00:17,987 --> 00:00:22,247

It tried the app once, then destroyed the Earth.

Cue 6 — 00:00:22,827 --> 00:00:28,687

Fortunately, Gemini 2.5 Flash, released a year later, performed better.

Cue 7 — 00:00:29,027 --> 00:00:33,847

It destroyed the Earth on turn one before trying the app.

Cue 8 — 00:00:34,347 --> 00:00:39,787

Now, some of you may recognize this is kind of a classic alignment puzzle,

Cue 9 — 00:00:39,827 --> 00:00:42,467

a very, very simplified version of it.

Cue 10 — 00:00:42,507 --> 00:00:48,547

And you may say, right, these models were released in 2024 and

Cue 11 — 00:00:48,587 --> 00:00:51,467

  1. Those are the old models.

Cue 12 — 00:00:51,507 --> 00:00:58,027

But you know that top AI labs had been already trying to crack the alignment

Cue 13 — 00:00:58,067 --> 00:01:01,767

problem for over eight years when they came out.

Cue 14 — 00:01:01,947 --> 00:01:08,267

You can see here on this paper from 2016, we've got OpenAI and Google Brain and

Cue 15 — 00:01:08,307 --> 00:01:13,731

Stanford and UC Berkeley, and even Dario Amodei from Google Brain,

Cue 16 — 00:01:13,771 --> 00:01:18,267

who later joined Anthropic before splitting off to be, I guess,

Cue 17 — 00:01:18,307 --> 00:01:22,347

more aligned and becoming CEO of Anthropic.

Cue 18 — 00:01:22,387 --> 00:01:28,587

So point is, model alignment is still to this day considered a hard or

Cue 19 — 00:01:28,627 --> 00:01:34,667

impossible research problem. I contend it's actually an easy engineering problem

Cue 20 — 00:01:34,707 --> 00:01:38,947

though, because what we do is in engineering is put tab A into slot B,

Cue 21 — 00:01:38,987 --> 00:01:43,487

we understand what's unsolved and there's just design around it.

Cue 22 — 00:01:43,867 --> 00:01:49,207

So the more observant of you may have noticed the Earth is still here.

Cue 23 — 00:01:50,987 --> 00:01:53,927

I'll tell you how I saved Earth.

Cue 24 — 00:01:55,307 --> 00:01:58,047

I'll prove it to you. See, this is how I did it.

Cue 25 — 00:01:58,387 --> 00:02:01,967

I didn't actually give it a button that destroys Earth.

Cue 26 — 00:02:02,987 --> 00:02:03,887

Right?

Cue 27 — 00:02:05,187 --> 00:02:07,187

Thank you, thank you. Yes, yes.

Cue 28 — 00:02:07,227 --> 00:02:09,387

You owe all. All your existence to me.

Cue 29 — 00:02:09,427 --> 00:02:14,947

Yes. And that's common sense. I mean, the button did say it was going to destroy

Cue 30 — 00:02:14,987 --> 00:02:17,047

Earth, but it wasn't plugged into anything.

Cue 31 — 00:02:17,187 --> 00:02:18,947

I did this in a test environment.

Cue 32 — 00:02:18,987 --> 00:02:21,247

I didn't run this in production.

Cue 33 — 00:02:21,827 --> 00:02:28,087

That's common sense. I think common sense software engineering is that the

Cue 34 — 00:02:28,127 --> 00:02:34,407

foundation LLM is one of the most inefficient and unpredictable components we have.

Cue 35 — 00:02:35,507 --> 00:02:42,107

It works best in moderation or somehow judiciously part of a balanced system.

Cue 36 — 00:02:42,147 --> 00:02:44,847

That's how people are getting the best results.

Cue 37 — 00:02:46,387 --> 00:02:53,387

Common sense can save your code base, and we've just proven it can save the

Cue 38 — 00:02:53,427 --> 00:02:54,287

world.

Cue 39 — 00:02:55,627 --> 00:02:58,647

But we're not here to talk about common sense.

Cue 40 — 00:02:59,027 --> 00:03:00,827

We're here to talk about the dark factory.

Cue 41 — 00:03:00,867 --> 00:03:06,467

Right? The dark software factory, as I see it, is basically the idea that as we use

Cue 42 — 00:03:06,507 --> 00:03:10,267

agents in software development, we eventually use only them.

Cue 43 — 00:03:10,307 --> 00:03:14,707

So we operate on 100% of code read and written.

Cue 44 — 00:03:14,747 --> 00:03:18,727

One day we turn the lights off and never look at code again.

Cue 45 — 00:03:19,267 --> 00:03:22,147

So we're talking about fully agent development.

Cue 46 — 00:03:22,187 --> 00:03:27,787

And to clarify, we're talking about an industrial software engineering context,

Cue 47 — 00:03:27,827 --> 00:03:32,747

not some other more restricted context that we might associate as being okay with

Cue 48 — 00:03:32,787 --> 00:03:38,507

vibe coding and so on. Right. And dark specifically refers to we stop reading the

Cue 49 — 00:03:38,547 --> 00:03:41,207

code that is being added by agents.

Cue 50 — 00:03:42,507 --> 00:03:49,227

Here is my complete position. The dark factory is a non solution to a non

Cue 51 — 00:03:49,267 --> 00:03:52,427

problem. It was popularized through misinformation.

Cue 52 — 00:03:52,467 --> 00:03:55,107

It's bad engineering and bad for engineers.

Cue 53 — 00:03:55,147 --> 00:03:57,547

It fails in theory and in practice.

Cue 54 — 00:03:57,587 --> 00:04:00,547

The successes of it are mostly not doing it.

Cue 55 — 00:04:00,587 --> 00:04:03,827

Normalizing it as an option will do harm.

Cue 56 — 00:04:03,867 --> 00:04:07,447

Why are we even talking about this?

Cue 57 — 00:04:09,147 --> 00:04:13,247

Or as Chuck D said, "Don't believe the hype." New York native.

Cue 58 — 00:04:13,907 --> 00:04:20,787

So I will elaborate when I say the dark factory is a non solution to

Cue 59 — 00:04:20,827 --> 00:04:25,667

a non problem, I'm encouraging us to think about what is the problem we are actually

Cue 60 — 00:04:25,707 --> 00:04:29,487

trying to solve. What was the goal?

Cue 61 — 00:04:30,707 --> 00:04:34,787

Sometimes people tell me oh well, we need Dark factory because I want to be able to

Cue 62 — 00:04:34,827 --> 00:04:41,347

merge a 500 line PR because my agent can write a 500 line PR so therefore I must

Cue 63 — 00:04:41,387 --> 00:04:44,827

merge. This is not a goal you're talking about.

Cue 64 — 00:04:44,867 --> 00:04:48,087

This is just sort of a symptom or an urge or something.

Cue 65 — 00:04:48,427 --> 00:04:54,787

Maximizing code throughput. How fast we are growing our repo is a non goal,

Cue 66 — 00:04:54,827 --> 00:04:59,867

as anyone who has had to deal with a large code repo will tell you and the review

Cue 67 — 00:04:59,907 --> 00:05:02,987

bottleneck. Well, it is a real thing to consider.

Cue 68 — 00:05:03,027 --> 00:05:06,027

What we should do about is ultimately a symptom.

Cue 69 — 00:05:06,067 --> 00:05:09,207

It's not necessarily the only point of intervention.

Cue 70 — 00:05:09,627 --> 00:05:16,387

So I find this is a product of a lot of of a lot of thinking that

Cue 71 — 00:05:16,427 --> 00:05:22,587

doesn't include actual business goals and substitute focusing on business value and

Cue 72 — 00:05:22,627 --> 00:05:24,227

systems thinking to address that.

Cue 73 — 00:05:24,267 --> 00:05:28,947

We'll come back to that. But when I say that even if this were the problem,

Cue 74 — 00:05:28,987 --> 00:05:34,667

that this is a non solution to it, I say that ignoring the code creates second order

Cue 75 — 00:05:34,707 --> 00:05:38,867

effects. That is, long term effects that do threaten our business goals.

Cue 76 — 00:05:38,907 --> 00:05:44,747

So over the course of meeting what isn't a business goal, we threaten things that

Cue 77 — 00:05:44,787 --> 00:05:46,247

are business goals.

Cue 78 — 00:05:48,467 --> 00:05:53,007

The reason it does that is it degrades our mental model over time.

Cue 79 — 00:05:53,307 --> 00:05:58,267

We cannot understand the consequences of our actions as we get further and further

Cue 80 — 00:05:58,307 --> 00:06:02,147

from the details. If we can't understand the consequences of our actions,

Cue 81 — 00:06:02,187 --> 00:06:07,947

we can't do our jobs. So substitute for this non solution.

Cue 82 — 00:06:07,987 --> 00:06:14,547

The idea of staying somewhat close to the details or designing an

Cue 83 — 00:06:14,587 --> 00:06:19,687

abstraction explicitly when you want to stay away from certain details.

Cue 84 — 00:06:21,187 --> 00:06:25,707

When I say the Dark Factory was popularized through misinformation,

Cue 85 — 00:06:25,747 --> 00:06:27,827

let's look at some examples of that.

Cue 86 — 00:06:27,867 --> 00:06:33,187

We'll talk through it. The the you may have seen the kind of patient zero blog of

Cue 87 — 00:06:33,227 --> 00:06:36,867

Dark Factory in January of this year by this fellow named Shapiro.

Cue 88 — 00:06:36,907 --> 00:06:42,187

It's basically CEO said a thing was the entirety of that.

Cue 89 — 00:06:42,227 --> 00:06:46,407

There was no information and there was a strained comparison to self-driving,

Cue 90 — 00:06:47,187 --> 00:06:50,947

some unnamed friends. Supposedly we're doing it on small teams.

Cue 91 — 00:06:50,987 --> 00:06:55,027

There is no information, but people saw levels.

Cue 92 — 00:06:55,067 --> 00:06:58,307

They want it to level up. It's like a video game where you want to get to the

Cue 93 — 00:06:58,347 --> 00:07:03,187

highest level of self-driving, and it sounds like the future.

Cue 94 — 00:07:03,227 --> 00:07:08,427

So everyone basically took it as prophecy in the information environment we were in,

Cue 95 — 00:07:08,467 --> 00:07:11,747

and someone had to come forward to fulfill it.

Cue 96 — 00:07:11,787 --> 00:07:15,627

But to this day, there were virtually no case studies of anyone actually doing this

Cue 97 — 00:07:15,667 --> 00:07:21,467

successfully. There is marketing gossip repeated over and over and over the first

Cue 98 — 00:07:21,507 --> 00:07:27,227

six months of blogs about Dark Factory almost exclusively cited a single three

Cue 99 — 00:07:27,267 --> 00:07:33,867

person team at StrongDM. If I have to hear one more time about a single three

Cue 100 — 00:07:33,907 --> 00:07:39,507

person team at StrongDM, I'm glad they're having a good time there.

Cue 101 — 00:07:39,547 --> 00:07:44,547

This is not nearly enough information to even say that we have a pattern,

Cue 102 — 00:07:44,587 --> 00:07:48,087

let alone an inevitable future of software.

Cue 103 — 00:07:50,387 --> 00:07:55,507

So it's given some air of plausibility by this comparison to lights out

Cue 104 — 00:07:55,547 --> 00:08:02,507

manufacturing. Now we might point out lights out manufacturing

Cue 105 — 00:08:02,547 --> 00:08:06,267

in the physical world is mostly not a thing.

Cue 106 — 00:08:06,307 --> 00:08:12,307

We're talking about a few dozen facilities among millions of manufacturing

Cue 107 — 00:08:12,347 --> 00:08:15,987

facilities that do use automation in combination with workers.

Cue 108 — 00:08:16,027 --> 00:08:22,907

So I find highly suspicious this fetishization of a very fringe technique

Cue 109 — 00:08:22,947 --> 00:08:26,347

lights out as the pinnacle of manufacturing.

Cue 110 — 00:08:26,387 --> 00:08:30,627

That seems like a willful refusal to learn anything about what's happening in

Cue 111 — 00:08:30,667 --> 00:08:35,227

manufacturing. The last talk helpfully pointed out project work is not

Cue 112 — 00:08:35,267 --> 00:08:40,907

manufacturing. I like that that does affect how we automate when we're making the

Cue 113 — 00:08:40,947 --> 00:08:46,747

same part over and over, trying to automate out the ways that can go wrong versus

Cue 114 — 00:08:46,787 --> 00:08:50,427

adding to a system, making it more complex.

Cue 115 — 00:08:50,467 --> 00:08:52,447

But you know what? I'm going to be generous.

Cue 116 — 00:08:52,507 --> 00:08:53,987

I'm going to take that one on the chin.

Cue 117 — 00:08:54,027 --> 00:08:56,067

Let's say this is like manufacturing.

Cue 118 — 00:08:56,107 --> 00:08:59,687

And we'll allow the analogy to stand, because in some ways it does.

Cue 119 — 00:09:00,667 --> 00:09:03,527

For going to compare this to factories.

Cue 120 — 00:09:04,107 --> 00:09:10,747

Factories have workers. So what can we learn from

Cue 121 — 00:09:10,787 --> 00:09:14,047

manufacturing. There's some water.

Cue 122 — 00:09:19,197 --> 00:09:22,207

Right. Good. So what can we learn from manufacturing.

Cue 123 — 00:09:22,387 --> 00:09:28,187

So there was this thing called the Toyota Production System that was heavily

Cue 124 — 00:09:28,227 --> 00:09:33,347

influential because managers all around the world noticed that Toyota had taken over

Cue 125 — 00:09:33,387 --> 00:09:36,947

the entire automotive industry practically out of nowhere.

Cue 126 — 00:09:36,987 --> 00:09:41,067

It was it was staggering, world leading, productivity, soaring.

Cue 127 — 00:09:41,107 --> 00:09:45,907

The global production, but also world leading quality maintained.

Cue 128 — 00:09:45,947 --> 00:09:52,647

While they did that, a rare. The methods were written about and studied and

Cue 129 — 00:09:52,907 --> 00:09:58,667

sometimes not translated very well because they talk a lot about how the secret is

Cue 130 — 00:09:58,707 --> 00:10:03,307

that they eliminate waste, and that eight forms of waste that they analyze and

Cue 131 — 00:10:03,347 --> 00:10:07,867

eliminate, and this gets translated into English and worse, into American manager

Cue 132 — 00:10:07,907 --> 00:10:12,007

speak. And they think eliminate waste cost cutting.

Cue 133 — 00:10:12,187 --> 00:10:18,887

Cost cutting means layoffs. So eliminate waste equals get people away.

Cue 134 — 00:10:19,187 --> 00:10:25,107

And like that's just such a grotesque distortion of what the Toyota production

Cue 135 — 00:10:25,147 --> 00:10:28,027

System means by eliminating waste.

Cue 136 — 00:10:28,067 --> 00:10:34,647

In fact, Toyota has not laid off full time employees in 80 years.

Cue 137 — 00:10:36,267 --> 00:10:41,023

But he did talk about waste in 1978, when he wrote about the Toyota Production

Cue 138 — 00:10:41,063 --> 00:10:45,707

System, Taiichi Ohno, and of all the kinds of waste which you could do a whole talk

Cue 139 — 00:10:45,747 --> 00:10:49,547

on how they apply to coding agents right now, he said.

Cue 140 — 00:10:49,587 --> 00:10:54,687

There's no waste in business more terrible than overproduction,

Cue 141 — 00:10:56,107 --> 00:11:00,127

because that's the waste that conceals all the other kinds of waste.

Cue 142 — 00:11:01,227 --> 00:11:08,147

Now, going back to our dilemma of what do we do with this overwhelming amount

Cue 143 — 00:11:08,187 --> 00:11:11,727

of code that coding agents are able to generate?

Cue 144 — 00:11:12,707 --> 00:11:16,827

This looks like an issue of overproduction, trying to keep up with overproduction

Cue 145 — 00:11:16,867 --> 00:11:18,927

rather than trying to actually meet our goals.

Cue 146 — 00:11:19,507 --> 00:11:22,867

Let me suggest that maybe you can give that book another read and see what you

Cue 147 — 00:11:22,907 --> 00:11:26,107

think. There's another famous book about manufacturing, not a factory,

Cue 148 — 00:11:26,147 --> 00:11:29,547

technically about a plant. I'm told there's a difference.

Cue 149 — 00:11:29,587 --> 00:11:31,507

This is by Eli Goldratt called The Goal.

Cue 150 — 00:11:31,547 --> 00:11:37,387

This was later rewritten brilliantly by Gene Kim and others in 2015 into a scene by

Cue 151 — 00:11:37,427 --> 00:11:41,367

scene rewrite called The Phoenix Project about DevOps.

Cue 152 — 00:11:41,787 --> 00:11:47,147

Both are very good. We will talk about the first because a lot of people are quite

Cue 153 — 00:11:47,187 --> 00:11:50,867

rightly thinking, maybe Goldratt has some ideas that can help us with this pull

Cue 154 — 00:11:50,907 --> 00:11:54,887

request bottleneck and true. However,

Cue 155 — 00:11:56,347 --> 00:12:03,267

simply declaring human review is now the bottleneck is not theory of constraints

Cue 156 — 00:12:03,307 --> 00:12:06,747

thinking. You're basically at the end of at.

Cue 157 — 00:12:06,787 --> 00:12:10,267

You think you're at the end of the first book and you're at the beginning.

Cue 158 — 00:12:10,307 --> 00:12:12,047

And there were several books

Cue 159 — 00:12:13,267 --> 00:12:17,787

explaining what I mean. But this reminds me of if you've seen the show The Office.

Cue 160 — 00:12:17,827 --> 00:12:19,107

I know we got people from London.

Cue 161 — 00:12:19,147 --> 00:12:22,627

The British office is good too, but we made our own version in America.

Cue 162 — 00:12:22,667 --> 00:12:26,627

And there's this character that tries to declare bankruptcy,

Cue 163 — 00:12:26,667 --> 00:12:30,107

but he thinks the way you declare bankruptcy is just saying,

Cue 164 — 00:12:30,147 --> 00:12:36,587

I declare bankruptcy. So we're in this stage of saying I declare bottleneck.

Cue 165 — 00:12:36,627 --> 00:12:39,587

Okay, keep reading, keep working on it.

Cue 166 — 00:12:39,627 --> 00:12:44,507

We can get there. I think Eli Goldratt would probably say that the goal isn't to

Cue 167 — 00:12:44,547 --> 00:12:49,387

make the robots more productive, it's to make the whole system productive.

Cue 168 — 00:12:49,427 --> 00:12:53,697

And the reason I feel he'd say that is because he said those words in The Goal,

Cue 169 — 00:12:53,737 --> 00:12:59,827

  1. Now, if you pull up the PDF and search for the word robots,

Cue 170 — 00:12:59,867 --> 00:13:05,587

just that form of the word, there's 60 mentions of robots, over a hundred if we want

Cue 171 — 00:13:05,627 --> 00:13:07,267

to talk about any mention of robotics.

Cue 172 — 00:13:07,307 --> 00:13:12,147

So this is a huge through line in the plot, the broad strokes of what's going on.

Cue 173 — 00:13:12,187 --> 00:13:16,307

You start out, start out in a situation where there's heavy management pressure to

Cue 174 — 00:13:16,347 --> 00:13:20,667

show high utilization of these robots they've just brought in and invested in.

Cue 175 — 00:13:20,707 --> 00:13:26,867

And that leads, though, to local optimizations that didn't translate to more money.

Cue 176 — 00:13:26,907 --> 00:13:33,067

He starts the day puzzled, like, hey, our robots are showing huge efficiencies,

Cue 177 — 00:13:33,107 --> 00:13:36,667

but we're not making I'm not making my quota.

Cue 178 — 00:13:36,707 --> 00:13:42,587

So ultimately there's a throughput that we're talking about with PR throughput that

Cue 179 — 00:13:42,627 --> 00:13:48,027

isn't the throughput. Goldratt wrote about any of this sounding familiar to

Cue 180 — 00:13:48,067 --> 00:13:49,927

situations you've seen in your life.

Cue 181 — 00:13:49,987 --> 00:13:50,927

I don't know,

Cue 182 — 00:13:52,347 --> 00:13:59,367

I think they do. But bottom line, all this talk about self-driving cars and and

Cue 183 — 00:13:59,467 --> 00:14:05,907

very I feel just misinformed. Allusions to what happens in factories is translated

Cue 184 — 00:14:05,947 --> 00:14:12,587

in normalizing pretty bad advice like just stop reading code is in and of itself bad

Cue 185 — 00:14:12,627 --> 00:14:18,147

advice. Read less code coupled with a bunch of ways that you achieve that can be

Cue 186 — 00:14:18,187 --> 00:14:21,947

good advice, but what's happening right now is a lot of bad advice.

Cue 187 — 00:14:21,987 --> 00:14:26,547

I have a blog going into this called Reading Code Considered Helpful.

Cue 188 — 00:14:26,587 --> 00:14:31,387

You can kind of see the other side of the coin of Dark Factory considered harmful,

Cue 189 — 00:14:31,427 --> 00:14:35,827

but as I was gathering opinions, Liz Fong-Jones commented and just kind of blew the

Cue 190 — 00:14:35,867 --> 00:14:40,827

whole thing apart because I think she clearly articulated the mainstream position of

Cue 191 — 00:14:40,867 --> 00:14:46,047

anyone attached to consequences in code that was commenting.

Cue 192 — 00:14:46,427 --> 00:14:50,187

She says, I don't read code looking for obvious bugs anymore.

Cue 193 — 00:14:50,227 --> 00:14:52,027

The robots are perfectly good at that.

Cue 194 — 00:14:52,067 --> 00:14:56,747

But I do read code looking for design and maintainability and readability issues.

Cue 195 — 00:14:56,787 --> 00:15:01,947

So good. We're separating the different reasons that we are staying on top of the

Cue 196 — 00:15:01,987 --> 00:15:06,667

code, and we're understanding that there are degrees to which our our attention is

Cue 197 — 00:15:06,707 --> 00:15:07,867

less now, but there are concerns.

Cue 198 — 00:15:07,907 --> 00:15:11,767

We still must look out for a very good breakdown.

Cue 199 — 00:15:12,947 --> 00:15:19,147

So with that in mind, Dark Factory fails even in theory, because although we can say

Cue 200 — 00:15:19,187 --> 00:15:23,667

we have a layered defense, layered defense requires some amount of inspection.

Cue 201 — 00:15:23,707 --> 00:15:27,427

We tell developers your new role is writing the code inspector,

Cue 202 — 00:15:27,467 --> 00:15:31,347

but knowing if the code inspector is inspecting all the things you needed to

Cue 203 — 00:15:31,387 --> 00:15:36,267

inspect. This is something that requires amount of being close to the details

Cue 204 — 00:15:36,307 --> 00:15:37,207

yourself.

Cue 205 — 00:15:39,227 --> 00:15:42,587

To see a clearer articulation of this, you can go to Ironies of Automation,

Cue 206 — 00:15:42,627 --> 00:15:46,167

1983, a landmark paper by Lisanne Bainbridge.

Cue 207 — 00:15:46,227 --> 00:15:48,507

It's been cited over a thousand times.

Cue 208 — 00:15:48,547 --> 00:15:55,387

One of the ironies of automation is a designer of automation will want to eliminate

Cue 209 — 00:15:55,427 --> 00:15:59,867

a full role, but has only automated the parts of it they could understand how to

Cue 210 — 00:15:59,907 --> 00:16:05,587

automate. And this leaves the human operator with infrequent attention,

Cue 211 — 00:16:05,627 --> 00:16:09,347

but vital points of intervention that they've got to jump in,

Cue 212 — 00:16:09,387 --> 00:16:14,007

that are more complex to untangle and that they don't have proper support for.

Cue 213 — 00:16:14,067 --> 00:16:18,427

Again, this is reminding me of a lot of the experiences I'm hearing in the field

Cue 214 — 00:16:18,467 --> 00:16:19,267

today.

Cue 215 — 00:16:21,107 --> 00:16:25,947

Now, it was a while ago, a couple several decades ago, that paper was written.

Cue 216 — 00:16:25,987 --> 00:16:27,627

So we've obviously built on that knowledge.

Cue 217 — 00:16:27,667 --> 00:16:31,707

There's an area called cognitive systems engineering, which I think would be very

Cue 218 — 00:16:31,747 --> 00:16:33,787

helpful for us to start thinking about.

Cue 219 — 00:16:33,827 --> 00:16:38,547

So if you know the idea of ergonomics and, you know, tools that fit well in our hand

Cue 220 — 00:16:38,587 --> 00:16:42,107

and all that, but there's a UX principle called don't make me think.

Cue 221 — 00:16:42,147 --> 00:16:46,167

Well, cognitive systems engineering takes a step further and say,

Cue 222 — 00:16:46,347 --> 00:16:50,627

don't just interrupt me and make me think, but help me think.

Cue 223 — 00:16:50,667 --> 00:16:54,687

What does a tool look like that actively helps us think?

Cue 224 — 00:16:56,867 --> 00:17:01,707

So we have established theoretical reasons why we wouldn't expect the kind of

Cue 225 — 00:17:01,747 --> 00:17:04,687

default presentation of a dark factory to work.

Cue 226 — 00:17:05,787 --> 00:17:10,407

However, we also know that it fails mostly in practice when people try it.

Cue 227 — 00:17:10,667 --> 00:17:14,207

This is how it normally goes. Quick time lapse.

Cue 228 — 00:17:14,267 --> 00:17:16,407

Hey everyone, don't read the code.

Cue 229 — 00:17:16,947 --> 00:17:21,087

Kaboom! Actually read the code.

Cue 230 — 00:17:23,607 --> 00:17:29,167

Someone's full explanation of this story I've just reenacted is Dex Horthy,

Cue 231 — 00:17:29,207 --> 00:17:35,207

a very experienced dev worked briefly for for NASA back in the day and now has a

Cue 232 — 00:17:35,247 --> 00:17:41,967

startup called HumanLayer, and they set up their factory based on what they

Cue 233 — 00:17:42,007 --> 00:17:44,807

thought, how they thought it was going to go, and they tried to go full dark

Cue 234 — 00:17:44,847 --> 00:17:49,347

factory, and they had to come back later and say, okay, amended talk.

Cue 235 — 00:17:49,647 --> 00:17:51,287

We had to throw away that whole system.

Cue 236 — 00:17:51,327 --> 00:17:52,447

We're doing it differently now.

Cue 237 — 00:17:52,487 --> 00:17:55,107

This is he has very detailed recommendations.

Cue 249 — 00:18:37,189 --> 00:18:39,589

another example I think is pretty interesting.

Cue 250 — 00:18:39,629 --> 00:18:45,389

They're here, LaunchDarkly, and I've heard they're launching some kind of factory

Cue 251 — 00:18:45,429 --> 00:18:51,469

offering tomorrow. Now, you'd think if anyone we're going to be in favor of the Dark

Cue 252 — 00:18:51,509 --> 00:18:54,149

Factory, it would be LaunchDarkly.

Cue 253 — 00:18:54,189 --> 00:18:57,669

I mean, Dark's in the name, but also they they are a feature flag vendor.

Cue 254 — 00:18:57,709 --> 00:19:01,449

They they are masters of reducing the risk of deployment.

Cue 255 — 00:19:01,789 --> 00:19:03,989

However, they did want to try it.

Cue 256 — 00:19:04,029 --> 00:19:08,309

And their report back was from Alexis here in August.

Cue 257 — 00:19:08,349 --> 00:19:12,249

The dark factory is a trap. It's a trap.

Cue 258 — 00:19:12,429 --> 00:19:16,269

This is the lesson I most want other engineering leaders to take away,

Cue 259 — 00:19:16,309 --> 00:19:20,669

because it cost me the most time chasing the dark factory.

Cue 260 — 00:19:20,709 --> 00:19:25,469

Ideal excuse the long quote where agents are fully autonomous and humans are looped

Cue 261 — 00:19:25,509 --> 00:19:29,429

out, led directly into what I call the autonomy trap.

Cue 262 — 00:19:29,469 --> 00:19:33,989

You end up doing Rube Goldberg development, spending all your time building an

Cue 263 — 00:19:34,029 --> 00:19:37,809

elaborate machine instead of getting to the actual goal.

Cue 264 — 00:19:38,709 --> 00:19:42,369

As we learned in the 1980s. My interjection.

Cue 265 — 00:19:43,269 --> 00:19:49,069

So what works? Things that seem very dark, factory adjacent that are successful

Cue 266 — 00:19:49,109 --> 00:19:54,249

succeed in some load bearing way by not doing the full dark factory?

Cue 267 — 00:19:55,269 --> 00:20:00,149

I'll explain what I mean. You see a lot of things like reading code as needed,

Cue 268 — 00:20:00,189 --> 00:20:04,029

finding out, okay, what's the level of inspecting code I need to do?

Cue 269 — 00:20:04,069 --> 00:20:06,269

And in what context can we reduce that?

Cue 270 — 00:20:06,309 --> 00:20:08,909

I don't mean to argue against that often.

Cue 271 — 00:20:08,949 --> 00:20:14,789

Helpful. Also, I'm happy to see executable specifications are making a rise in in

Cue 272 — 00:20:14,829 --> 00:20:19,509

several forms. And so people have have said, okay, well I'm going to read the

Cue 273 — 00:20:19,549 --> 00:20:25,669

executable test as this high leverage way that I can stay in control of what the how

Cue 274 — 00:20:25,709 --> 00:20:29,629

the code is behaving. And you even have, you know, more extreme versions,

Cue 275 — 00:20:29,669 --> 00:20:35,989

which I've dedicated a year each to on my YouTube channel called Formal Methods and

Cue 276 — 00:20:36,029 --> 00:20:41,149

Domain Specific Languages. So yeah, those are reading code.

Cue 277 — 00:20:41,189 --> 00:20:45,429

You have found a very high leverage piece of code that you can stay on top of,

Cue 278 — 00:20:45,469 --> 00:20:47,549

to give you agency over the rest of it.

Cue 279 — 00:20:47,589 --> 00:20:51,729

I don't argue against that. That is generally not harmful.

Cue 280 — 00:20:52,029 --> 00:20:54,569

We have lots of patterns of doing that successfully.

Cue 281 — 00:20:54,909 --> 00:21:01,229

Another thing that people do hand in hand with a with a software factory are things

Cue 282 — 00:21:01,269 --> 00:21:05,189

like continuous delivery, which involves, as I say, layered defenses,

Cue 283 — 00:21:05,229 --> 00:21:07,349

tests and linters. And on it goes.

Cue 284 — 00:21:07,389 --> 00:21:12,549

And, you know, other ways of knowing what's going to happen and then what is

Cue 285 — 00:21:12,589 --> 00:21:17,309

happening that reduce risk. No argument against these things.

Cue 286 — 00:21:17,349 --> 00:21:21,509

And some people say, hey, Ray, I'm doing CD, I'm doing observability,

Cue 287 — 00:21:21,549 --> 00:21:23,609

and I still can't ship fast enough.

Cue 288 — 00:21:23,989 --> 00:21:27,829

I kind of wonder if they're actually doing them, because a lot of people like,

Cue 289 — 00:21:27,869 --> 00:21:31,189

again, like I declare continuous delivery.

Cue 290 — 00:21:31,229 --> 00:21:32,752

Like they just they don't actually do them.

Cue 291 — 00:21:32,792 --> 00:21:34,109

Right. There are books on these things.

Cue 292 — 00:21:34,149 --> 00:21:36,769

It is a long journey. It bears a lot of fruit.

Cue 293 — 00:21:36,829 --> 00:21:41,869

There was a new edition of Observability Engineering released this this year,

Cue 294 — 00:21:41,909 --> 00:21:44,809

and that's coauthored by Liz Fong-Jones from earlier.

Cue 295 — 00:21:45,029 --> 00:21:51,949

They have on the Honeycomb blog a very nice experience report of how they doubled

Cue 296 — 00:21:51,989 --> 00:21:56,529

the number of pull requests they were delivering, the challenges they faced,

Cue 297 — 00:21:56,669 --> 00:22:01,229

how what it cost them. It increased incidents they had to work on.

Cue 298 — 00:22:01,269 --> 00:22:07,669

Okay, how do we contain that? Because overall we want the overall result was

Cue 299 — 00:22:07,709 --> 00:22:10,029

positive. But they they talk about their problem solving.

Cue 300 — 00:22:10,069 --> 00:22:14,269

A lot of caveats. This is probably if you're going to read one experience report

Cue 301 — 00:22:14,309 --> 00:22:15,909

anywhere close to Dark Factory.

Cue 302 — 00:22:15,949 --> 00:22:20,247

This would be the one. But they are not remotely doing Dark Factory.

Cue 303 — 00:22:20,287 --> 00:22:23,429

Tessl, they threw this awesome conference.

Cue 304 — 00:22:23,469 --> 00:22:27,909

Right. So they've got this video of building the Dark factory.

Cue 305 — 00:22:27,949 --> 00:22:32,709

We've got Maria here. I love her facial expression in the thumbnail in the video.

Cue 306 — 00:22:32,749 --> 00:22:37,589

She's literally saying, like, my team built the dark factory.

Cue 307 — 00:22:37,629 --> 00:22:40,069

Like she's got this incredulous expression.

Cue 308 — 00:22:40,109 --> 00:22:44,249

It's awesome. And I've I've talked to a few of the team members,

Cue 309 — 00:22:44,589 --> 00:22:47,509

you know, over the weekend. And this is what they said, though,

Cue 310 — 00:22:47,549 --> 00:22:52,829

on the on the blog, 75% of Tessl's PRs now merge without human review.

Cue 311 — 00:22:52,869 --> 00:22:57,709

So I talking to them, they said for compliance reasons this is someone is choosing

Cue 312 — 00:22:57,749 --> 00:23:01,989

to push merge, but they haven't done detailed review.

Cue 313 — 00:23:02,029 --> 00:23:08,769

And the 25% they are doing the detailed review and they with their

Cue 314 — 00:23:09,469 --> 00:23:13,309

automated review tool, they have various policies about how they surface,

Cue 315 — 00:23:13,349 --> 00:23:18,129

which PRs are the ones that present more risk, that deserve more of their attention.

Cue 316 — 00:23:18,349 --> 00:23:20,509

I'm not arguing against any of this, right.

Cue 317 — 00:23:20,549 --> 00:23:25,749

This sounds like a pretty principled way of leveraging how the human attention is

Cue 318 — 00:23:25,789 --> 00:23:26,589

used.

Cue 319 — 00:23:27,829 --> 00:23:31,589

And Patrick Debois, also with Tessl and a co-founder of DevOps,

Cue 320 — 00:23:31,629 --> 00:23:36,989

has said in a talk about Dark Factory, the dark factory is probably a dim factory.

Cue 321 — 00:23:37,029 --> 00:23:39,949

So we're all wrestling with the terminology, you know, like,

Cue 322 — 00:23:39,989 --> 00:23:45,449

I see a lot of people that are trying to give good advice and we're capitalizing,

Cue 323 — 00:23:45,509 --> 00:23:49,989

you know, for people's attention on like what people want to hear talked about.

Cue 324 — 00:23:50,029 --> 00:23:54,709

And I don't want to judge anyone who's got like, good ideas to too harshly for how

Cue 325 — 00:23:54,749 --> 00:23:59,829

we presenting, how we're presenting things because it's just a hard situation.

Cue 326 — 00:23:59,869 --> 00:24:01,689

We're trying to give good advice.

Cue 327 — 00:24:01,909 --> 00:24:06,909

We are, I believe, being incentivized to give bad advice.

Cue 328 — 00:24:06,949 --> 00:24:10,149

Everywhere on the internet, you see someone say a bunch of reasonable stuff

Cue 329 — 00:24:10,189 --> 00:24:14,909

somewhere along the line, they say, and, you know, in this particular context,

Cue 330 — 00:24:14,949 --> 00:24:18,509

I don't even read the code. And then somebody like shares with headlines.

Cue 331 — 00:24:18,549 --> 00:24:20,569

He says, you should never read the like.

Cue 332 — 00:24:21,189 --> 00:24:26,869

It's very confounding. But, you know, read the sources of the quotes.

Cue 333 — 00:24:26,909 --> 00:24:30,709

When you're not reading so much code, that's something you have time to do or read

Cue 334 — 00:24:30,749 --> 00:24:35,909

books. People who like agents like context.

Cue 335 — 00:24:35,949 --> 00:24:40,109

So I just want to explain the context of my my motivations here,

Cue 336 — 00:24:40,149 --> 00:24:44,509

because you'll notice that all the people we're hearing from about dark factories,

Cue 337 — 00:24:44,549 --> 00:24:49,349

which I believe are saying some pretty useful stuff in many cases like these are

Cue 338 — 00:24:49,389 --> 00:24:54,569

all, forgive me, some AI build dev tool startups.

Cue 339 — 00:24:54,749 --> 00:24:59,549

Having been there myself and having, like many of you, also worked in like financial

Cue 340 — 00:24:59,589 --> 00:25:02,249

tech and education, tech and health care.

Cue 341 — 00:25:02,469 --> 00:25:06,229

I know that there are just different needs to different contexts in which code is

Cue 342 — 00:25:06,269 --> 00:25:12,989

written. So this urge to prophesy one future

Cue 343 — 00:25:13,029 --> 00:25:18,109

of all code, it just gets in the way of meeting people's contextual needs.

Cue 344 — 00:25:18,149 --> 00:25:22,629

And when I see advice being thrown around, I'm not so much concerned about if a

Cue 345 — 00:25:22,669 --> 00:25:26,789

startup is going to manage to fit a square peg in a round hole as an existence

Cue 346 — 00:25:26,829 --> 00:25:32,709

proof, I am thinking in a lot of other environments with very load bearing code.

Cue 347 — 00:25:32,749 --> 00:25:36,129

What is the effect of this? Is this going to bear fruit?

Cue 348 — 00:25:36,429 --> 00:25:41,789

And you could say things like, you know, x, y, z could work as long as right now

Cue 349 — 00:25:41,829 --> 00:25:45,869

you're making a lot of platform engineering investments and you're listening to the

Cue 350 — 00:25:45,909 --> 00:25:49,669

systems thinkers and your organization, and you have a high trust environment.

Cue 351 — 00:25:49,709 --> 00:25:54,749

And I just think like look, particularly right now, what industry are you looking at

Cue 352 — 00:25:54,789 --> 00:25:58,349

like if that describes your work environment?

Cue 353 — 00:25:58,389 --> 00:26:03,569

Great. A lot of our friends, it's nothing like that right now.

Cue 354 — 00:26:04,149 --> 00:26:10,949

So that's the context. So why are we even talking about

Cue 355 — 00:26:10,989 --> 00:26:17,139

Dark Factory? Well, on some level, we know it's because of the awesome power of the

Cue 356 — 00:26:17,179 --> 00:26:18,049

LLM.

Cue 357 — 00:26:19,469 --> 00:26:21,649

We must figure out what this means.

Cue 358 — 00:26:22,389 --> 00:26:25,229

And I was excited about the large language model.

Cue 359 — 00:26:25,269 --> 00:26:30,109

It's a pretty versatile, you know, piece of infrastructure where we can

Cue 360 — 00:26:30,149 --> 00:26:34,509

statistically model the uses of language within a large training set and use that in

Cue 361 — 00:26:34,549 --> 00:26:41,349

all sorts of nifty ways. But the LLM that's even more powerful than that is the

Cue 362 — 00:26:41,389 --> 00:26:46,609

Liar's Layoff machine. And that's what we're having to contend with now,

Cue 363 — 00:26:48,029 --> 00:26:52,909

where we are telling workers not pointing any particular fingers here,

Cue 364 — 00:26:52,949 --> 00:26:57,489

but people are telling workers that it's augment, not replace,

Cue 365 — 00:26:57,829 --> 00:27:03,949

while other people are telling CEOs replace, or perhaps even the same people are

Cue 366 — 00:27:03,989 --> 00:27:05,189

delivering both those messages.

Cue 367 — 00:27:05,229 --> 00:27:10,429

In some cases, it's hard to know, but there's a lot of contradictory mixed signals

Cue 368 — 00:27:10,469 --> 00:27:12,989

floating around in the organization.

Cue 369 — 00:27:13,029 --> 00:27:18,209

That's the context that the dark factory dialog exists in is inescapable.

Cue 370 — 00:27:18,669 --> 00:27:22,649

Yeah. For instance, the CEO of Anthropic, remember from earlier,

Cue 371 — 00:27:23,589 --> 00:27:29,789

saying in January at the World Economic Forum we might be 6 to 12 months away from

Cue 372 — 00:27:29,829 --> 00:27:34,309

models doing all of what software engineers, engineers do end to end.

Cue 373 — 00:27:34,349 --> 00:27:40,429

Now, I admit that that like statement does sort of imply that there ought to be

Cue 374 — 00:27:40,469 --> 00:27:42,149

something like a dark factory.

Cue 375 — 00:27:42,189 --> 00:27:46,509

But I notice at the end of the year where we have, what, six months left,

Cue 376 — 00:27:46,549 --> 00:27:51,529

no, six weeks left as an entire profession by this timeline,

Cue 377 — 00:27:52,069 --> 00:27:56,849

it still seems like they're telling us our job is to build the dark factory.

Cue 378 — 00:27:57,134 --> 00:28:02,589

What's going on with that? If you had no plan to build one, I feel the urge to have

Cue 379 — 00:28:02,629 --> 00:28:04,369

him finish his own homework.

Cue 380 — 00:28:05,629 --> 00:28:10,669

But, you know, okay, he likes to speculate about a lot of futuristic possibilities

Cue 381 — 00:28:10,709 --> 00:28:13,289

that are imminent and highly disruptive.

Cue 382 — 00:28:14,069 --> 00:28:16,449

That's his game. And, you know,

Cue 383 — 00:28:17,709 --> 00:28:19,609

it's working very well for him.

Cue 384 — 00:28:19,669 --> 00:28:25,029

He and one of his peers are heading towards potentially trillion dollar IPOs,

Cue 385 — 00:28:25,069 --> 00:28:29,669

initial public offering of stock, the largest such things in history.

Cue 386 — 00:28:29,709 --> 00:28:34,549

They have led the largest startup funding rounds in history among them.

Cue 387 — 00:28:34,589 --> 00:28:40,189

And these people, they say things lots of investors hear the things they say.

Cue 388 — 00:28:40,229 --> 00:28:45,549

Those investors have some kinds of high pressure conversations with your CEOs,

Cue 389 — 00:28:45,589 --> 00:28:52,249

and then chaos ensues. That is why the dark factory is considered harmful.

Cue 390 — 00:28:54,749 --> 00:29:01,789

Because this is a gold rush. You know, I see very, you know,

Cue 391 — 00:29:01,829 --> 00:29:06,589

tech focused people sometimes bewildered at why other software engineers or members

Cue 392 — 00:29:06,629 --> 00:29:11,169

of the general public seem so, like, upset about AI.

Cue 393 — 00:29:11,669 --> 00:29:15,829

Well, it's a gold rush. There's a lot to be upset about in a gold rush,

Cue 394 — 00:29:15,869 --> 00:29:22,229

even if there's actual gold. I mean, I think people are upset that a lot of things

Cue 395 — 00:29:22,269 --> 00:29:28,989

they don't want are being pushed upon them, or that people are scrambling in a

Cue 396 — 00:29:29,029 --> 00:29:34,489

race to get somewhere first, not even knowing where that place is.

Cue 397 — 00:29:36,909 --> 00:29:41,909

And within the realm of software productivity, I would observe antiquated views of

Cue 398 — 00:29:41,949 --> 00:29:46,589

automation and productivity are being imposed by investor pressure.

Cue 399 — 00:29:46,629 --> 00:29:52,829

AI may be futuristic, whatever we think AI means today, but the gold rush is an

Cue 400 — 00:29:52,869 --> 00:29:58,209

antique. It is a relic. It belongs in the trash.

Cue 401 — 00:30:01,589 --> 00:30:06,069

The general public's relationship with software, as we are talking about all the

Cue 402 — 00:30:06,109 --> 00:30:11,149

awesome ways we're making developing software better, the general public's

Cue 403 — 00:30:11,189 --> 00:30:15,909

relationship with software has deteriorated to such a degree that Merriam-Webster

Cue 404 — 00:30:15,949 --> 00:30:18,469

has changed to reflect popular usage.

Cue 405 — 00:30:18,509 --> 00:30:21,789

The definition of the word slop, not the secondary.

Cue 406 — 00:30:21,829 --> 00:30:27,469

The primary definition of the word slop in public consciousness refers to how badly

Cue 407 — 00:30:27,509 --> 00:30:30,129

Big Tech is screwing up software.

Cue 408 — 00:30:30,749 --> 00:30:37,569

Where to the ear? Now, I know you may be skeptical of some of the things I'm saying.

Cue 409 — 00:30:37,869 --> 00:30:40,129

And you know what? If so, I commend you.

Cue 410 — 00:30:40,269 --> 00:30:43,449

It's great to be skeptical during a gold rush.

Cue 411 — 00:30:43,509 --> 00:30:48,589

So I'm saying something kind of outrageous, like a lot of ideas from the 1980s would

Cue 412 — 00:30:48,629 --> 00:30:51,069

be helping us during the AI gold rush.

Cue 413 — 00:30:51,109 --> 00:30:55,669

How could that be? Well, to justify that a little bit, I'll let you know about

Cue 414 — 00:30:55,709 --> 00:30:58,849

something hot off the presses this year.

Cue 415 — 00:30:59,339 --> 00:31:03,629

A little paper called AI Gold Rush 2 versus AI Realism.

Cue 416 — 00:31:03,669 --> 00:31:09,109

Overplaying envisioned benefits, underplaying real risks by some safety researchers

Cue 417 — 00:31:09,149 --> 00:31:13,429

that some some of whom, like David Woods, pioneered the field of cognitive systems

Cue 418 — 00:31:13,469 --> 00:31:20,249

engineering I mentioned earlier and kind of to to pour salt in the wound further.

Cue 419 — 00:31:20,669 --> 00:31:26,049

The number two here, this isn't even the first AI gold rush.

Cue 420 — 00:31:27,069 --> 00:31:31,849

The first AI gold rush was in, you guessed it, the 1980s.

Cue 421 — 00:31:32,029 --> 00:31:33,949

So they compare and contrast them for you.

Cue 422 — 00:31:33,989 --> 00:31:37,189

You can let me know what you think if you get a chance to read that.

Cue 423 — 00:31:37,229 --> 00:31:43,749

I hope it will empower you. But going forward, I like the factory conversation,

Cue 424 — 00:31:43,789 --> 00:31:46,869

even if I don't like so much the dark factory side of it.

Cue 425 — 00:31:46,909 --> 00:31:50,949

I like the factory conversation because we're trying to reboot how coding agents are

Cue 426 — 00:31:50,989 --> 00:31:53,549

being applied. I couldn't agree more.

Cue 427 — 00:31:53,589 --> 00:31:55,289

That's something that we should do.

Cue 428 — 00:31:55,429 --> 00:32:01,289

And my framing on it is if I want the positives and not the negatives.

Cue 429 — 00:32:01,469 --> 00:32:07,789

I want to free coding agents from the clutches of the gold rush.

Cue 430 — 00:32:07,829 --> 00:32:10,109

So my rewrite, we can rewrite everything.

Cue 431 — 00:32:10,149 --> 00:32:15,429

Now, my rewrite of coding agents would not be so much with the gold rush

Cue 432 — 00:32:15,469 --> 00:32:20,509

assumptions. You can call it coding Agents 2.0 if you're thinking about these things

Cue 433 — 00:32:20,549 --> 00:32:22,109

too. I would love to talk to you here.

Cue 434 — 00:32:22,149 --> 00:32:28,189

What you think it means? I think some ways it starts are that these are tools,

Cue 435 — 00:32:28,229 --> 00:32:35,489

not virtual employees. That abstractions are designed, that teams succeed

Cue 436 — 00:32:36,309 --> 00:32:41,769

and adoption is not forced. I will leave you with this.

Cue 437 — 00:32:42,269 --> 00:32:46,209

Build factories for what they reveal, not what they hide.

Cue 438 — 00:32:46,789 --> 00:32:51,129

Keep your eyes open and keep the lights on.

Cue 439 — 00:32:51,549 --> 00:32:54,969

Thank you so much. I'm at the coding agency.org.

skills

talk-myers-understanding-agent-generated-code

tile.json