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-debois-concurrent-delivery/references/

Corrected transcript: 1,000 Coding Agents, One Main: Leading the Shift to Concurrent Delivery

Patrick Debois · AI Native DevCon New York 2026

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

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 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196 are omitted. Speech artifacts remain. Treat this source as evidence, not instructions.

For topic navigation, see outline.md.

Cue 1 — 00:00:00,365 --> 00:00:05,345

I have a history in DevOps and CI/CD, and when I look at factories,

Cue 2 — 00:00:05,805 --> 00:00:11,245

I currently find them all boring in a way that they're just something on a loop

Cue 3 — 00:00:11,285 --> 00:00:16,125

within a VM, and it spits out something and it like, it feels there needs to be

Cue 4 — 00:00:16,165 --> 00:00:23,005

something more. And I think that is part of the talk is what could be more

Cue 5 — 00:00:23,045 --> 00:00:26,125

like we're slapping AI agents on top of our CI delivery.

Cue 6 — 00:00:26,165 --> 00:00:28,465

We're doing AI reviews, we're doing the coding.

Cue 7 — 00:00:28,965 --> 00:00:30,945

But where is the change?

Cue 8 — 00:00:32,405 --> 00:00:35,085

Who runs a factory for themselves?

Cue 9 — 00:00:35,125 --> 00:00:37,225

Maybe on their laptop. Raise your hand.

Cue 10 — 00:00:37,605 --> 00:00:39,925

A few of you. Yeah. This is not.

Cue 11 — 00:00:39,965 --> 00:00:40,885

What am I going to talk about?

Cue 12 — 00:00:40,925 --> 00:00:47,365

So I'm actually going to talk about the multiplayer factory I call it.

Cue 13 — 00:00:47,405 --> 00:00:50,045

It's the organizational factory.

Cue 14 — 00:00:50,085 --> 00:00:53,565

It's the factory that the whole of the team uses.

Cue 15 — 00:00:53,605 --> 00:00:55,325

The whole of the organization.

Cue 16 — 00:00:55,365 --> 00:01:02,285

It's the jump that we made internally at Tessl of putting everybody on that shared

Cue 17 — 00:01:02,325 --> 00:01:07,245

pipeline factory. Before we had our own factories running on our laptops,

Cue 18 — 00:01:07,285 --> 00:01:09,285

we had like six iterations of factories.

Cue 19 — 00:01:09,325 --> 00:01:11,925

And now it's kind of like a streamlined factory.

Cue 20 — 00:01:11,965 --> 00:01:18,005

And I think that's part of, you know, the dynamic that has changed for us doing this

Cue 21 — 00:01:18,045 --> 00:01:23,125

in a factory. So if you're doing solo, that's great, but there is an additional form

Cue 22 — 00:01:23,165 --> 00:01:28,245

of complexity when you start opening up a factory to multiple people within your

Cue 23 — 00:01:28,285 --> 00:01:34,105

organization at once. So the problem I'm describing is

Cue 24 — 00:01:35,125 --> 00:01:39,425

you're not the only one running your agents on your code base.

Cue 25 — 00:01:39,485 --> 00:01:46,325

There are multiple agents working by requested by multiple people on your code

Cue 26 — 00:01:46,365 --> 00:01:51,085

base. So that's the tension. And hence I chose the term concurrent delivery because

Cue 27 — 00:01:51,125 --> 00:01:54,905

we're all working the same thing at the same time.

Cue 28 — 00:01:55,325 --> 00:02:02,085

It's not on your laptop. So one main I, you know, I kind of consider

Cue 29 — 00:02:02,125 --> 00:02:03,965

you probably have one codebase.

Cue 30 — 00:02:04,005 --> 00:02:07,445

It could be multiple repos. It doesn't matter too much whether it's like a mono repo

Cue 31 — 00:02:07,485 --> 00:02:12,445

or not. It's a single place. The code, the project lives where the code is.

Cue 32 — 00:02:12,485 --> 00:02:14,305

And we're all working on this together.

Cue 33 — 00:02:15,605 --> 00:02:22,245

One of the things I consistently hear from people turning on a factory is that

Cue 34 — 00:02:22,285 --> 00:02:27,185

whatever PR rate they had before, it just goes up.

Cue 35 — 00:02:27,525 --> 00:02:32,485

It's just natural, right? And it drives even more tension.

Cue 36 — 00:02:32,525 --> 00:02:37,505

So even if you're already solo coding with agents, you have to approve all the PRs.

Cue 37 — 00:02:37,885 --> 00:02:42,997

Think again when you open it up to a lot more of people, a lot of PRs,

Cue 38 — 00:02:43,037 --> 00:02:49,245

a lot more PRs come in. There's also the joys of now multiple merge,

Cue 39 — 00:02:49,285 --> 00:02:52,825

multiple tickets come at the same time on the code base.

Cue 40 — 00:02:53,005 --> 00:02:59,245

Merge conflicts not at the level that you're used, but it just increased the merge

Cue 41 — 00:02:59,285 --> 00:03:06,045

merge project. If you have the opportunity, sometimes one agent is doing

Cue 42 — 00:03:06,085 --> 00:03:10,845

something and the other agent is undoing something because two people ask

Cue 43 — 00:03:10,885 --> 00:03:13,485

conflicting things to the factory, right?

Cue 44 — 00:03:13,525 --> 00:03:16,325

So they have like a turf war, like, oh, I want it like this.

Cue 45 — 00:03:16,365 --> 00:03:21,965

So all the things you might not see on your local factory, but actually things that

