We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
A course for teams who have had Copilot for a year and still use it as autocomplete: the surfaces nobody opened, its part in the pull request, and the controls the organisation never configured.
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.
Get more out of inline suggestions by shaping what the code around the cursor tells the model.
Use chat for the questions it answers well, and recognise the ones it will answer confidently and wrongly.
Run one instruction across a set of files with the edit and agent surfaces instead of repeating yourself in each of them.
Put Copilot to work in the pull request without letting its summary stand in for an actual read of the diff.
Configure content exclusion, policy and the public code filter so the tool matches what your organisation has actually agreed to.
Gather the kind of evidence a sceptical finance director would accept about whether the seats are worth renewing.
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
Everything Copilot does that is not the grey text at the end of the line. The day most teams should have run a year ago.
2 days
Adds its part in the pull request, and the policy controls an organisation wants settled before it widens access any further.
4 days
Adds the rollout work: shared instruction files, extensions, seat management, and evidence that the licences are earning what they cost.
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.
That is exactly the room this course is built for. Teams who have had it for a year are usually still living in one of its four surfaces, and the day is mostly spent on the other three. If your team is genuinely fluent across all of them, say so and I will suggest a different course rather than sell you this one.
Yes, an active seat each on the day. In most organisations booking this course the seats already exist, which is usually why the course is being booked at all. If some participants are unlicensed, tell me the split and I will pair them with somebody who is.
Yes, and it is worth doing with your administrator in the room. Content exclusion, the public code filter and audit logging are settings somebody has to own, and the usual state is that nobody has looked at them since the rollout. Bring the administrator and the decisions get made on the day.
Yes, wherever your policy allows it. Copilot's behaviour depends heavily on what surrounds the cursor, so a real repository with real conventions is where the exercises land. If content exclusion blocks parts of it, that is a far better thing to discover in a workshop than in production.
If Copilot is what everybody has today, yes, because those seats are already paid for either way. If the evaluation is genuinely open, the tool-agnostic course is the better use of the day: that one is built around choosing, and this one is built around getting more out of a choice already made.
Five to twenty-five. The policy and pull request material works well with a larger room, the hands-on editor work does not, so above fifteen I split the day so the practical parts run in pairs.
Yes, the session runs in German or English as you prefer. Copilot's own interface is English either way, so materials stay English by default to match what participants see on screen, with a German version 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