We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
A course about delegating engineering work rather than pairing on it: scoping tasks Codex can finish alone, preparing the environments they run in, and reviewing what comes back.
Booked privately for your team. Dates and length are agreed when you book.
Every module ends with something participants can repeat on Monday morning, in your codebase and against your conventions.
Write a brief complete enough that a task comes back finished rather than half-done and confused.
Keep several independent tasks in flight without losing track of which branch is holding what.
Define the container a task runs in so it has every dependency it needs and none of your credentials.
Read a change that was written without you watching, and know which parts of it to check first.
Drive Codex locally for the work that is quicker to supervise than it is to specify.
Separate the tasks worth delegating from the ones where writing the brief costs more than the work.
Built around hands-on work rather than slides. The running order and the depth of each module are adjusted to the group before delivery.
Every length is drawn from the same modules. A longer booking is more of the course, not a different one.
1 day
The delegation model and how to scope a task so it comes back finished. One day, and for most teams that is the whole of it.
2 days
Adds the local command line and the work of fitting delegated changes into a review process that was designed for humans.
Not sure which one fits? The intake call settles it, and the length can still change afterwards.
The curriculum above is a starting point, not a syllabus. Before anything is booked I find out where your team actually stands, then rebuild the course around that. A team already running agents daily spends its two days somewhere completely different from one that installed the tool last week.
Step 1
A call before anything is agreed: what your team already uses, what has gone wrong so far, and what you need them doing differently afterwards.
Step 2
Language, framework, review process, CI. Exercises are rebuilt against your repository so nothing in the room is hypothetical.
Step 3
Modules get dropped, deepened or added. You see the adjusted outline and sign it off before the date is fixed.
Step 4
We run the course, then check in once the team has applied it to real work and the awkward questions have surfaced.
What gets adjusted
Same material either way. The format changes how much of it lands in the first week.
I come to your office and work with the team in the room. Usually the most effective option for a first rollout, because the sideways questions get answered as they come up.
Delivered live over video in focused blocks rather than one long day, with shared screens and hands-on exercises on your own work.
A day on site to get everyone moving, followed by shorter remote sessions once the team is applying it to real work and hitting real friction.
There is no public schedule. Every course is booked privately for a single team, and we agree the dates together.
Software engineer and AI coding trainer
I train engineering teams to work with AI coding tools, and I use the same tools to ship production software every week. The material comes out of building things, not out of a slide deck.
Before going freelance I spent six years as technical co-founder of a marketing agency, responsible for everything technical from automation infrastructure to coordinating a freelancer network. That is why the courses spend as much time on review, guardrails and rollout as they do on prompting.
The things teams ask before booking. If yours is not here, ask me directly.
No. The delegation model is easier to pick up than pairing with an agent, because there is far less to steer in real time. Working knowledge of pull request review matters much more, since that is the skill the entire day rests on.
A Codex-enabled account each, plus a repository they are allowed to open pull requests against. Both are worth arranging a week ahead. I send the exact requirements once a date is agreed, including which plan covers the parallel task work.
Yes, and the environment setup module only pays off if they do. Half of what makes delegation work is a container that can install your dependencies and run your tests, and getting that right for your stack is time very well spent in a workshop.
Yes, because the working model is different: one is a conversation you steer, the other is a brief you hand over and come back to. Teams using both tend to split their work between them. If you only want one course, the Claude Code one is broader; this one goes deeper on delegation.
Five to twenty. Delegated tasks take real minutes to run, so the day is paced around those gaps, and a smaller group is what makes the discussion in each gap worth having.
Yes, in German or English. The tool's output, its configuration files and its documentation are all English, so the materials follow that by default, and a German version is available if you would rather have one.
Still not sure whether this is the right fit for your team?
Tell me the size of the group, the codebase they work in, and roughly when you want to run it. I will come back with a proposal.
Delivered in English or German, on site across Europe or remotely.
Trusted by teams & training providers
I deliver AI training for some of Europe's leading organisations and L&D platforms.
Cegos Integrata
Commissioned trainer via leading European L&D provider
NobleProg
AI coding workshops via one of the world's largest IT training marketplaces
Innomotics
In-house AI training for engineering teams
Bots & People
Commissioned trainer for developer workshops
Code First Girls
Course creator — 3-month AI & agentic tools curriculum
Nomad Summit
Conference speaker on AI tools, agentic development, and developer workflows (2025)
Vertiv
In-house AI-assisted coding training for engineering teams