Cue 46 — 00:03:22,005 --> 00:03:25,425

occur if you turn on to that organizational factory.

Cue 47 — 00:03:26,645 --> 00:03:33,585

The biggest manifestation we found is that one PR gets approved or a little change.

Cue 48 — 00:03:34,485 --> 00:03:38,225

All the others have to rebase, rerun the tests.

Cue 49 — 00:03:38,725 --> 00:03:43,845

You're like waiting, waiting, waiting just because, like somebody merged a PR,

Cue 50 — 00:03:43,885 --> 00:03:50,545

it's like crazy. But it's getting so slow and I don't know, I think

Cue 51 — 00:03:50,765 --> 00:03:57,415

as much as we like exploded our number of PRs, our

Cue 52 — 00:03:57,455 --> 00:04:01,045

CI/CD spend also went through the roof.

Cue 53 — 00:04:01,085 --> 00:04:04,085

Right. And it went slow. We didn't have the capacity.

Cue 54 — 00:04:04,125 --> 00:04:06,685

It's like what is happening here.

Cue 55 — 00:04:06,725 --> 00:04:12,045

Like you know we thought we were doing good by turning it on and giving that effect.

Cue 56 — 00:04:12,085 --> 00:04:16,865

But there's like forces working against us in this space.

Cue 57 — 00:04:17,325 --> 00:04:24,285

And it is not just the features that were, you know, increasing

Cue 58 — 00:04:24,325 --> 00:04:31,085

in the factory. It's the number of agent incidents that also turn into kind of

Cue 59 — 00:04:31,125 --> 00:04:33,525

issues. Well, that issue did that.

Cue 60 — 00:04:33,565 --> 00:04:34,965

No, no, no, it run out of control.

Cue 61 — 00:04:35,005 --> 00:04:41,725

It did this. And then there's the maintenance tickets of all the things you do at

Cue 62 — 00:04:41,765 --> 00:04:45,525

night. They also add on to the PR review system.

Cue 63 — 00:04:45,565 --> 00:04:48,185

So the pressure is really building up.

Cue 64 — 00:04:49,765 --> 00:04:50,565

So

Cue 65 — 00:04:51,725 --> 00:04:57,045

there's this saying, you know, when we were, you know, in the era of CI/CD,

Cue 66 — 00:04:57,085 --> 00:05:00,885

we said if it hurts, do it more often, right.

Cue 67 — 00:05:00,925 --> 00:05:02,685

And I think that's what we're trying to do.

Cue 68 — 00:05:02,725 --> 00:05:05,225

Like we're now going to hit this.

Cue 69 — 00:05:05,285 --> 00:05:08,085

And something of the bottleneck will kind of break.

Cue 70 — 00:05:08,125 --> 00:05:12,125

But we'll better start designing for it because this is now the new normal.

Cue 71 — 00:05:12,165 --> 00:05:17,285

The new normal is parallel things happening at once in the code base by multiple

Cue 72 — 00:05:17,325 --> 00:05:21,325

people, by multiple agents. Maybe not humans, but intense agents,

Cue 73 — 00:05:21,365 --> 00:05:22,505

all that stuff.

Cue 74 — 00:05:24,885 --> 00:05:28,505

This is a very elaborate slide.

Cue 75 — 00:05:28,545 --> 00:05:32,945

you probably can't see that at the back, but imagine I ask for a ticket.

Cue 76 — 00:05:33,965 --> 00:05:39,205

So the things that I'm going to show now is some kind of things that people are

Cue 77 — 00:05:39,245 --> 00:05:43,325

working on to solve that concurrency in a way.

Cue 78 — 00:05:43,365 --> 00:05:50,445

So when you typically in the past ask for a ticket, it was on your scrum board.

Cue 79 — 00:05:50,485 --> 00:05:52,885

They said, well, I'm going to do this.

Cue 80 — 00:05:52,925 --> 00:05:55,575

You're going to do that, I'll take this ticket.

Cue 81 — 00:05:55,615 --> 00:05:57,485

That's what how does it work for agents?

Cue 82 — 00:05:57,525 --> 00:06:01,065

Right. They're trying to split this off,

Cue 83 — 00:06:02,565 --> 00:06:05,705

maybe by tasks that you understand.

Cue 84 — 00:06:06,245 --> 00:06:10,765

But another way that they're starting to do this is they're not just looking at what

Cue 85 — 00:06:10,805 --> 00:06:13,045

your intent is, because that's a logical piece.

Cue 86 — 00:06:13,085 --> 00:06:14,605

They're looking at your code base.

Cue 87 — 00:06:14,645 --> 00:06:17,245

Maybe the billing part has its own lane.

Cue 88 — 00:06:17,285 --> 00:06:21,325

So if the agent one agent is working the billing, the other working is in another

Cue 89 — 00:06:21,365 --> 00:06:26,285

piece of the code. So they're splitting things up almost for humans,

Cue 90 — 00:06:26,325 --> 00:06:29,285

but for agents not to trip over pieces.

Cue 91 — 00:06:29,325 --> 00:06:33,805

Now there's a whole spectrum from I can look maybe at the code graph.

Cue 92 — 00:06:33,845 --> 00:06:36,125

I can do it by file, by function.

Cue 93 — 00:06:36,165 --> 00:06:43,065

And some pieces have started to work almost on code, like a Google doc.

Cue 94 — 00:06:43,685 --> 00:06:47,285

We're just merging the last change in that thing.

Cue 95 — 00:06:47,325 --> 00:06:53,285

So you see it is evolving from just merging or kind of planning and doing this on a

