How we actually use AI in our training

Every training provider now claims to be "AI-powered". Most of them mean they put a chatbot in the corner of the page. We want to be specific about what ours does, because the difference matters to what you will learn.

What the assistant is for

Our study assistant is scoped to the course you are enrolled on. It knows the module you are in, the lesson you are reading, and what the curriculum expects you to be able to do by the end of the week. When you ask it something, it answers against that context.

It is good at three things:

• Explaining the same concept a second and third way, at 1am, without getting tired of you
• Reading your code and telling you where your mental model diverged from what the machine is doing
• Generating practice problems at the exact difficulty you are stuck on

What the assistant will not do

It will not write your assignment. This is a deliberate constraint, not a limitation we are working around. When you ask it to produce the solution, it will ask you what you have tried and walk you toward it instead.

We are strict about this because the failure mode is well documented: learners who let a model write their code report high confidence and fail technical interviews. The typing is not the part you are paying to learn.

Where the human comes in

Your mentor does the things a model cannot: reading your pull request in the context of your career, deciding what to skip because it does not matter for the job you want, and telling you honestly when work is not good enough yet. The assistant handles volume. The mentor handles judgement.

What we teach about AI itself

We also teach the tools directly, because you will be expected to use them at work. The AI-Assisted Engineering course covers writing specifications a model can act on, reviewing generated code critically, and building against the API yourself. Understanding the tool is different from depending on it.