What these tools actually do
- What building software with AI means when you have never written any
- The tools worth your time, and what each one is good at
- Where they fall over, told honestly and early
- What you can realistically expect to finish
Training course
Beginner
Tailored to your team
Vibe Coding Training
Build and ship a working tool without writing code, and without waiting for a developer to have time.
- Level
- Beginner
- Length
- 1 to 2 days
- Delivery
- On site, Remote, Hybrid
- Group size
- 5 to 20 participants
Booked privately for your team. Dates and length are agreed when you book.
What your team will be able to do
Every module ends with something participants can repeat on Monday morning, in your codebase and against your conventions.
Leave with something that runs
Take a real task from your own work and turn it into a tool a colleague can open.
Ask for what you actually want
Say what a thing should do precisely enough that the first attempt comes back close instead of wild.
Fix it when it comes back wrong
Read what went wrong, change one thing at a time, and get out of a loop of broken attempts.
Connect it to real information
Get your own spreadsheet, form or list into the thing so it stops being a demo.
Know when to stop
Recognise the point where a tool needs an engineer, and hand it over before it becomes a problem.
Put it in front of people
Publish it, collect what colleagues say about it, and decide whether it earns a second version.
Curriculum
Built around hands-on work rather than slides. The running order and the depth of each module are adjusted to the group before delivery.
80% hands-on
Saying what you want
- Cutting an idea down to something buildable today
- Describing the screens before describing the logic
- Why one instruction at a time beats a paragraph of them
- The handful of words that make the tool understand you
From blank page to working thing
- Getting the first version onto the screen
- Bringing your own list, sheet or form into it
- Letting the right people in and keeping everyone else out
- What to do when it keeps producing the same broken answer
Getting it used
- Putting it somewhere a colleague can reach
- Watching someone else use it without helping them
- The things you should not build this way at all
- What an engineer needs from you if they take it further
Built around your team
No two runs of this course are the same
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
Intake call
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
Stack review
Language, framework, review process, CI. Exercises are rebuilt against your repository so nothing in the room is hypothetical.
-
Step 3
Curriculum reshaped
Modules get dropped, deepened or added. You see the adjusted outline and sign it off before the date is fixed.
-
Step 4
Delivery and follow-up
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
- Depth of each module
- Your stack and repository
- Group size and seniority mix
- Length and how days are split
- English or German
- On site, remote or hybrid
Is this course right for your team?
Who it is for
What participants need beforehand
- No programming experience at all. The course assumes you have never written code and does not quietly expect otherwise.
- A laptop and an email address you can sign up to a tool with.
- One real task from your own week that you wish were a small tool.
How the training is delivered
Same material either way. The format changes how much of it lands in the first week.
On site
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.
Remote
Delivered live over video in focused blocks rather than one long day, with shared screens and hands-on exercises on your own work.
Hybrid
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.
Optional add-ons
Certificate of participation
There is no public schedule. Every course is booked privately for a single team, and we agree the dates together.
Your trainer
Luka Breitig
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.
- Ships production software every week
- Delivers in English and German
- On site across Europe, or remote
- Speaker at Nomad Summit, Chiang Mai
Questions about this course
The things teams ask before booking. If yours is not here, ask me directly.
Yes, and that is exactly who the course is designed around. There is no code to read and none to write. If your group does write code, the Claude Code course is the better booking.
The ones that turn a description into a running app, currently Lovable, Bolt and v0 among others. I pick the pairing that fits your group and your IT constraints, and the technique transfers when the tools change.
Genuinely usable for a small internal job with a handful of users. Not usable for anything holding customer data or money, and the course is explicit about where that line runs rather than leaving you to find it.
Covered in the room rather than left to chance: what these tools store, what should never be pasted into them, and how to check with your own IT before publishing anything. Bring your policy and we work against it.
It stays yours and it keeps running. The last module covers what to write down so an engineer can pick it up, which is usually what happens to the two or three tools that prove genuinely useful.
Five to twenty. People with no coding background get stuck on very different things, and each one is a short conversation that does not scale past twenty.
Still not sure whether this is the right fit for your team?
Book this training 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