Most developers already have Claude Code installed by the time they take a course like this. What they usually do not have is a repeatable loop. They prompt, they get a 400-line diff, they spot-check it, they merge, and the reviewer inherits the problem. First-week Claude Code usage tends to produce more reviewer work than it saves.
This course replaces that pattern with a plan-first loop:
It is the minimum viable habit for someone about to do real work with an agent on a real codebase.
Course objectives
Target audienceDevelopers and senior developers joining a team that has standardized on Claude Code, or evaluating it seriously for the first time. Engineering managers who want to understand the loop their team is about to adopt are welcome, but this is a hands-on day with real labs.
Prerequisites
Important informationEvery participant takes a 10-minute online self-assessment before the course. It checks what they already use:
It also checks how they currently handle planning and verification, and what their review process looks like. The assessment routes them to the right track and flags obvious gaps.
Why this matters to our customers:
That lets day one open with "here is what this room already knows and where the shared gaps are" instead of generic material.
Every participant leaves with a versioned template pack checked into a real repository they can open on Monday. The pack is not a slideware deliverable. It is a working set of 10 to 20 files such as:
The pack is co-authored during the course. Participants do not receive it as a gift at the end. They build it, review each other's entries, and commit it. That is what makes it stick. If nobody has owned a particular file by the end of the day, it does not go in the pack.
Two weeks after delivery, the instructor runs a one-hour follow-up with the cohort. The agenda is fixed:
The follow-up is included in the course price. Without it, most of the value walks out the door inside a month.

We open with the reason most people under-deliver with Claude Code in week one: no plan, no spec, no verification. Short live walkthrough of the weak version of the loop and the strong version, on the same ticket, side by side.
Structure, conventions, hot files, existing patterns. How to spend five minutes on the repo so the agent spends forty minutes doing the right thing.
Lab:
Turning a ticket into constraints and acceptance criteria. Comparing weak prompts to spec-driven prompts on the same task.
Lab:
Using plan mode to force a design conversation before any file is touched. Rejecting and resetting when the plan drifts. Keeping each change small enough that a reviewer can reason about it in under ten minutes.
Lab:
The moment a developer writes the same spec twice, it should be a slash command. We introduce slash commands as the bridge from ad-hoc prompting to named, reviewable, version-controlled workflows.
Lab:
Running tests, checking assumptions, reading the diff the reviewer will read. Debugging with a hypothesis instead of re-prompting.
Lab:
We close the day with the delegate, review, own decision model: which tasks go to Claude Code, which get reviewed carefully, and which stay human end to end.

Duration: 1 day
Price: 10 900 NOK
Language: English
Format: Instructor-led classroom training with hands-on exercises
Hva er Claude Code Beginners?
Claude Code Beginners er et introduksjonskurs som gir deg en praktisk innføring i Claude Code og hvordan du kan bruke det til å jobbe med kode og automatisere oppgaver.
Trenger jeg erfaring med AI eller LLM-er?
Nei, men du bør ha erfaring som utvikler og grunnleggende forståelse for programmering.
Er kurset praktisk rettet?
Ja, kurset er hands-on og inneholder øvelser og praktiske eksempler gjennom hele opplæringen.
Hva lærer jeg i løpet av kurset?
Du lærer blant annet å bruke Claude Code til å utforske kode, jobbe med kontekst og minne, bruke kommandoer og bygge enkle agentbaserte arbeidsflyter.
Hvem passer kurset for?
Kurset passer for utviklere og tekniske roller som ønsker å komme i gang med AI-assistert utvikling og agentbaserte verktøy.
