Videos W76woOYHlvY
Software Engineering Is Becoming Plan and Review — Louis Knight-Webb, Vibe Kanban
Scene timeline
72 shot(s).
keyframes kept every frame deduplicated
What was stored
- cues
- 232
- whisperx 232
- chunks
- 34
- from 232 cues
- keyframes
- 52
- kept of 72 captured
- frames with text
- 52
- 2,056 lines read
- chapters
- 10
- from the source metadata
- keyframe bytes
- 7.7 MB
- word timings on 232 cues
Provenance
| stage | state | model | started | took |
|---|---|---|---|---|
fetch |
done | — | 2026-08-10 18:07 | 1m 54s |
stt |
done | — | 2026-08-10 18:09 | 21s |
chunk |
done | — | 2026-08-10 18:10 | 0s |
text_embed |
done | — | 2026-08-10 19:54 | 1s |
keyframe |
done | — | 2026-08-10 18:10 | 1m 52s |
ocr |
done | — | 2026-08-10 18:12 | 30s |
frame_embed |
done | — | 2026-08-10 19:54 | 9s |
Frames, and what the machine read
-
- AlEngineer0.98
- EUROPE1.00
-
- PRESENTINGSPONSOR1.00
- Google DeepMind1.00
-
- PLATINUM SPONSORS0.98
- # Braintrust0.96
- WorkOS OpenAI0.95
-
- AlEngineer0.98
- EUROPE1.00
- What are we even0.98
- to do all day?1.00
- Software Engineer Edition1.00
- AlEngineer0.99
- EUROPE1.00
-
- *★*0.53
- AIE1.00
- ★1.00
- What are we even0.97
- going1.00
- to do all day?1.00
- Software Engineer Edition1.00
- Google DeepMind1.00
- AlEngineer0.99
- EUROPE1.00
- 20261.00
-
- AIE1.00
- Louis Knight-Webb0.97
- @tokengobbler1.00
- ★1.00
- vibekanban.com1.00
- london.aitinkerers.org1.00
- Engineering the future of Al0.99
- AlEngineer0.99
- EUROPE1.00
- 20260.99
-
- Leaderboards1.00
- There's an all-nw, challenging SWE-bench Multimodal, containing software issues described with images. Leam more here.0.94
- Bash Only0.99
- Verified1.00
- Lite1.00
- Full1.00
- Multimodal1.00
- Verified is a human-filtered subset of 500 instances (details)0.99
- Fiters:0.99
- No Filters0.97
- All Tags0.96
- Model1.00
- % Resolved0.99
- Org1.00
- Date1.00
- Site1.00
- EPAM AI/Run Developer Agent v20250719 + Claude 4 Sonnet0.98
- 76.801.00
- 2025-08-041.00
- e0.65
- ★1.00
- ACoder1.00
- 76.401.00
- 2025-08-191.00
- e0.86
- AIE1.00
- ★1.00
- TRAE1.00
- 75.200.99
- 2025-06-121.00
- e0.96
- ★1.00
- Harness AI1.00
- 74.801.00
- 2025-07-311.00
- e0.99
- ★1.00
- ★1.00
- ★1.00
- Lingxi-v1.5_claude-4-sonnet-202505141.00
- 74.601.00
- 2025-07-201.00
- e0.92
- Refact.ai Agent1.00
- 74.401.00
- 2025-06-031.00
- e0.98
- Anthropic1.00
- Tools + Claude 4 Opus (2025-05-22)0.98
- 73.201.00
- 2025-05-221.00
- e0.84
- Tools + Claude 4 Sonnet (2025-05-22)0.99
- 72.400.92
- 2025-05-221.00
- e0.58
- Qodo Command0.98
- 71.201.00
- 2025-07-151.00
- Bloop1.00
- 71.200.98
- 2025-07-101.00
- e0.53
- Us!1.00
- Warp0.99
- 71.000.89
- 2025-06-231.00
- e0.65
- Moatless Tools + Claude 4 Sonnet0.99
- 70.801.00
- 2025-06-111.00
- e0.93
- EURUPE0.94
- TRAE1.00
- 70.601.00
- 2025-05-191.00
- e0.94
- OpenAI1.00
- Refact.ai Agent1.00
- 70.401.00
- 2025-05-151.00
- e0.91
- OpenHands + Claude 4 Sonnet0.99
- 70.401.00
- 580.52
- 2025-05-241.00
- e0.83
- Braintrust1.00
- WorkOS OpenAI0.92
- AlEngineer0.99
- EUROPE1.00
-
- AGENDA1.00
- 1. Background: everything is plan and review0.98
- 2. Balancing planning and review0.99
- 3. Long running agents0.99
- AIE1.00
- 4. Let's shut my company down0.99
- ★1.00
- ★1.00
- #Braintrust0.96
- WorkOS OpenAI0.95
- AlEngineer0.99
- EUROPE1.00
- 20261.00
-
- AIE1.00
- 1. Background: everything is plan1.00
- ★0.99
- ★1.00
- and review0.99
- AlEngineer0.97
- AlEngineer0.97
- EUROPE1.00
- 20261.00
-
- Ratios: 1843 - 20210.96
- AIE1.00
- ★1.00
- ★1.00
- Planning1.00
- Writing code1.00
- Reviewing1.00
- Reviewing other1.00
- my code1.00
- people's code0.99
- Source: vibes0.99
- AlEngineer0.96
- AlEngineer0.99
- EUROPE1.00
- EUROPE1.00
- 20261.00
-
- Ratios1.00
- GitHub Copilot1.00
- AIE1.00
- 20211.00
- Planning1.00
- Writing code1.00
- Reviewing1.00
- Reviewing other1.00
- my code0.98
- people's code1.00
- ★1.00
- ★1.00
- 20221.00
- Planning1.00
- Writing code1.00
- Reviewing1.00
- Reviewing other1.00
- my code1.00
- people's code1.00
- Source: vibes0.99
- AlEngineer0.96
- AlEngineer0.99
- EUROPE1.00
- 20261.00
-
- Stackverflow0.91
- Ratios1.00
- ChatGPT1.00
- 20211.00
- Planning1.00
- Writing code1.00
- Reviewing1.00
- my code1.00
- Reviewing other1.00
- people's code0.99
- AIE1.00
- ★1.00
- ★1.00
- Reviewing1.00
- Reviewing other1.00
- 20221.00
- Planning1.00
- Writing code1.00
- my code1.00
- people's code1.00
- 20231.00
- Planning1.00
- Writing code1.00
- Reviewing my0.98
- Reviewing other0.99
- code1.00
- people's code1.00
- Source: vibes0.99
- Engineering the future of Al1.00
- AlEngineer0.97
- EUROPE1.00
- 20261.00
-
- Ratios1.00
- CURSOR1.00
- Reviewing0.98
- Reviewing other1.00
- 20211.00
- Planning1.00
- Writing code0.95
- my code1.00
- people's code0.98
- AIE1.00
- 20221.00
- Planning1.00
- Writing code0.97
- Reviewing1.00
- my code0.97
- Reviewing other0.99
- people's code0.99
- ★1.00
- ★1.00
- ★1.00
- 20231.00
- Planning1.00
- Writing code0.96
- Reviewing my0.97
- Reviewing other0.99
- code1.00
- people's code1.00
- 20241.00
- Planning1.00
- Writing1.00
- Reviewing my code1.00
- Reviewing other1.00
- code1.00
- people's code1.00
- Source: vibes0.97
- Engineering the future of Al1.00
- AlEngineer0.99
- 20260.99
-
- Ratios1.00
- 20211.00
- Planning1.00
- Writing code0.98
- Reviewing1.00
- Reviewing other1.00
- my code1.00
- people's code1.00
- 20221.00
- Planning1.00
- Writing code0.96
- Reviewing1.00
- my code1.00
- Reviewing other1.00
- people's code1.00
- ★1.00
- AIE1.00
- ★1.00
- ★1.00
- ★1.00
- 20231.00
- Planning1.00
- Writing code0.96
- Reviewing my1.00
- code1.00
- Reviewing other0.99
- people's code1.00
- 20241.00
- Planning1.00
- Writing1.00
- Reviewing my code1.00
- Reviewing other0.99
- code1.00
- people's code1.00
- 20251.00
- Planning1.00
- Reviewing1.00
- Reviewing other1.00
- my code1.00
- people's code1.00
- Source: vibes0.97
- Writing code1.00
- Engineering the future of Al1.00
- AlEngineer0.99
- 20260.99
-
- Did we get the time we used to1.00
- spend writing code back, or did1.00
- AIE1.00
- it just create more work in other0.98
- ★1.00
- categories?1.00
- 20251.00
- Planning1.00
- Reviewing1.00
- Reviewing other1.00
- my code1.00
- people's code1.00
- Writingcode1.00
- Engineering the future of Al1.00
- AlEngineer0.99
- 20260.99
-
- AIE1.00
- 2. Balancing planning and review1.00
- ★1.00
- ★1.00
- Engineering the future of Al1.00
- AlEngineer0.99
- EUROPE1.00
- 20260.99
-
- Spend a lot of time planning0.98
- Very comprehensive plan doc0.99
- Specs1.00
- AIE1.00
- ★1.00
- Interrogation1.00
- ★1.00
- ★1.00
- ★1.00
- More time spent planning1.00
- + Coding agent runs for longer0.99
- +0.94
- Less time needed for review0.98
- Code1.00
- Planning1.00
- AI working1.00
- QA1.00
- review1.00
- AlEngineer0.95
- AlEngineer0.99
- EUROPE1.00
- 20261.00
-
- Spend a lot of time planning0.99
- AlEngineer0.98
- Very comprehensive plan d1.00
- Specs1.00
- EUROPE1.00
- Interrogation1.00
- More time spent planning1.00
- Coding agent runs for lon1.00
- Less time needed for revi1.00
- Planning1.00
- AI wor1.00
- AlEngineer0.99
- EUROPE1.00
-
- Spend a lot of time reviewing0.99
- Loosely defined prompts1.00
- More time QA'ing manually1.00
- AIE1.00
- Synchronous1.00
- ★1.00
- ★1.00
- ★1.00
- Less time spent planning1.00
- Coding agent yields back faster0.99
- More back and forth1.00
- AI1.00
- AI1.00
- AI1.00
- Planning1.00
- QA1.00
- QA1.00
- QA1.00
- Code review1.00
- working1.00
- working1.00
- working1.00
- Engineering the future of Al1.00
- AlEngineer0.98
- 20261.00
-
- Your 'mode' of vibe engineering1.00
- is influenced by the type of work0.99
- AIE1.00
- ★1.00
- Frontend1.00
- Backend1.00
- New features1.00
- Review heavy0.98
- Plan heavy1.00
- Refactoring/migration1.00
- Plan heavy0.95
- Plan heavy1.00
- AlEngineer0.96
- AlEngineer0.99
- EUROPE1.00
- EUROPE1.00
- 20261.00
-
- Your 'mode' of vibe engineering1.00
- is influenced by the type of work0.99
- AIE1.00
- ★1.00
- ★1.00
- Frontend1.00
- Backend1.00
- New features1.00
- Review heavy1.00
- Plan heavy1.00
- Refactoring/migration1.00
- Plan heavy1.00
- Plan heavy1.00
- Engineering the future of Al1.00
- AlEngineer0.98
- EUROPE1.00
- 20261.00
-
- As coding agents become more0.99
- AIE1.00
- capable, the time before human0.99
- ★1.00
- intervention is required grows1.00
- Engineering the future of Al1.00
- AlEngineer0.97
- 20261.00
Transcript
232 cues· 3,294 words· 17,460 chars
- 0:15 Is this mic on?
- 0:15 Yes, this mic is on.
- 0:16 How are we doing?
- 0:19 Fucking fantastic!
- 0:20 Yeah!
- 0:21 Let's go!
- 0:22 All right.
- 0:26 So the title of this is about planning and review, but I think the real point behind this is basically what are we all going to do after AI continues to get really, really good?
- 0:39 I'm Louie.
- 0:40 I'm the founder of a startup called Vibe Kanban, and I also started the London chapter of AI Tinkerers, which is a great community if you're in London looking for events.
- 0:54 You should listen to me because I have done some stuff like get on the SWE bench verified leaderboard ahead of OpenAI.
- 1:03 This is a couple of months old now.
- 1:04 But anyway, you know, it's always nice to know that the people talking have done some research in the space.
- 1:11 The agenda for today class is we're going to, I'm gonna walk you through why I have arrived at the conclusion that basically all software engineers are gonna do all day is plan and review stuff.
- 1:23 And I'm gonna talk about how to think about balancing that, if that is what you do all day.
- 1:30 I'm gonna talk about time horizon and how agents are running for longer and how that changes the behavior of the job.
- 1:39 And then at the end, we're going to shut my company down.
- 1:42 And we'll get onto that later on.
- 1:45 So let's get started.
- 1:46 Everything is plan and review.
- 1:47 So work that we software engineers do.
- 1:51 Everybody in here is a software engineer, right?
- 1:53 Yes?
- 1:54 OK.
- 1:54 Most people.
- 1:56 We plan stuff.
- 1:57 We write code.
- 1:58 We review code.
- 1:59 And we review other people's code.
- 2:01 Roughly the work that we do.
- 2:04 The ratios until GitHub Copilot hit the scene were roughly this for me.
- 2:09 I know it depends on whether you work in a big company or a small company and things like that, but a lot of it was writing code and not very much of it compared to that was planning and reviewing code.
- 2:20 And what we see is over time, with things like the first version of GitHub Copilot, that basically the writing code part starts to shrink.
- 2:29 So, you know, chat GPT arrived, suddenly, you know, you can like generate functions and paste them in.
- 2:36 And then Cursor, not Cursor today, but like the original version of Cursor arrives, and then it's like able to complete a whole page of code.
- 2:44 And then you get Claude code, and it's like, wow, you know, I actually am not really doing much code writing anymore.
- 2:51 So it kind of poses an interesting question though, which is, say we were spending four hours a day coding before, does that mean I now get four hours back if I'm not doing any actual coding?
- 3:04 The answer of course is no, it has displaced work.
- 3:07 work that you or time that was previously spent doing the coding has moved it has moved to planning and reviewing i think it is an accelerant you're probably getting more done in the day but it's probably like you know you get uh 20 minutes back for every half an hour that you were you know spending coding and some other time has gone to planning and reviewing
- 3:30 So I want to talk about that.
- 3:32 What is this new way of working?
- 3:35 And I think there's fundamentally two approaches that people take.
- 3:38 I'm not going to get too specific about specs or playwright MCPs or things like that.
- 3:44 There's tons of fascinating talks about that at this event.
- 3:48 I just want to kind of conceptually ground what we're talking about here today.
- 3:52 The first way is the plan-based approach.
- 3:56 This is where you spend a lot of time upfront planning the work that you want a coding agent to do.
- 4:03 So the smells of whether you are doing this type of work would probably look like you're writing a very comprehensive plan doc, markdown file.
- 4:12 You're maybe using like one of these spec frameworks.
- 4:15 you're interrogating.
loading
Chapters
- 0:00 Intro and agenda
- 1:45 Why software engineering is shifting to plan and review
- 3:30 The two approaches: Plan-based vs. Review-heavy
- 6:02 The matrix: Feature development vs. migrations and maintenance
- 7:27 The impact of agent execution time
- 9:52 Managing the 'five-minute' agent threshold
- 10:29 Parallelization and workflow management
- 12:00 Vision for future coding interfaces and 'focus maxing'
- 14:00 Announcement: Shutting down Vibe Kanban
- 18:13 Q&A: Next steps and reflections on the startup journey