Click to Career

From clicking buttons to a real engineering job.

The bootcamp for the adult who can use a phone and a browser and nothing else. Thirty-two chapters take you from naming the four parts of a computer to shipping a full-stack TypeScript app and clearing the interview pipeline at a junior AI-engineer role. One gated assignment closes every chapter.

Start chapter 0See the syllabus

If any of this sounds familiar

You opened the editor.
You closed it again.

  • You’ve heard the words “Git”, “React”, and “API” and you couldn’t say what any of them are without bluffing.
  • The last tutorial you finished felt great in the moment and you couldn’t reproduce one line of it the next day.
  • Every YouTube intro promises six weeks to a job and the comments are all from people six months in, still stuck on lesson three.
  • You think you might be too old, too non-technical, or too late. You aren’t. The fear is the first thing the course dismantles.
  • The terminal still feels like a hostile room you walked into by mistake.

None of that is a sign you can’t do this. It’s a sign every course you’ve tried skipped the part where the language gets translated for someone who’d only ever clicked. This one doesn’t.

What you walk away with

A working engineer, not a graduate of another course.

  • Ch 10–29

    A full-stack TypeScript app you built, tested, deployed, and own

  • Ch 8, 21, 27

    The vocabulary to read an unfamiliar codebase and ship a change

  • Ch 19

    Tests that catch the regression before a user does

  • Ch 20

    A debugging loop you trust instead of guessing

  • Ch 22–23

    A local LLM in your editor and Claude Code for the larger work

  • Ch 29

    A portfolio capstone you take to every interview

  • Ch 30

    A resume, GitHub, and pipeline that actually return offers

  • Ch 31

    A playbook for the first ninety days on the job

The bar isn’t “you finished the course.” The bar is you walk into the first ninety days and aren’t the person everyone has to babysit. Every chapter is cut down until it only contains what serves that.

The arc

Ten blocks. One direction.

Every block depends on the one before it. You don’t skip the terminal to get to React. You don’t skip databases to get to deploys. The order is the lesson.

  1. Block 1

    Foundations

    Ch 0–3

    Your computer, how software runs, the terminal, how the internet works. The vocabulary every later chapter assumes.

  2. Block 2

    Web fundamentals

    Ch 4–7

    HTML, CSS, JavaScript, the DOM. The three languages a browser actually runs, in the order it reads them.

  3. Block 3

    Engineering hygiene

    Ch 8–9

    Git and GitHub. Modern JS and TypeScript. The discipline that lets you change code without losing it.

  4. Block 4

    Frontend

    Ch 10–13

    React, the patterns that trip every beginner, Next.js, forms with real validation and accessibility.

  5. Block 5

    Backend

    Ch 14–18

    Node and Express, NestJS, Postgres and Prisma, auth done right, APIs beyond REST.

  6. Block 6

    Engineering quality

    Ch 19–21

    Testing the pyramid honestly, debugging as a learnable loop, refactoring you can defend.

  7. Block 7

    AI tooling

    Ch 22–23

    Local AI in VSCode for everyday work. Claude Code and the harness for spec-shaped work.

  8. Block 8

    Production reality

    Ch 24–26

    Deploying, observability and security, performance and scale. The skills that come after the code runs locally.

  9. Block 9

    Career foundations

    Ch 27–29

    Working as an engineer, staying current, and the capstone you take to interviews.

  10. Block 10

    Getting hired

    Ch 30–31

    Interview prep, then the first ninety days on the job. The chapters that turn the work into an offer.

The unit shape

Every unit, the same six beats.

You read the same shape every time. By the third unit, your brain knows what’s coming. The shape is the contract.

  1. 1. The promise.One paragraph. What you’ll be able to do at the end of this unit that you couldn’t at the start.
  2. 2. The mental model. Plain English with one concrete real-world analogy. A diagram if a picture works better than prose.
  3. 3. You do it, with me. Step-by-step. Screenshots for every UI step. A code block for every command. You do the work on your own machine.
  4. 4. What you should be seeing. The expected state at this point. If your screen doesn’t match, you stop and fix it.
  5. 5. Common stumbles. The two-to-four things that go wrong, named, with the fix for each. Drawn from people getting it wrong, not invented.
  6. 6. You should know. A short checklist of what you now understand. The chapter assignment composes from these.

Short, do-shaped units. The chapter-end assignment is longer and graded against a green/yellow/red rubric you score yourself.

Syllabus

32 chapters · 541 units

Chapter 0 is fully free. Every other chapter’s orientation unit is free. That’s 47open units — enough to skim before deciding to unlock.

Block 1

Foundations

Ch 0–3
Ch 0Your computerFoundation16 units