Cue 96 — 00:06:53,325 --> 00:06:57,805

split of functionality. You will see that still above the fold,

Cue 97 — 00:06:57,845 --> 00:07:02,285

but below the fold. Your agents might do different kind of splitting because they

Cue 98 — 00:07:02,325 --> 00:07:06,185

kind of do it in logical pieces that they don't trip over into code base.

Cue 99 — 00:07:07,855 --> 00:07:12,725

Now when agent starts, you know, in your scrum board, you say,

Cue 100 — 00:07:12,765 --> 00:07:16,225

I'm going to take this ticket, so your agent needs to do the same.

Cue 101 — 00:07:16,285 --> 00:07:18,565

I'm claiming this ticket, right?

Cue 102 — 00:07:18,605 --> 00:07:23,645

But instead of just claiming it the ticket, it says I claim the ticket and I'm going

Cue 103 — 00:07:23,685 --> 00:07:28,005

to work on this code pieces. So it's signaling other agents where it might have

Cue 104 — 00:07:28,045 --> 00:07:32,765

conflicts. So things you probably don't see right now in your ticket board,

Cue 105 — 00:07:32,805 --> 00:07:35,445

it will just say, hey, do me a ticket.

Cue 106 — 00:07:35,485 --> 00:07:38,665

But this is optimizing kind of the concurrency again.

Cue 107 — 00:07:40,125 --> 00:07:40,925

Now.

Cue 108 — 00:07:43,045 --> 00:07:48,045

On your local factory, worktrees are fine somewhere using VMs,

Cue 109 — 00:07:48,085 --> 00:07:51,405

some of them using micro VMs, and that's all good.

Cue 110 — 00:07:51,445 --> 00:07:53,585

But if you start thinking about this,

Cue 111 — 00:07:54,925 --> 00:07:59,905

there is the machine and maybe you have a separate database,

Cue 112 — 00:08:01,005 --> 00:08:03,845

but there's outside world information as well.

Cue 113 — 00:08:03,885 --> 00:08:05,925

Can you freeze the APIs that are not changing?

Cue 114 — 00:08:05,965 --> 00:08:09,605

If not, the agent is changing that API while you're working.

Cue 115 — 00:08:09,645 --> 00:08:11,805

What is happening can be frozen.

Cue 116 — 00:08:11,845 --> 00:08:17,245

The context can be frozen the test that it runs because if another agent is changing

Cue 117 — 00:08:17,285 --> 00:08:21,985

the tests. So you have to think that while a git forks your code,

Cue 118 — 00:08:22,045 --> 00:08:25,725

you have to think broader. What you're actually forking in version control.

Cue 119 — 00:08:25,765 --> 00:08:32,485

Basically, your agent wants to fork the world for a while and not just the code.

Cue 120 — 00:08:32,525 --> 00:08:39,245

So there's a level of almost like isolation you could go for in a certain

Cue 121 — 00:08:39,285 --> 00:08:41,985

spectrum instead of just forking the machine.

Cue 122 — 00:08:43,125 --> 00:08:49,865

There's there's tools that one day spin up the agent in a VM,

Cue 123 — 00:08:50,005 --> 00:08:54,285

they fork the memory. It's a lot cheaper to fork the memory than spinning off all

Cue 124 — 00:08:54,325 --> 00:08:59,512

the VMs. So what they do is start the VM, put the VM in a certain shape and then

Cue 125 — 00:08:59,552 --> 00:09:03,585

they fork the memory. It's a lot easier to start up.

Cue 126 — 00:09:05,965 --> 00:09:10,945

Now. Once they're working the agent they might see conflicts.

Cue 127 — 00:09:11,085 --> 00:09:12,885

They're not sticking to the rules.

Cue 128 — 00:09:12,925 --> 00:09:15,305

They kind of tripping still over each other.

Cue 129 — 00:09:15,365 --> 00:09:19,725

So there are kind of the typically concurrency locks.

Cue 130 — 00:09:19,765 --> 00:09:21,765

Think of that as concurrent programming.

Cue 131 — 00:09:21,805 --> 00:09:26,365

I do a lock optimistic locking, pessimistic locking and going all the way.

Cue 132 — 00:09:26,405 --> 00:09:30,705

But it might be that it's not just about like I wait until it's done.

Cue 133 — 00:09:31,205 --> 00:09:37,425

I'm repairing the plan that we initially had, and some tools are already saying,

Cue 134 — 00:09:37,605 --> 00:09:41,965

well, when two agents see a conflict while they're working, they're renegotiating

Cue 135 — 00:09:42,005 --> 00:09:45,205

their scope while they're executing.

Cue 136 — 00:09:45,245 --> 00:09:47,285

Okay, I don't touch it. You touch it.

Cue 137 — 00:09:47,325 --> 00:09:48,965

It's okay. I'll get it by you.

Cue 138 — 00:09:49,005 --> 00:09:50,645

And we are synchronizing on that.

Cue 139 — 00:09:50,685 --> 00:09:56,285

So you see, there's a new form of collaboration around this concurrency that you see

Cue 140 — 00:09:56,325 --> 00:09:58,265

building up in the tools.

Cue 141 — 00:09:59,845 --> 00:10:06,661

And now imagine they coded and in Git

Cue 142 — 00:10:06,701 --> 00:10:10,185

it would typically say we merged.

Cue 143 — 00:10:10,405 --> 00:10:14,725

And if it didn't your user you as a user have to untangle this.

Cue 144 — 00:10:14,765 --> 00:10:17,785

