Mark Nguyen
CEOPassionate trainer focused on helping professionals realise better opportunities in work and business.
The terminal tool everyone says you should be using, explained properly - and running on your own project by six
Some of the companies where our students come from
Running on your own machine, Mac or Windows, before the first break.
Ask for something, watch the files change, and know exactly what happened and why.
Throw away what it just did and get back to where you were, no harm done.
A plan you can read and argue with, before a single line of code gets written.

You see the actual gap - not clever prompting, but giving Claude your context and your own material to work on.

Set up around your own work, and running on it before the session is half over.

The two places Claude will mislead you, caught in seconds - so using it well and using it safely become one habit.

Three of your own jobs, packaged up to rerun next week, without starting from a blank chat.
There is a particular kind of frustration reserved for Claude Code. Everyone around you says it has changed how they work. You installed it once, opened a terminal, typed something, got a wall of text back, and quietly closed the window. Nobody was rude about it - nobody explained it either.
The problem is that the good introductions are written for people who already work in a terminal all day. They start three steps past where most people actually are, and they skip the two things that would make the whole thing feel safe: how to see what it just did, and how to undo it.
So that’s where this afternoon spends its time. We install it together, on both platforms, and nobody moves on until every screen has it working. We make a real change to a real project and then read it properly - what changed, why, whether you’d have done it that way. And we learn to throw all of it away cleanly, early, because being able to undo is what makes people willing to be bold.
After that the two habits that matter: getting a plan you can argue with before any code gets written, and giving Claude the standing context about your project so you stop re-explaining it every time. Then an honest block on it going wrong - what a wrong path looks like early, and what to do about it.
It’s deliberately small. When the install fails on your machine and not on anyone else’s, somebody needs to look at your actual screen - which is the whole reason to do this live rather than watching a video at 1.5×.
A beginners' session that doesn't spend two hours on theory. The running order below is UK time; the session times at the top of the page are shown in yours.
What everyone works on, and what they'd like to change about it. If you haven't got a project, we'll get you one - nobody sits this out.
Mac and Windows, side by side, including the two things that go wrong most often. We don't move on until every screen in the room has it running.
Point it at the project, ask for something small, and watch what happens. Then read the change: what it edited, why, and whether you'd have done it that way.
Coffee, stand up, look out of a window. Back at twenty past.
Throwing work away cleanly, keeping what's good, and never being one wrong instruction from a mess. This block is what lets you be bold for the rest of the afternoon.
Getting a written plan before any code, and writing the project file that stops you re-explaining your setup in every new session. We build yours on the day.
Spotting a wrong path early, stopping it, and getting back on track. Plus the honest limits - the jobs it's bad at, and how to recognise one before you've lost an hour.
What to try first on your own, and the one habit worth keeping from today.
Details, agenda and timing subject to change.
It has your joining details, your receipt and a calendar invite, ready to add straight away.
Everything installed and ready before the day, so no session time is lost to downloads. You and your fellow students start straight on real work.
Our instructors show you how to use Claude, drawn from their own experience in industry. Then you do the real work, and leave with workflows you can use the very next morning.
Need to move to another date, or can't make it any more? Reply to your confirmation email and we'll sort it. You can cancel up to 21 days before the workshop and we'll refund you in full.
Book 3 seats or more for this same date and the discount is applied automatically at checkout below. No code, no separate invoice.
Run this session privately, tailored to your stack and your own material, remote or on-site.
Explore team training
Passionate trainer focused on helping professionals realise better opportunities in work and business.
Leads curriculum design and workshop delivery at Atlas Learn. Formerly an educator and trainer, specialising in breaking down complex technical concepts into accessible, hands-on learning paths.
Three hours, a small group, and Claude Code running on your own machine by the end of the first half hour. Change your mind? Cancel up to 21 days before and we'll refund you in full.
We'd like to set analytics and advertising cookies to see how this site is used and which ads bring people here. Nothing is loaded until you say yes. See our privacy policy.