- Duration
- One day
- Participants
- 5 to 15
- Location
- At your office
- Language
- Dutch or English
What the kata is
One day in a real codebase, learning step by step to direct an agent on code that already exists. Like a kata, you learn the movement by repeating it: every exercise builds on the code from the step before. The repository is the lesson, and at the end the build decides whether what came out is good enough.
The course material, the code and the assignments are one whole, and they stay available after the training day. Every page yields the slide the trainer puts on screen, so what you read back later is exactly what you saw that day. The same pages carry a self-study track, in Dutch and English, so you keep building at your own pace and take your colleagues along. The trainers work this way themselves every day: they are not only in front of the room, they sit beside you at the screen.
How your day runs
The steps build on one another. Where an agent's answer comes from, through to what changes in your own role.
Start here
How the kata works, how to run the project on your own machine, and a first flag board: codes you earn with a solution that works.
How this kata works · The backend · Workshop
Context, model, mechanisms
Where an agent's answer comes from: what is in the context window, what each layer costs and what happens when it fills up.
Tokens · Your prompt · Tools · Context · The session · The harness · The model · Truth · Workshop · Recap
Agentic engineering
How you work with an agent rather than against one. The longest step of the day, and the afternoon workshop sits in it.
Project evolution · Project setup · Craft · Steering · Recurring patterns · Workflows · What it asks of you · Parallel workflows · Spending tokens · Workshop
Soft skills
The part that is not about code: what changes about the work itself, and about how you talk about it.
Change management · Expectation management · Impostor syndrome
What sticks
Every theme has an exercise behind it where you do it yourself, and every one of them comes back in the work the day after.
How you practise
By doing. Most steps carry a flag board: short codes that only surface once you run the code on your own machine, instrument it or harden it. They are nowhere in the text and a search will not find them. The quizzes beside them run in the browser and keep working with the service down. In the afternoon workshop the build decides: coverage, complexity and mutation testing say whether your code is ready, not the agent's word for it.
What you bring
Ready to make your developers work more efficiently?
Tell us briefly how big your team is and where it gets stuck today. We propose a day built around you, at your office, and we also say when a kata is not what you need.