Learn vibe coding, one level at a time.

The intro course is free. Beginner through Advanced run as solo practice, and Team Lab continues as a team project.

A code editor panel beside the running web screen it produces

Course structure

Six levels, Intro through Enterprise

Intro through Advanced are solo practice. Team Lab is a team project, and Enterprise works on an existing system.

Solo practice

  1. LEVEL 1IntroFreeSolo practice
  2. LEVEL 2BeginnerKRW 30,000Solo practice
  3. LEVEL 3IntermediateKRW 50,000Solo practice
  4. LEVEL 4AdvancedKRW 100,000Solo practice

Project courses

  1. TEAM LABTeam LabKRW 300,000Team project
  2. ENTERPRISEEnterpriseKRW 1,000,000Applied project

Taken back to back, Intro through Advanced runs about three months.

Intro · Beginner · Intermediate · Advanced

What each level covers

What you build in one level carries into the next.

  • LEVEL 1Solo practice

    Intro

    Free

    Describe a program to AI in plain words, run what comes back, look at the result, and change the parts you do not like.

    What you do

    • Describing what you want so AI can act on it
    • Running the code you get on your own machine
    • Asking again when the result is off

    The goal here is the first "oh, it works" moment. Shaping it into a service comes later.

  • LEVEL 2Solo practice

    Beginner

    KRW 30,000

    Own one feature end to end. Writing down what you need, putting a screen on it, and tracking down what broke starts to feel routine.

    What you do

    • Turning an idea into something you can hand over
    • Laying out a UI
    • Adding a feature and changing it
    • Reading an error and finding the cause

    This is one feature at a time. Wiring several together into a service comes a little later.

  • LEVEL 3Solo practice

    Intermediate

    KRW 50,000

    What happens behind the screen comes into view. Once you can see where data lives and how it moves, the range of what you can build widens fast.

    What you do

    • Thinking about frontend and backend separately
    • Moving data over an API
    • Storing and reading from a database
    • Handling login and permissions
    • Undoing work with Git
    • Connecting a third-party service and trying realtime

    Still on your own for now. Splitting the work across people happens in Team Lab.

  • LEVEL 4Solo practice

    Advanced

    KRW 100,000

    Reading and changing code you did not write stops being daunting. You add to an existing program, tidy it up, and deploy it.

    What you do

    • Finding your way around unfamiliar code
    • Pinpointing where a change belongs
    • Fixing bugs and tidying code
    • Writing tests and running them
    • Working in separate branches
    • Deploying it for real

    By here you can handle most things solo. Next you do it alongside other people.

How it works

Learning and practice come as a set

You submit each assignment, apply the feedback, and move on to the next level.

  1. 01

    Learn

    See what you are building this time.

  2. 02

    Build

    The instructions sit beside your workspace, so you build as you read.

  3. 03

    Submit

    Hand in what you made.

  4. 04

    Feedback

    Find out what to change and why.

  5. 05

    Next

    Fix it, then move on.

Team Lab

Planned, built and deployed as a team

KRW 300,000

Team Lab

A team of five to ten builds one service together, from planning through deployment. The development environment, servers and sample data are set up to fit the project.

What teams build

  • A store screen with a product grid, cart panel and checkout steps

    Online store

    List products, put them in a cart, and carry that through to orders and payment.

    • Environment
    • Server
    • Sample product data
  • A messenger screen with a conversation list, message thread and presence dots

    Messenger

    Move messages in real time, then add read receipts and who is online.

    • Environment
    • Server
    • Sample account data
  • An HR screen with an org chart, member table and approval flow

    HR system

    Handle organizations and members, and make attendance and approvals flow.

    • Environment
    • Server
    • Sample org data
  • A game screen with a board, scoreboard and player markers

    Game

    Set the rules and scoring, and keep it from falling apart when everyone joins at once.

    • Environment
    • Server
    • Game assets
  • A marketing dashboard with a contact table, funnel and response chart

    Marketing tool

    Manage a contact list, send messages, and gather what came back.

    • Environment
    • Server
    • Sample contact data
  • A POS screen with a menu grid, order summary, card terminal and kitchen ticket

    POS / Kiosk

    Build what actually happens in a shop: taking the order, the payment, and the ticket that lands in the kitchen.

    • Environment
    • Server
    • Menu and store assets

Roles

  • Frontend
  • Backend
  • Database
  • AI
  • QA
  • PM

Roles are split per project without confining anyone to one area. You read and change code in other parts as the work requires.

How the team works

  • Git
  • Branch
  • Issue
  • Pull Request
  • Code Review
  • API Specification
  • Database Schema
  • Conflict resolution
  • Test
  • Deploy
Pull Request

#42

Cart total does not update when the quantity changes

feature/cart-total → main

2 reviews · 3 files changed

getTotal is missing qty. Multiply by it inside the reduce.

Enterprise

Analyse and change an existing system

KRW 1,000,000

Enterprise

A project course working on a codebase at production scale.

You work out how an unfamiliar codebase fits together, scope the impact of a requirement, then make the change and take it through testing, code review and deployment.

Systems you may be handed

  • An existing HR system
  • An existing CRM
  • An existing ERP
  • An existing internal system
  • A large web application

How it runs

  1. 01Read the code
  2. 02Map the system
  3. 03Analyse the requirement
  4. 04Trace the impact
  5. 05Make the change
  6. 06Test
  7. 07Code review
  8. 08Deploy

Pricing

Prices and running total

You pay once per course.

  • Intro

    Free

    Solo practice

  • Beginner

    KRW 30,000

    Solo practice

  • Intermediate

    KRW 50,000

    Solo practice

  • Advanced

    KRW 100,000

    Solo practice

  • Team Lab

    KRW 300,000

    Team project

  • Enterprise

    KRW 1,000,000

    Applied project

The intro course can be taken without payment.

For teams

Running this with a team

Get in touch if you are bringing this in as internal training or running it with a whole team. Team Lab and Enterprise were built for teams from the start.

Four colleagues around a meeting table looking at a laptop together

Frequently asked questions

Is this workable if I have never written code?

The intro course assumes you have not. Follow the screens from installation through to running it and you will be fine.

Can I just take the free intro?

Yes. You can take the intro course without paying and decide afterwards whether to continue.

How much time does this take per day?

There are no fixed class hours. You work assignment by assignment, so you go at whatever pace your week allows. Intro through Advanced back to back runs about three months.

What happens when I get stuck on my own?

Submit the assignment and you get feedback on what to change and why. You are not left to carry a blocker into the next assignment.

How are Team Lab teams put together?

Five to ten people per team, with roles split across Frontend, Backend, Database, AI, QA and PM to fit the project. You also build outside your own role using AI.

Who is Enterprise for?

People who want practice reading and changing code that already exists. Where Team Lab builds something new, Enterprise hands you a running system to modify and deploy.

Can a whole team at my company take this together?

Yes. Team Lab and Enterprise were designed for teams. Get in touch through the team training enquiry.

The intro course is free

Take it without paying, then decide whether to continue.

Learn vibe coding, one level at a time. | TypeCampus