We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
A hands-on course that takes your developers from first prompt to reviewed, merged pull request, working in your own repository rather than a toy example.
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.
Take a ticket through to a reviewed pull request with Claude Code, without losing track of what changed.
Write project instruction files that make the agent follow your conventions instead of inventing its own.
Review agent-written code quickly, and recognise the failure modes that a green test suite does not catch.
Configure permissions and hooks so agent runs stay safe inside a real repository.
Turn repetitive engineering chores into repeatable commands and delegated subagent runs.
Judge when reaching for an agent pays off, and when writing the code yourself is simply faster.
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 agent loop and how to steer it. Enough for a team that should be writing real code with Claude Code by the end of the day.
2 days
Adds the working rhythm and the guardrails a team needs before it lets an agent near a shared repository.
4 days
Adds what only pays off once the whole team is on it: shared configuration, sub-agents, and measuring whether any of it worked.
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 course starts from how the agent loop works, so developers who have never run an agent can follow from the beginning. It does assume everyday professional coding experience, because most of the value sits in the review and judgement material rather than in the typing.
Yes, and it is the version I recommend. Exercises land far better against code the team already argues about. Send me a rough description of the stack beforehand and I will adapt the exercises. If the code cannot leave the building, the course runs entirely on your machines and I bring a fallback repository for anything sensitive.
Yes. Everyone needs working access on the day, and it is worth sorting a week ahead rather than on the morning. Once we agree a date I send the exact requirements, including which plan covers what we will be doing. If procurement is slow at your end, say so early and I will plan the exercises around whatever access you can get in time.
Between five and twenty-five. Below five the group discussions lose most of their value, and from about fifteen upwards I run fixed pairs so nobody gets stuck at the keyboard. Larger organisations usually run several cohorts instead of one full room.
On request, yes. A certificate naming the participant, the date and the material covered is available as an add-on and is sent digitally after the course. It is a record of attendance rather than an examined certification: there is no exam attached to this course.
The workflow, guardrail and review material transfers almost completely, because the hard part is context and review rather than the specific tool. The configuration and custom command sections are Claude Code specific. If your team has standardised on a different tool, tell me which one and I will run the equivalent course for it.
Yes. Delivery is available in English or German. Course materials are provided in English by default, because that is the language of the tooling and its documentation, and can be provided in German on request.
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