Engineer and founder
6 years as co-founder and CTO
Tymeslot and In A Nutshell, my own products
We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
I train your engineers on your own repositories to hand whole tickets to Claude Code, Cursor, Codex or Copilot. Same headcount, more shipped.
Output stays where it was until the team learns to hand whole tasks to agents. Then the same engineers can double what they ship.
Agents take six kinds of routine work off an engineer's week, and the hours they free go into shipping features.
Illustration: in an engineer's week with agents, the six kinds of work below take up far less of the week, and the time freed up goes into shipping more.
The team you have, shipping more each sprint.
Every exercise runs on your repositories, and I adapt the topics to your stack.
Hand an agent a whole ticket with its context, and keep several of them running while you review.
Repeats until the tests pass
Agents that read your tracker, docs and databases
Several agents, one engineer reviewing
Review and test habits that keep up with agent output
From a few enthusiasts to the whole team
Briefing leadership too? AI training for leadership teams
Engineers listen to someone who ships code. Habits change with someone who knows why they formed.
6 years as co-founder and CTO
Tymeslot and In A Nutshell, my own products
Top 2% nationally, in a master's in management
BSc Psychology
From engineering teams I trained to work with AI agents.
From first call to agents doing real work on your codebase.
01
You tell me about your stack and your backlog, and we look at how much agents can take on.
02
I rework the course around your repositories and real tickets your team has queued.
03
On site or remote, your team ends the training with agents already closing real tickets.
04
Once your team has worked with the agents for a while, you can book follow-up sessions.
Booked by a company for one engineering team, run on its own codebase.
A good fit
Not a fit
Nine quick questions, about three minutes, on setup, adoption, integration and results. You get a score for each area and the next step that fits where your team stands.
Pick the tool your team already pays for, or start with AI Coding Training to choose one. I rebuild every booking around your stack.
Ship real features with Claude Code: steer it with project instructions, keep its diffs reviewable, and set guardrails that hold up in a production codebase.
Make your team fluent in Cursor: which mode to reach for, how to teach it your conventions, and how to keep a twelve-file change reviewable.
Move a team past tab completion into Copilot's chat and agent surfaces, its role in code review, and the enterprise controls around all of it.
Hand engineering work over to Codex and get it back finished: task briefs, parallel runs, environment setup, and reviewing a change nobody watched being written.
Choose one AI coding tool for the team, agree how everyone uses it, and run a rollout that shows the gain in output.
Build agents that run real workflows in production, with the tools, tests and guardrails that keep them reliable.
Build a working MCP server against your own systems, from the protocol up to auth and distribution.
Run language models on your own infrastructure and serve them to the whole team, with the data staying inside the building.
The ones that usually come up before a booking.
GitHub Copilot made its name with autocomplete, suggesting the next few lines as you type. In agentic coding you describe a goal, and an agent plans the approach, reads your codebase, writes code across several files, runs the tests and iterates on errors. Claude Code works this way, and so do the agent modes now built into Copilot, Cursor and Codex. For a team, that means scale, because one engineer can direct several pieces of work at once.
Doubling is the target the training is built around, and how close a team gets depends on its backlog. The gain comes from work an agent can carry end to end: well-specified features, tests, migrations, first-pass reviews and bug reproduction. A team whose backlog is full of that work gets closest; a team that mostly does research or architecture gains less. Tell me about your backlog and we can work out where your team sits.
Prompt engineering is the smallest part of it. The topics that matter now are agentic workflows with tools like Claude Code, running work in parallel with subagents, MCP integrations that connect agents to internal tools, AI-assisted code review, and finding your way round unfamiliar codebases. It should also cover how review and testing keep up once agents write more of the code, and run on the team's own codebase, so participants apply it the next morning.
Look for a trainer who ships production software with these tools every day. Claude Code is my main development environment, for client work and for my own products such as Tymeslot, an open-source scheduling platform. The exercises come from that work, including where agents fail and how to recover. Cegos Integrata, NobleProg and Code First Girls book me for exactly that.
Yes. I deliver every workshop in German (native) or English (fluent), and in bilingual teams participants can ask questions in either language. The exercises run on your team's own codebase and tools, so each one is a task from your team's own week. I run it remotely, on site at your offices, or as a mix of both.
I am happy to sign an NDA. Claude Code and similar agents send prompts and the code they read to the model provider, under the data terms of your plan. If code has to stay in your own cloud or under stricter terms, we can run Claude Code through Amazon Bedrock or Google Vertex AI, or with zero data retention. For code that cannot be used in the training at all, I bring a comparable practice repository.
Each participant needs working access on the day to the tool the course uses. It is worth arranging this a week ahead.
Between 5 and 30, depending on the course. Above about fifteen, I pair people up for the practical parts.
It depends on several things: the course, the size of the team, how long it runs, on site or remote, and how much preparation your codebase and tools need. Tell me about your team and we'll work out an offer that makes sense for both sides. You get the price in writing before anything is booked.
Your team keeps everything we set up during the training, including instruction files such as CLAUDE.md, agent settings and prompt libraries. Once the team has worked with the agents for a while, you can book follow-up sessions.
Something else on your mind?
Tell me about your stack and your team, and I'll tell you which work agents can carry and which course fits. A few lines are enough.
I reply myself, usually within a day. In English or German, on site or remote.
Articles on how agents work, for anyone deciding where to use them
Users turned Bild.de's public chatbot against its own brand. I walk through the prompt-injection defences that keep a public chatbot working for you.
The same approach, built around different work.
Build no-code agents for research, drafts and reports, and publish more with the same team. No technical background needed.
See marketing trainingDecide where agents pay off, how to roll them out and how to measure the gain.
See leadership trainingOne-on-one coaching on your own work: six weeks to build the habit, or a single session any time.
See one-on-one coaching
Companies and training providers I have worked with
I deliver AI training for organisations and L&D providers.
Cegos Integrata
Commissioned trainer for Cegos Integrata
NobleProg
AI coding workshops via an IT training provider active in 50+ countries
Innomotics
In-house AI training for engineering teams
financial.com
In-house Cursor training for the engineering team
Digitality Agency
Training for the design team in using LLMs for coding work
Bots & People
Commissioned trainer for developer workshops
Code First Girls
Course creator: a 3-month curriculum on AI and agentic tools
Nomad Summit
Conference speaker on AI tools, agentic development and developer workflows (2025)
Vertiv
On-site workshops in AI-assisted coding for engineering teams
Deutsche Telekom
Hands-on AI coding training for enterprise engineering teams