Choosing a provider
Vibe coding training: how to choose
Learning vibe coding means two very different things depending on who is selling: learning to make a model produce code, or learning not to ship what it produces. The second is the one that is missing.
What we are talking about
Vibe coding means describing an intent and letting a model write the code, without reviewing every line. It is remarkably effective for exploring an idea, prototyping a screen, testing a hypothesis in an hour instead of a day. The term comes from Andrej Karpathy and describes a way of working, not a job title.
It gets complicated when you want to keep what was produced. A prototype built without review has no tests, no error handling, no data model built to last, and nobody on the team can explain why it works. So the skill that matters is not prompting, it is knowing when to switch from exploring to specifying.
That is the criterion separating useful training from the rest. Plenty teach you to generate fast. Few teach you when to stop.
Kinds of provider
School or bootcamp
- Good for
- Starting from nothing with no technical background, with a long track, a framework and a cohort moving at the same pace.
- Where it breaks down
- Fitting your context. The curriculum is built for a whole cohort, so never on your repository or your constraints.
- Billing
- Tuition, often several thousand euros.
Certified training body
- Good for
- Funding. Certification opens up employer-scheme coverage, which changes everything when the budget is not yours.
- Where it breaks down
- Freshness. A catalogue programme is written then approved, and on a subject moving every quarter it is often a year behind.
- Billing
- Price per trainee per day, eligible for funding.
Online course
- Good for
- Cost and pace. A few tens of euros, available immediately, and you can come back to it.
- Where it breaks down
- Putting it into practice. Nobody looks at what you write, so bad habits picked up during the course are never corrected.
- Billing
- One-off purchase or monthly subscription.
Team workshop on your repository
- Good for
- Leaving with written conventions that hold: where exploring is allowed, what must be specified, what never gets a light review.
- Where it breaks down
- Fundamentals. Half a day does not replace learning the craft, it assumes a team that already codes.
- Billing
- Fixed price for the group, not per person.
Guided self-teaching
- Good for
- Costing nothing. Vendor documentation is good and current, which is rare.
- Where it breaks down
- The blind spot. You cannot learn what you do not know you are missing, and that is exactly where incidents come from.
- Billing
- Free, apart from the time spent.
What actually decides
- 01
Which code you work on
Ask whether the session runs on your repository or on a sample project. A toy project has no debt, no house conventions, no inherited tests, so it raises none of the questions that will actually block you.
- 02
What remains afterwards
A slide deck does not survive the week. What survives is a project instruction file, a permission policy and a written rule on what gets read line by line. Ask to see the deliverable before paying.
- 03
Who runs it
Someone who has shipped an agent to production knows where it breaks. Someone who has read the documentation will give you a decent overview and nothing more. Ask directly, and the answer is audible immediately.
- 04
The cost of the tools
Training that never mentions subscriptions and quotas leaves you to discover the bill on your own. Tiers run from $0 to $200 a month per person depending on the tool, and that gets decided before training the team, not after.
- 05
Funding
If you are counting on employer-scheme funding, check certification before anything else. Without it there is no funding, and that single criterion rules out some providers whatever their level.
Warning signs
- A session that never touches your repository
- A programme that mentions neither code review nor tests
- Productivity gains quoted with no measurement method
- No mention of subscription cost or quotas
- A trainer who has never shipped an agent to production
- The promise of doing without developers
Where we sit
Our vibe coding workshop runs for half a day, on your repository, and aims at one thing: knowing where exploring pays and where it turns dangerous. You leave with a project instruction file, a permission policy and the switching rule written down.
Two neighbouring workshops sit in the catalogue, one on Claude Code in a team and one on Codex and coding agents in production. They are three faces of the same subject, and the choice follows the tool your team already uses rather than a curriculum.
When we are not the right choice
- We are not a certified training body. If your budget goes through an employer scheme, you need one that is, and that criterion outranks everything else.
- If nobody on the team codes, the workshop comes too early. It assumes people who can read a code review, not people discovering programming.
- If you are after a diploma or a recognised certification, take a school. A workshop leaves conventions, not a qualification.
- If you want to train forty people, the format does not scale. We work with groups of four to twelve so everyone has hands on the keyboard.
Our ranges
- Vibe coding workshopfrom €900Half a day on your repository, group of 4 to 12, written conventions delivered.
- Claude Code or Codex workshopfrom €900Same format, centred on the tool your team already uses.
Excl. VAT, France. Monthly running cost is always costed separately from the build.
Frequently asked
- How do you learn vibe coding?
- By starting on a low-stakes project, to feel what the model produces quickly and well. The part that genuinely needs guidance comes later: deciding when to stop exploring and switch back to specified work, because that is where production incidents come from.
- What is the best vibe coding training?
- It depends where you start. With no technical background, a school or an online course. With a team that already codes, a workshop on your own repository will help more, because the hard questions come from your existing code and not from a sample project.
- How long does it take to get going?
- Producing something that works takes an hour. Knowing what to keep takes longer, because it requires having seen at least one prototype reach production and cause trouble. Half a day of guidance saves that detour.
- Does vibe coding replace developers?
- No, and any training promising otherwise should be ruled out. It moves the effort: less time writing, far more deciding what to check and what to throw away. That work takes experience, not less of it.
- Is the training eligible for funding?
- Not with us: the workshop is not backed by a training certification, so it does not go through an employer scheme. If funding decides your project, go to a certified body, that criterion comes first.
Going further
Scope your first AI agent
20 minutes to review your tools, data and the first useful case. No jargon, no commitment.