The chapter that closes the gap between 'I use a computer' and 'I can talk about a computer.' Files, paths, hidden files, permissions, keyboard fluency, browser dev tools.

Ch 1How software actually runsMedium12 units

Source vs binary, compile vs interpret, runtimes, processes, memory. Why 'works on my machine' happens. The mental model every other chapter relies on.

Ch 2The terminalMedium16 units

The shell, the prompt, and twenty commands you'll use forever. Pipes, redirection, env vars, PATH. Bash and PowerShell side by side.

Ch 3How the internet worksPEAK16 units

A packet's life from your browser to a server in another country. DNS, TCP, HTTP, HTTPS, headers, CDNs. The network tab as your first inspection tool.

Block 2

Web fundamentals

Ch 4–7
Ch 4HTMLMedium17 units

The file the server returns. Tags, structure, semantics, forms, accessibility — the structure layer before any styling lands.

Ch 5CSSMedium18 units

The look layer. Selectors, the cascade, the box model, flexbox, grid, responsive, custom properties, and the Tailwind subset that earns its weight.

Ch 6JavaScript, the languagePEAK22 units

Types, scope, closures, modules, and the event loop. Promises and async/await. The language itself, separate from where it runs.

Ch 7The DOM and the browserMedium16 units

JavaScript controlling a web page. Events, delegation, storage, CORS, and the browser as a security boundary.

Block 3

Engineering hygiene

Ch 8–9
Ch 8Git and GitHubPEAK19 units

Three trees, branches, rebase vs merge, PRs as a social artifact, conflicts as a routine event. The discipline that lets you change code without losing it.

Ch 9Modern JavaScript and TypeScriptMedium17 units

Types are descriptions, not enforcement. Narrowing, generics, unknown vs any vs never. The tool that catches errors before they reach a user.

Block 4

Frontend

Ch 10–13
Ch 10React fundamentalsPEAK16 units

Components, props, state, re-renders, lists, forms, lifting state. The mental model first, the library second.

Ch 11React patterns and pitfallsMedium16 units

useEffect traps, custom hooks, memoisation honestly, context, suspense. Server state vs client state, and why TanStack Query is the right answer for fetched data.

Ch 12Next.jsPEAK17 units

App Router, server components, server actions, route handlers, deploying to Vercel. The frontend that ships to production.

Ch 13Forms, validation, accessibilityMedium16 units

Where your app meets reality. React Hook Form, Zod, ARIA without cargo-cult, keyboard navigation, screen-reader testing.

Block 5

Backend

Ch 14–18
Ch 14Node.js and the backend mental modelMedium18 units

A server is a program that waits for HTTP requests. Express, middleware, env vars, errors, CRUD from scratch.

Ch 15NestJSPEAK19 units

Modules, controllers, services, DI, DTOs, guards, interceptors, pipes. The structure that lets a backend grow past the toy.

Ch 16DatabasesPEAK19 units

Data outlives code. SQL, Postgres, schemas, relations, indexes, normalisation, Prisma, migrations, the N+1 problem.

Ch 17AuthPEAK18 units

Sessions vs JWT, password hashing, OAuth, magic links, RBAC, CSRF and XSS in auth contexts. The chapter where security stops being someone else's job.

Ch 18APIs beyond RESTMedium16 units

REST in detail, GraphQL, tRPC, WebSockets, webhooks, idempotency, rate limiting. The protocols you'll see at real companies.

Block 6

Engineering quality

Ch 19–21
Ch 19TestingPEAK17 units

The pyramid honestly, Vitest, integration, Playwright, mocking, CI. The skill that lets you change code without breaking it.

Ch 20DebuggingPEAK17 units

Hypothesis → experiment → observe → update. Stack traces, dev tools end to end, the VSCode debugger, git bisect. The skill nobody teaches.

Ch 21RefactoringMedium16 units

Named smells, extract function/module, refactoring under and without tests, strangler-fig. Reading large unfamiliar code without panicking.

Block 7

AI tooling

Ch 22–23
Ch 22Local AI in VSCodeMedium17 units

Self-contained AI in your editor. Ollama, Continue.dev, the model landscape, quantisation. When local is enough, when you reach for a frontier model.

Ch 23Claude Code and the harnessPEAK17 units

The CLI loop, /commands, skills, hooks, memory, subagents, plan mode, loop mode. Writing specs, not snippets.

Block 8

Production reality

Ch 24–26
Ch 24DeployingMedium17 units

Vercel, Railway, Fly, Cloudflare. CI/CD with GitHub Actions. Preview deploys, rollbacks, migrations in CI. The pipeline that ships your work to the public.

Ch 25Observability and securityMedium18 units

