Where Claude Code tokens go, and what is safe to cut
Before you trim Claude Code's output to save tokens, check what you'll lose. This article looks at compaction, memory and the cost of checking the result.
Read the article
Use AI.
Trust your work.
Live, practical training from San Digital for software engineers and people who work in documents and data.
£495 including VAT per place.Four live 40-minute sessions.
Two courses
Engineering
AI-Assisted Engineering. For engineers with two months to two decades of experience who use AI coding tools. Four live 40-minute sessions of repository work in Python, with TypeScript, C# and Rust variants for selected sessions, reviewed on the change you would merge and the tests that were run. £495 including VAT per place.
See the engineering courseBusiness
AI-Assisted Knowledge Work. For analysts, marketing, operations, HR, finance and product people who produce work with an AI assistant. Four live 40-minute sessions on realistic document packs, with no coding, using the assistant you already use. £495 including VAT per place.
See the business courseThe four sessions
Each of the four sessions teaches one operating rule, then moves into a prepared, realistic task. Engineering cohorts work in code, while business cohorts work in documents, data and messages.
-
1
Review a change that already looks finished
Engineering: A supplied code change passes every check it ships with. You still have to review it.
Business: An assistant has written a polished client briefing. Work out how much of it can safely be said. -
2
Write the definition before anything is produced
Engineering: Turn a one-line ticket into criteria a test could pass or fail, before implementation starts.
Business: Before anything gets produced, pin a one-line request down into a written definition. -
3
Keep each delegated step small enough to check
Engineering: Ship a change in steps small enough that each one gets a proper review.
Business: A customer pack, built stage by stage, with each stage checked against the data. -
4
Correct your first explanation
Engineering: Investigate a fault and use what you find to decide whether your first diagnosis holds up.
Business: Check a summary that has already been sent, then explain what needs correcting and why.
Feedback from the first cohort
Two of the engineers on our first course (July and August 2026) agreed to share their feedback. You can read their full comments on the engineering course page.
The hands-on repository exercises, live tutor feedback, and support for multiple programming languages make the learning immediately applicable. It’s a thoughtful, credible course that promotes responsible engineering judgment, not simply faster code generation.
Camila CotaEngineering course, September 2026Before the course, I mainly focused on solving the technical problem. Now I ask better questions, think more like a product owner, and look for evidence first. I learned to check test cases, reproduce issues, keep logs, and make small, meaningful commits. This has made my development process more structured and reliable.
Sujal NeupaneEngineering course, September 2026Price and dates
Both courses cost £495 including VAT per place.
Dates for both courses are sent to the waiting list first. Tell us which course interests you when you join.
Public places and private cohorts
Individual place
Join the waiting list to hear the dates for either course first.
Get the next course datesPrivate course
Give your team a shared way to verify AI-assisted changes and own the software it delivers, or run the business course for the people who work in documents and data.
Discuss private team trainingLatest articles
A checklist for reviewing AI-generated code
A five-step checklist for the next AI-authored change you're asked to merge.
Read the article
Questions about the courses
How much does it cost?
Both courses cost £495 including VAT per place.
When does it run?
Candidate times are published when booking opens. Dates go to the waiting list first.
What if I cannot make a time?
When booking opens, tick every offered time that works. We confirm one of those times by email. And if none of the times you selected runs, you can transfer, or we refund you in full.
How do I pay?
When booking opens, you'll be able to choose card or invoice. After you've paid, look out for our acceptance email: that is what confirms your place.
Can I book for several people?
You can request up to five places. Check with the others before ticking times, as everyone needs to be able to attend the same sessions. For six or more, ask about a private course.
What if I need a refund?
You receive a full refund if the course is full, no time you selected runs, or you withdraw before we accept your booking. After acceptance, our cancellation terms include a full refund at least 14 days before the first session and a 50% refund 7 to 13 days before it. Your statutory rights are not reduced. Read the booking terms.
Which course should I choose?
Pick the engineering course if most of your AI work is code. For reports, spreadsheets and other office work, take the business course. You'll learn the same four rules through different exercises.
Do I need a technical background for the business course?
No. The business course needs ordinary office-software fluency and access to a mainstream AI assistant such as Microsoft 365 Copilot, ChatGPT, Gemini or Claude. There is no coding.
What do I need?
For the engineering course: a computer that can run one of the supported exercise variants, and an AI coding tool. The business course asks for less, just your usual office tools and an AI assistant. Whichever course you pick, you will need a current browser and a stable connection for the four live sessions.
Are sessions recorded?
No. The live sessions are not recorded and automatic AI summaries are off, on both courses. Read the privacy notice.
Join a course
Joining a waiting list is free and does not commit you to a booking.