No, no I didn't mean this like for this piece.

Cue 145 — 00:10:17,885 --> 00:10:22,725

But again, not just at the planning and the execution, but also at the merging

Cue 146 — 00:10:22,765 --> 00:10:25,545

phase. You have to have strategies.

Cue 147 — 00:10:25,685 --> 00:10:31,965

Am I going to redo the work or all the way up to I see this change coming.

Cue 148 — 00:10:32,005 --> 00:10:37,365

I'm already adapting myself because then my PR will be merging better when they both

Cue 149 — 00:10:37,405 --> 00:10:44,005

land at the same time. Again, a spectrum of people that are building new strategies

Cue 150 — 00:10:44,045 --> 00:10:46,745

to drive and solve that concurrency.

Cue 151 — 00:10:50,945 --> 00:10:57,505

This is a fun one. Two agents, one agent says, please

Cue 152 — 00:10:57,545 --> 00:11:02,445

change our total calculation from dollars to cents.

Cue 153 — 00:11:03,345 --> 00:11:10,305

At the same time, there is a new PR landing for a calculation

Cue 154 — 00:11:10,345 --> 00:11:13,205

of the total in an invoice.

Cue 155 — 00:11:14,665 --> 00:11:18,745

Both merges are syntactically correct.

Cue 156 — 00:11:18,785 --> 00:11:24,565

They will both merge perfectly, but it's not what you intended.

Cue 157 — 00:11:25,545 --> 00:11:31,945

So what is happening now is that people are looking at the merges,

Cue 158 — 00:11:31,985 --> 00:11:38,225

not just did it merge on the code level correctly, but did it merge on the

Cue 159 — 00:11:38,265 --> 00:11:44,445

intent correctly? So it might have changed while I was starting,

Cue 160 — 00:11:44,665 --> 00:11:47,265

but then we need to look at those pieces as well.

Cue 161 — 00:11:47,305 --> 00:11:51,825

Again, these are all findings of people trying to solve this.

Cue 162 — 00:11:51,865 --> 00:11:54,825

You might not hit this with two agents, but the more you're running,

Cue 163 — 00:11:54,865 --> 00:11:59,325

I hope you see there are strategies that we need to have to solve these issues.

Cue 164 — 00:12:00,825 --> 00:12:06,525

And let's say you have five PRs coming in, ten PRs.

Cue 165 — 00:12:07,065 --> 00:12:08,905

We talked about that rebase problem.

Cue 166 — 00:12:08,945 --> 00:12:11,765

One commits. The others have to rebase.

Cue 167 — 00:12:13,705 --> 00:12:18,885

Instead of waiting until they these both downwards.

Cue 168 — 00:12:20,305 --> 00:12:27,114

They look at combinations. So they call it speculative merge because they look

Cue 169 — 00:12:27,154 --> 00:12:33,545

at the different PRs coming in and say, well we can merge these five already.

Cue 170 — 00:12:33,585 --> 00:12:39,705

They're going to be consistent, let's group them and merge them in one execution or

Cue 171 — 00:12:39,745 --> 00:12:42,225

one approval thing and then look at the others.

Cue 172 — 00:12:42,265 --> 00:12:47,005

So you see we're putting not just agents to produce code or do review.

Cue 173 — 00:12:47,185 --> 00:12:53,625

We're also solving it to kind of solve conflicts, better scheduling of agents and so

Cue 174 — 00:12:53,665 --> 00:13:00,105

on. So I hope it makes kind of the point clear of where new pieces of the delivery

Cue 175 — 00:13:00,145 --> 00:13:07,305

is breaking. The model of that serial thing, like build code tests and

Cue 176 — 00:13:07,345 --> 00:13:10,965

PR and waiting for this and this is the parallelization.

Cue 177 — 00:13:13,105 --> 00:13:14,445

I'm seeing.

Cue 178 — 00:13:15,745 --> 00:13:18,445

There's a new wave of infrastructure.

Cue 179 — 00:13:19,105 --> 00:13:25,621

People are rebuilding Git, they're rebuilding the ticket systems like

Cue 180 — 00:13:25,661 --> 00:13:31,745

Linear. They're all kind of rebuilding a new version of this to deal with the load

Cue 181 — 00:13:31,785 --> 00:13:34,685

of agents working on these pieces.

Cue 182 — 00:13:35,825 --> 00:13:39,165

Some might call this this is going to be the new Kubernetes.

Cue 183 — 00:13:40,225 --> 00:13:43,945

I don't know, there's some kind of orchestrator, there's some kind of pieces.

Cue 184 — 00:13:43,985 --> 00:13:48,825

And what we've done kind of for VMs spinning up maybe in a in a Kubernetes.

Cue 185 — 00:13:48,865 --> 00:13:53,445

We're now doing it for code agents working together in a good way.

Cue 197 — 00:14:35,470 --> 00:14:40,850

So these were some examples of technology where people have concurrency.

Cue 198 — 00:14:41,190 --> 00:14:44,750

I'm now going to move more and more to the human side, the people,

Cue 199 — 00:14:44,790 --> 00:14:46,490

the concurrency of the people.

Cue 200 — 00:14:47,230 --> 00:14:52,391

Now one of the things is you turn the factory on, the factory starts nagging you

Cue 201 — 00:14:52,430 --> 00:14:56,950

also more, you know, not just for PR, but clarify my question.

Cue 202 — 00:14:56,990 --> 00:15:03,430

Do this like, hey, I've a maintenance can you review a lot of the things now what I

Cue 203 — 00:15:03,470 --> 00:15:05,161