Logs, metrics, traces. Sentry. The OWASP top 10 as ten stories. The instrumentation that lets you answer 'what broke' in under two minutes.

Ch 26Performance and scaleMedium18 units

Core Web Vitals, the critical render path, caching layers, database indexes. When you actually need Redis or a queue. Measure first, every time.

Block 9

Career foundations

Ch 27–29
Ch 27Working as an engineerMedium16 units

Reading codebases, asking good questions, PR descriptions reviewers read, code review etiquette, estimation honesty. The soft stack that decides if you stay hired.

Ch 28Staying currentMedium15 units

The half-life problem. What doesn't change vs what changes constantly. The information diet you can actually sustain.

Ch 29CapstoneHigh point14 units

Spec it, design it, build it, test it, deploy it, iterate twice on real feedback. The portfolio piece you take to interviews.

Block 10

Getting hired

Ch 30–31
Ch 30Interview prepPEAK18 units

The realistic junior-AI-engineer pipeline. Resume, GitHub, DSA realism, take-homes, behavioural, light system design. The application sprint that gets you offers.

Ch 31The first 90 daysHigh point17 units

What 'junior' actually means in a team. Onboarding fast. The non-technical mistakes that get juniors fired. The six-month review you set up for yourself.

Full access

One price. Lifetime access.

A$4,000once. You keep the course forever — including every revision when the AI tooling chapter or the interview pipeline shifts.

  • ✓All 32 chapters, 541 units, every gated chapter assignment with its rubric
  • ✓47open units — chapter 0 in full plus every chapter’s orientation unit
  • ✓Local progress tracking and a continue-learning button so the course meets you where you left it
  • ✓The capstone brief, the interview chapter, and the first-90-days playbook — the chapters most courses skip
Sign up to unlockRead chapter 0 first

Frequent objections

Honest answers.

Who is this actually for?

An adult who can use a phone, a browser, and a credit card, but who has never used a terminal, never written a line of code, and wants a junior engineering job at a company that uses AI tools. If you already know what a closure is, this course will feel slow for the first eight chapters and then catch up to you. If you don't, this is the course written for you.

Why A$4,000? Other bootcamps cost more.

Other bootcamps cost A$15,000–A$30,000 and fund a building, a cohort, and a careers team. This course is text-first, do-shaped, and you read it on your own. The price covers the writing, the engineering of the platform, the assignment grading you do against the rubric, and lifetime access. Without the building and the cohort, the price drops by an order of magnitude.

How long does it actually take?

Roughly 480 hours of guided study end to end. At ten hours a week, that's about a year. At twenty hours a week, six months. Faster is possible if you bring relevant background. Slower is fine and expected if you have a job and a family — the course was built for the working adult, not the gap-year student.

Do I need a powerful computer?

Any laptop from the last five years runs the whole course. The AI tooling chapter (22) recommends sixteen gigabytes of RAM for local LLMs, but the rest of the course works on eight. macOS, Windows, and Linux are all supported; chapter 2 shows the bash and PowerShell commands side by side.

Does it cover AI engineering specifically?

Yes. Chapters 22 and 23 are dedicated to AI tooling — Ollama and Continue.dev for the local-first workflow, Claude Code and the harness for spec-shaped work. The capstone (chapter 29) and interview prep (chapter 30) target a junior AI-engineer role, not a 2018 frontend role. The whole curriculum was written knowing AI is the assumption now, not the optional add-on.

What if I get stuck on chapter four and can't move?

Every unit ends with two-to-four named common stumbles and the fix for each. Each chapter ends with a self-graded assignment where you check your own work against a green/yellow/red rubric — yellow means re-read the relevant unit, red means redo the chapter. You move forward only when you've earned green, so the course can't accidentally carry you past a gap.

Will this course get me a job?

It can't promise that. What it does promise: the work that gets you to the interview, the work that gets you through the interview, and the work that keeps you employed in the first ninety days. The pipeline outcome depends on the market, your location, your portfolio polish, and luck. Everything the course can control, it controls.

Why one price, no subscription?

Subscriptions feel exploitative for content you don't consume continuously. You buy it, you read it on your timeline, you keep it. The same applies if you come back to chapter 25 in three years for a refresher.

Is chapter 0 really free with no signup?

Yes. Read every unit in chapter 0 without an account. If the voice, the analogies, and the pace work for you, the rest of the course will too. If they don't, close the tab. The free chapter is enough to make that call.

Chapter 0 is free. The terminal can wait.

Read the first three units. Name the four parts of your machine, open dev tools on a real website, write down twenty keyboard shortcuts you actually used. If the voice and the pace work for you, the rest of the course will too.

Start chapter 0See the syllabus