We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
A course for organisations deciding how they will code with AI rather than which button to press: what genuinely separates the tools, what transfers between them, and how to roll one out across a team that will not all agree.
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.
Pick a tool against criteria you wrote down first, and still be able to explain the choice six months later.
See where the tools genuinely differ, and where the marketing is describing a feature every one of them has.
Identify the practices that survive a change of vendor, which turn out to be most of what makes a team faster.
Leave with the conventions your team will follow, written in a form somebody will actually read.
Design a trial that produces a decision instead of an inconclusive month and a renewal by default.
Agree what will count as evidence before the rollout, so that nobody has to argue about it afterwards.
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
An honest map of the tools, and the practices that hold whichever one you pick. The day to run before anybody signs a contract.
2 days
Adds a structured evaluation, and the conventions a team needs when its members do not all use the same tool.
4 days
Adds the rollout itself: the pilot, the policy, the enablement plan, and the numbers you will judge all of it by.
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.
Claude Code, Cursor, GitHub Copilot and Codex in depth, with the rest of the field covered by category rather than by name. The list is reviewed before every delivery, because a course on this subject that reused last year's slides would defeat its own purpose.
I have no reseller relationship with any of these vendors and no commission on what you choose, which is the only kind of neutrality worth claiming. What I do have is opinions from using all four in production, and you get those clearly labelled as opinions rather than presented as findings.
The evaluation module is, and I would drop it. The rest is not: the shared practices, the review standard and the rollout plan are what decide whether a chosen tool changes anything, and they are exactly the parts organisations skip. In that case a tool-specific course plus this one's second half is usually the better shape.
Those make a team good at a tool. This one decides which tool, and how the organisation will work with it. There is deliberately little keyboard time here and a great deal of comparing, deciding and writing things down, so booking both makes sense and booking this one as a substitute does not.
Five to thirty, and the mix matters rather more than the number. The day works best with the people who will make the decision and the people who will live with it in the same room, which usually means leads and senior engineers together.
English or German. This is the one course where German materials are the default rather than the exception, because most of the day is discussion and decision-making rather than reading output from a tool.
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