tom

Speaking

A course is judged by what it refuses to teach. A system, by what it refuses to add.

I've spent thirteen years in front of rooms — classrooms, bootcamps, engineering teams — and I'm now building a training program for engineers at a cloud company. I talk about the part of teaching nobody prepares you for: deciding what to leave out, and holding a room when your plan stops helping.

Talks

What a Good Course Refuses to Teach

Most failed trainings suffer from the same thing: too much content. Not because the trainer knew too much, but because nobody ever asked them to decide what mattered. I walk through real courses — Docker, design patterns — and show the decisions behind them: what I cut, what I kept, and why the order matters more than the list. For anyone who has to explain their work to someone else: mentors, tech leads, and yes, trainers.

30–40 min · also works as a 15-min short

You Can't Train a Trainer With a Slide Deck

Handing someone your slides doesn't make them a trainer — it makes them a narrator. Three levels of what "train the trainer" can mean: content, methodology, and the one almost nobody works on — posture, what you do when the room goes quiet and you can't tell whether they're thinking or lost. Drawn from building a training program for engineers, including the parts I haven't solved yet.

30–40 min

Previously

AWS Summit Paris

Two Datadog partner sessions on the main program — a log strategy that lets you sleep, and shipping features on Datadog Apps.

DevOps D-Day

Conference talk. Watch ↗

The Product Crew

Guest, on building and teaching. Watch ↗

training-dev.fr

Interview on training developers. Watch ↗

Le Joboscope — OpenClassrooms

Podcast episode. Listen ↗

Ironhack

Talks on how developers actually get hired.

Practical

I speak in French and English. Based in Paris, happy to travel.

Conferences, meetups, internal engineering sessions, podcasts.

Tell me the audience and I'll tell you honestly whether I'm the right person.