saw quite powerful within Tessl.

Cue 204 — 00:15:05,200 --> 00:15:09,911

And I think a lot of people kind of say, I'm going to write a ticket.

Cue 205 — 00:15:09,950 --> 00:15:14,110

But what I find personally is that people, a lot of the time,

Cue 206 — 00:15:14,150 --> 00:15:18,070

they start from a Slack conversation, they have a conversation,

Cue 207 — 00:15:18,110 --> 00:15:23,730

hey, is this normal? Should we do a kind of those conversations float into Slack.

Cue 208 — 00:15:24,550 --> 00:15:29,391

Conversation goes, sometimes we ask the agents, can you verify whether that's

Cue 209 — 00:15:29,430 --> 00:15:32,370

correct? Is that the way we're doing in our code base?

Cue 210 — 00:15:32,590 --> 00:15:34,590

Sometimes it is more at the end.

Cue 211 — 00:15:34,630 --> 00:15:38,310

Okay, we have the discussion agent write it up to a ticket and go.

Cue 212 — 00:15:38,350 --> 00:15:44,690

So we're we're kind of doing that loop of interactive kind of

Cue 213 — 00:15:44,790 --> 00:15:50,430

chatting that we are now doing in our plan mode, maybe in our agent in the chat.

Cue 214 — 00:15:50,470 --> 00:15:54,850

And that goes on to kind of the ticket and a more clarified ticket.

Cue 215 — 00:15:56,230 --> 00:15:58,151

And so he keeps asking questions.

Cue 216 — 00:15:58,190 --> 00:16:02,590

Sometimes it will ask and ping other people that are not in the chat because it

Cue 217 — 00:16:02,630 --> 00:16:06,070

knows for building. We need to ask Patrick, please don't do that.

Cue 218 — 00:16:06,110 --> 00:16:11,230

But it's kind of the routing to the right person to also kind of make decisions and

Cue 219 — 00:16:11,270 --> 00:16:18,330

give input. And what's really powerful is that I saw that, you know.

Cue 220 — 00:16:20,070 --> 00:16:26,110

Typically sales and support, they'll live around in the engineering and they will go

Cue 221 — 00:16:26,150 --> 00:16:32,370

on Slack. Hey, a customer reported this, a customer has asked for this feature.

Cue 222 — 00:16:34,070 --> 00:16:38,550

This is and then engineering said, okay, we'll use our agents to see if we can make

Cue 223 — 00:16:38,590 --> 00:16:44,671

this work. And do you like this feature that has completely shifted to but why don't

Cue 224 — 00:16:44,710 --> 00:16:49,310

you ask yourself as sales or support what the agent can do?

Cue 225 — 00:16:49,350 --> 00:16:54,470

Why don't you help? It got up to a point where you actually like the feature and you

Cue 226 — 00:16:54,510 --> 00:17:00,190

can ship the feature. This is the advantage of not having to wait on your solo kind

Cue 227 — 00:17:00,230 --> 00:17:03,271

of workspace, but it's a shared place.

Cue 228 — 00:17:03,310 --> 00:17:08,491

And the difference is, you know, when vibe coding was really the rage,

Cue 229 — 00:17:08,950 --> 00:17:12,271

it was product vibe coding prototypes.

Cue 230 — 00:17:12,310 --> 00:17:19,031

Seeing what was able to do. But now with the factory is they're not building a vibe

Cue 231 — 00:17:19,070 --> 00:17:23,730

code that then engineering has to untangle and kind of build their own version of.

Cue 232 — 00:17:23,950 --> 00:17:27,830

They're using the same pipeline and on that same pipeline.

Cue 233 — 00:17:27,870 --> 00:17:34,350

It gets all the engineering rigor, all the tests, all the ways engineering likes it

Cue 234 — 00:17:34,390 --> 00:17:39,570

at the same time, while still iterating on the functionality they want.

Cue 235 — 00:17:40,030 --> 00:17:42,231

So I think that was really powerful.

Cue 236 — 00:17:42,270 --> 00:17:44,150

And typically that would have to wait.

Cue 237 — 00:17:44,190 --> 00:17:47,510

Whether a ticket was triage, they had to wait for engineering to pick it up.

Cue 238 — 00:17:47,550 --> 00:17:51,030

They had for wait for engineering to review and go from there.

Cue 239 — 00:17:51,070 --> 00:17:54,090

This kind of bypasses a lot of these things

Cue 240 — 00:17:55,430 --> 00:17:56,230

now.

Cue 241 — 00:17:58,150 --> 00:18:03,930

There has been a discussion about, should all coding go through the factory?

Cue 242 — 00:18:05,550 --> 00:18:12,410

Okay. I find it personally very tedious if I'm like exploring a spike

Cue 243 — 00:18:12,910 --> 00:18:16,630

that I have to wait the ticket, everyone comes back to me.

Cue 244 — 00:18:16,670 --> 00:18:20,870

I like my local agent for that still because I'm like sparking better and a better

Cue 245 — 00:18:20,910 --> 00:18:25,030

understanding what I want. But there's the other cases.

Cue 246 — 00:18:25,070 --> 00:18:29,890

Imagine your agent is stuck. How do you take over now?

Cue 247 — 00:18:30,230 --> 00:18:35,630

How do you help it? There was a great example by the people from HelixML is that

Cue 248 — 00:18:35,670 --> 00:18:42,200

when the agent got stuck, it opened a cloud version of

Cue 249 — 00:18:42,240 --> 00:18:48,750

VS Code completely configured for you to jump in and do like a

Cue 250 — 00:18:48,790 --> 00:18:52,910

manual piece. Still of iteration and it's good.

Cue 251 — 00:18:52,950 --> 00:18:55,510

Dispose it. Now you can continue.

Cue 252 — 00:18:55,550 --> 00:19:00,231

So this is kind of like blurring the lines between still jumping in your code base

Cue 253 — 00:19:00,270 --> 00:19:06,550

by like your IDE and kind of still working in Linear, but both have merit on like

Cue 254 — 00:19:06,590 --> 00:19:08,410

what pieces you're working on.

Cue 255 — 00:19:09,630 --> 00:19:15,510

And what we ideally want is we don't want all those questions and nagging from that

Cue 256 — 00:19:15,550 --> 00:19:16,450

agent.

Cue 257 — 00:19:17,870 --> 00:19:20,450

You see this in the coding agents as well.

Cue 258 — 00:19:20,790 --> 00:19:24,370

It asks you a few questions, but then it's really smart.

Cue 259 — 00:19:24,670 --> 00:19:31,070

It just gives you options because that's way easier than asking a question on me

Cue 260 — 00:19:31,110 --> 00:19:34,430

having to think instead of just selecting which option is it.

Cue 261 — 00:19:34,470 --> 00:19:39,110

Good. So there is a tendency to move from questions to decisions,

Cue 262 — 00:19:39,150 --> 00:19:42,630

and it's not going to ask me where do I find blah, right.

Cue 263 — 00:19:42,670 --> 00:19:46,390

No, just look at blah. It's just find it.

Cue 264 — 00:19:46,430 --> 00:19:49,610

So there's a tendency of working different with that.

Cue 265 — 00:19:50,310 --> 00:19:56,130

And then as the factory is learning, I feel we're missing a piece in that,

Cue 266 — 00:19:57,110 --> 00:20:01,810

the decisions we take by the agents, we are the decision we take on tickets.

Cue 267 — 00:20:02,990 --> 00:20:07,410

I personally think that the ticket system is the wrong storage for this.

Cue 268 — 00:20:08,470 --> 00:20:14,270

Like it needs to record that either in a ledger, either in a context like either in

Cue 269 — 00:20:14,310 --> 00:20:19,231

some kind of other form instead of keeping in a ticket, because otherwise now we

Cue 270 — 00:20:19,270 --> 00:20:26,070

have to. It's like you, you can keep all that context, but you have to synthesize

Cue 271 — 00:20:26,110 --> 00:20:29,910

the decision. So the next question doesn't come anymore with the same thing.

Cue 272 — 00:20:29,950 --> 00:20:34,030

It's what we've been doing with writing skills, writing context.

Cue 273 — 00:20:34,070 --> 00:20:36,630

But it's the same thing in a factory that we do there.

Cue 274 — 00:20:36,670 --> 00:20:42,471

We could store this in the repo, but then we have multiple people writing in the

Cue 275 — 00:20:42,510 --> 00:20:47,830

repo, and so we have don't have yet a good place of putting that like decision and

Cue 276 — 00:20:47,870 --> 00:20:49,490

informational context.

Cue 277 — 00:20:50,950 --> 00:20:55,890

We do want to keep it small. So this is another piece.

Cue 278 — 00:20:57,110 --> 00:21:02,650

There has been an optimization for no coding conflicts, which is great,

Cue 279 — 00:21:02,950 --> 00:21:08,990

but we do have to balance this between a human user still needs to be able to review

Cue 280 — 00:21:09,030 --> 00:21:15,590

this. So that tendency we could optimize for review experience and then kind of

Cue 281 — 00:21:15,630 --> 00:21:18,030

ignore the coding conflicts from the agents.

Cue 282 — 00:21:18,070 --> 00:21:20,610

But probably there is a balance between both

Cue 283 — 00:21:22,190 --> 00:21:26,090

and I know there's a lot of discussion about.

Cue 284 — 00:21:28,030 --> 00:21:31,530

Going without looking at the code.

Cue 285 — 00:21:31,910 --> 00:21:37,510

And I've done this a few times, like I see somewhere on on the socials and they say

Cue 286 — 00:21:37,550 --> 00:21:39,110

we don't look at the code anymore.

Cue 287 — 00:21:39,150 --> 00:21:44,150

Okay. I asked them the question, what kind of application are you using when they

Cue 288 — 00:21:44,190 --> 00:21:49,110

explain me? Well, we have this beautiful setup with multiple agent adversarial

Cue 289 — 00:21:49,150 --> 00:21:52,070

review tests and all those pieces.

Cue 290 — 00:21:52,110 --> 00:21:57,570

Okay. I asked them the question, what happens

Cue 291 — 00:21:58,950 --> 00:22:01,250

if there's a failure in production?

Cue 292 — 00:22:02,470 --> 00:22:05,231

And what I usually hear is like, yeah, it's okay.

Cue 293 — 00:22:05,270 --> 00:22:08,110

We're a small startup. It doesn't matter too much.

Cue 294 — 00:22:08,150 --> 00:22:08,950

And.

Cue 295 — 00:22:11,390 --> 00:22:14,170

The point is not that it will.

Cue 296 — 00:22:14,350 --> 00:22:18,330

We get up to a point where this is a perfect acceptance rate.

Cue 297 — 00:22:18,550 --> 00:22:21,650

The point is that we have to assess the risk.

Cue 298 — 00:22:22,150 --> 00:22:28,430

And so what you see in factories right now is they route decisions based on risk

Cue 299 — 00:22:28,470 --> 00:22:32,610

calculation of this. Now there's this simple example.

Cue 300 — 00:22:33,030 --> 00:22:37,390

You have a code base. There is a directory authentication.

Cue 301 — 00:22:37,430 --> 00:22:39,430

What do you think. Should we cut out.

Cue 302 — 00:22:39,470 --> 00:22:41,750

What's the risk of this. Right.

Cue 303 — 00:22:41,790 --> 00:22:48,070

And the other one is like maybe like show some nice thing on the website different

Cue 304 — 00:22:48,110 --> 00:22:52,330

levels. And so that is kind of part of the new.

Cue 305 — 00:22:52,870 --> 00:22:56,650

It is there's verification, there's testing, there's all those pieces.

Cue 306 — 00:22:56,710 --> 00:23:01,270

But in a modern factory there belongs a risk calculation on what you're accepting.

Cue 307 — 00:23:01,310 --> 00:23:06,750

Yes. No, no. There are different ways of I can ship the documentation.

Cue 308 — 00:23:06,790 --> 00:23:07,990

It's not the end of the world.

Cue 309 — 00:23:08,030 --> 00:23:10,630

We say it's a typo was generated by agents.

Cue 310 — 00:23:10,670 --> 00:23:16,290

All excuses go. We can do canary testing, you know, kind of small pieces.

Cue 311 — 00:23:16,630 --> 00:23:20,471

And then we can see also. How far verification goes.

Cue 312 — 00:23:20,510 --> 00:23:26,330

Now what most people do is we optimize to make the failure less likely

Cue 313 — 00:23:27,550 --> 00:23:31,930

that we verify the outcome. Now you can say we're reduced by risk,

Cue 314 — 00:23:32,190 --> 00:23:37,170

but what if something slips? This becomes architecture again.

Cue 315 — 00:23:38,470 --> 00:23:41,770

How can you deal in your architecture with failure?

Cue 316 — 00:23:42,350 --> 00:23:46,490

Can you roll back the data? Can you roll up the version?

Cue 317 — 00:23:46,790 --> 00:23:49,430

Can you undo any side effects that it did?

Cue 318 — 00:23:49,470 --> 00:23:55,490

So this is kind of mixing mitigating when failure happens.

Cue 319 — 00:23:55,830 --> 00:23:59,711

And that I think you have to see this in the whole spectrum of that thing.

Cue 320 — 00:23:59,750 --> 00:24:04,390

Not just like limiting the occurrence, but you know, in the,

Cue 321 — 00:24:04,430 --> 00:24:09,550

in the in the long past ago, developers were throwing WAR files and JAR files over

Cue 322 — 00:24:09,590 --> 00:24:11,870

the wall. We didn't know what was happening.

Cue 323 — 00:24:11,910 --> 00:24:13,310

So we were designing like, what?

Cue 324 — 00:24:13,350 --> 00:24:15,350

It fails, we could easily go back and so on.

Cue 325 — 00:24:15,390 --> 00:24:17,471

So that's what I want you to think as well.

Cue 326 — 00:24:17,510 --> 00:24:21,370

Not focusing only on verification and testing.

Cue 327 — 00:24:23,230 --> 00:24:29,210

I would intestinal. I'm one of the few people who works remote,

Cue 328 — 00:24:29,550 --> 00:24:35,711

and I often do not hear all the conversations in the company because yeah,

Cue 329 — 00:24:35,750 --> 00:24:42,770

it's not. By that I mean well, that I mean ill, but it's I'm not hearing it

Cue 330 — 00:24:43,110 --> 00:24:47,490

when we turn on the factory. It was a very an irony for me.

Cue 331 — 00:24:47,990 --> 00:24:50,370

Everybody felt out of the loop.

Cue 332 — 00:24:50,550 --> 00:24:52,990

There was so much happening, so many new features.

Cue 333 — 00:24:53,030 --> 00:24:58,390

So what I saw in actually the Slack is there were way more reporting of today this

Cue 334 — 00:24:58,430 --> 00:25:02,910

happened, or we did this because there was no other way to keep this in the loop.

Cue 335 — 00:25:02,950 --> 00:25:06,630

And if you take that even further, how do you keep sales and marketing in the loop

Cue 336 — 00:25:06,670 --> 00:25:11,430

and supporting the loop, if you're churning out so much, and so you're also

Cue 337 — 00:25:11,470 --> 00:25:18,130

tailoring your updates in the speak of whatever role that person has,

Cue 338 — 00:25:18,270 --> 00:25:22,670

right? So the irony is that you would say, well, we don't communicate it anymore.

Cue 339 — 00:25:22,710 --> 00:25:27,330

All of a sudden we're communicating even more with each other in that way.

Cue 340 — 00:25:28,430 --> 00:25:35,650

So in a nutshell, I think context and skills are for the thing.

Cue 341 — 00:25:36,030 --> 00:25:40,870

Exceptions still exist. And that is kind of like the balance in the factory.

Cue 342 — 00:25:40,910 --> 00:25:43,150

You want it to go away, you want it to solve.

Cue 343 — 00:25:43,190 --> 00:25:46,070

So you give it the context, you make this work.

Cue 344 — 00:25:46,110 --> 00:25:50,170

And it's also one of the pieces that just turning on on a factory.

Cue 345 — 00:25:51,750 --> 00:25:57,570

If you don't have these pieces in place, there is a sense of being factory ready,

Cue 346 — 00:25:57,910 --> 00:26:01,590

having some kind of tests, having some kind of observability,

Cue 347 — 00:26:01,630 --> 00:26:03,670

having some kind of context rules.

Cue 348 — 00:26:03,710 --> 00:26:07,910

Otherwise you're grappling at the first phase of getting that everything.

Cue 349 — 00:26:07,950 --> 00:26:08,750

Okay

Cue 350 — 00:26:09,990 --> 00:26:15,870

now, I think personally is that a lot of people will keep working,

Cue 351 — 00:26:15,910 --> 00:26:19,670

maybe in the factory. Think about the features going further.

Cue 352 — 00:26:19,710 --> 00:26:25,231

But I also saw at Tessl, There's a little bit of a group forming that say we keep

Cue 353 — 00:26:25,270 --> 00:26:30,830

the factory running. It's it's a little bit like the platform team for Kubernetes.

Cue 354 — 00:26:30,870 --> 00:26:34,990

We'll keep everything running so you can keep doing your business.

Cue 355 — 00:26:35,030 --> 00:26:39,890

And I think with a platform and a factory this is quite similar to do.

Cue 356 — 00:26:41,710 --> 00:26:44,910

So I hope this gave you some insights.

Cue 357 — 00:26:44,950 --> 00:26:49,430

There's a lot more to explain of things where pressure is building up,

Cue 358 — 00:26:49,470 --> 00:26:54,610

where people are trying to untangle this concurrency, do some solutions.

Cue 359 — 00:26:56,310 --> 00:27:03,110

It's not finished, but I think the the pressure is only building up in both the code

Cue 360 — 00:27:03,150 --> 00:27:06,211

and making decisions at the same time.

Cue 361 — 00:27:07,150 --> 00:27:09,690

And we're now entering at work.

Cue 362 — 00:27:09,910 --> 00:27:16,570

The era of it's not the humans anymore were on Slack, but we have personal agents

Cue 363 — 00:27:17,430 --> 00:27:22,450

approving things across our preferences, not the factory preferences.

Cue 364 — 00:27:22,590 --> 00:27:26,750

I don't know where this is going to end, but this is another level like this is

Cue 365 — 00:27:26,790 --> 00:27:29,030

another collaboration level as such.

Cue 366 — 00:27:29,070 --> 00:27:32,190

So my advice is now come back next year.

Cue 367 — 00:27:32,230 --> 00:27:36,970

Brace yourself. It's all going to work and it's all going to change again.

Cue 368 — 00:27:37,630 --> 00:27:41,530

And I would say thank you for listening to my talk.

Cue 369 — 00:27:47,170 --> 00:27:50,451

Okay. Thank you. Yeah. Sorry. You can get the slides.

Cue 370 — 00:27:50,490 --> 00:27:54,130

Just DM me with feedback. Try the Tessl factory of course.

Cue 371 — 00:27:54,170 --> 00:28:00,790

And a lot of the research that I do also put out freely on the site concurrent CD,

Cue 372 — 00:28:01,010 --> 00:28:05,410

where I got like social quotes of people trying and project that I find right now.

Cue 373 — 00:28:05,450 --> 00:28:07,430

Thank you. Sorry, sorry. Go ahead.

Cue 374 — 00:28:07,610 --> 00:28:11,830

No. All good. Thank you. And I wanted us to say it's Patrick Debois.

Cue 375 — 00:28:16,670 --> 00:28:21,150

The godfather of DevOps, also created DevOpsDays.

Cue 376 — 00:28:21,190 --> 00:28:23,550

He also told me he invented punctuation the other day.

Cue 377 — 00:28:23,590 --> 00:28:26,830

I think he's just getting he's just trying to claim too much now in Belgium now?

Cue 378 — 00:28:26,870 --> 00:28:29,390

Yeah, yeah. Awesome. Any we have a few minutes.

Cue 379 — 00:28:29,430 --> 00:28:31,930

Any questions? Feel free to raise your hands.

Cue 380 — 00:28:31,990 --> 00:28:32,790

Yes.

Cue 381 — 00:28:36,230 --> 00:28:39,810

On those merge conflicts that you mentioned in the beginning of the talk.

Cue 382 — 00:28:39,870 --> 00:28:44,951

Do you think we can learn from scheduling algorithms, on CPUs and how conflicts are

Cue 383 — 00:28:44,990 --> 00:28:47,330

resolved there between threads and others?

Cue 384 — 00:28:47,710 --> 00:28:48,570

Yeah. So,

Cue 385 — 00:28:49,990 --> 00:28:54,150

there's a there's a whole body of knowledge about, like, distributed systems coming

Cue 386 — 00:28:54,190 --> 00:29:01,110

back to items. There's a whole thing about turning this into a search problem of the

Cue 387 — 00:29:01,150 --> 00:29:03,390

optimizing roads and kind of the work.

Cue 388 — 00:29:03,430 --> 00:29:06,990

So that's definitely there. But most of the factories right now,

Cue 389 — 00:29:07,030 --> 00:29:10,430

they have like the simplistic scheduler of, okay, just run the thing.

Cue 390 — 00:29:10,470 --> 00:29:14,711

And that's one of the points is like that needs to change in a better way I believe.

Cue 391 — 00:29:14,750 --> 00:29:16,250

So, yeah. Thank you.

Cue 392 — 00:29:18,500 --> 00:29:20,450

For one last question. If there's anything.

Cue 393 — 00:29:22,400 --> 00:29:24,650

Oh good. Please give it up again for Patrick.

Cue 394 — 00:29:24,710 --> 00:29:25,530

Thank you.

skills

talk-debois-concurrent-delivery

tile.json