01 / Curriculum

Three tracks, one rhythm: a merged pull request every week

Every track runs on the same weekly loop. You open a pull request on Monday, a practising engineer reviews it line by line, and you resubmit until it is approved. The full week-by-week sequence sits in the syllabus table.

The three tracks

  • Foundation

    16 weeks. Git, HTML and CSS, JavaScript fundamentals, first solo project.

    UAH 28,0003 instalments

  • Professional

    24 weeks. React, Node, testing, and a team project with a reviewer on every pull request.

    UAH 52,0003 instalments

  • Review Only

    8 weeks. Bring your own repository and get structured weekly reviews on your own code.

    UAH 9,800paid once

03 / Curriculum

Week-by-week syllabus

Twelve core weeks, one pull request each. Every deliverable receives written, line-anchored feedback from a practising engineer. Scoring is public in the review rubric.

Cohort 12 · 12 core weeks and 4 lab weeks · 16 seats
WeekModuleStackDeliverableReview
01Tooling and the loopGit, CLIPR #1: notes CLILine review
02HTML and CSSHTML, FlexboxPR #2: landing pageRubric review
03JavaScript coreES2023, DOMPR #3: quiz componentLine review
04Async dataFetch, RESTPR #4: weather dashboardPair review
05React componentsReact, VitePR #5: task boardRubric review
06State and formsReact, ZodPR #6: multi-step formLine review
07TestingVitest, PlaywrightPR #7: tested checkoutDemo review
08BackendNode, SQLPR #8: notes APILine review
09Auth and deployJWT, DockerPR #9: full-stack appDemo review
10Portfolioa11y, perfPR #10: portfolio repoRubric review
11InterviewsCV, systemsPR #11: interview packPanel review
12CapstoneReleasePR #12: capstone releasePanel review

Weeks 13 to 16 are lab weeks for portfolio hardening, mock interviews, and the capstone release. See portfolio expectations.

04 / Review Rubric

Four criteria, scored 1 to 4, published before you pay

Every weekly pull request is scored on the same four criteria. The scale is fixed, the reviewer is named in the thread, and nothing is adjusted to soften the result.

1 missing 2 partial 3 solid 4 production-ready
  1. 01

    Correctness

    The pull request does what the task asks, and handles the edge cases written into the brief.

  2. 02

    Readability

    Names, structure and comments let another developer follow the change without asking you questions.

  3. 03

    Testing

    The change ships with tests that fail before the fix and pass after it, plus the command to run them.

  4. 04

    Communication

    The description explains the decision and names the trade-off. Review comments get an answer in the thread.

Scoring note

Reviewers do not inflate scores. A 2 stays a 2 until the work changes. Your scores sit in the repository history, so week one and week sixteen are directly comparable.

Modules and deliverables are listed in the syllabus table.

05 / Portfolio expectations

What your repository proves to a hiring team

Every week of the course produces one public pull request. By week 16 you own a repository of reviewed work, not a folder of finished tutorials.

01 / Public repository

A repo you own from the first commit

Work sits on GitHub under your own account. A readme, setup steps and a short architecture note are part of the deliverable, because someone opening the project cold should be able to run it.

02 / Commit history

Small commits that explain a decision

Reviewers read the history, not only the final file. We ask for commits that state the intent of a change, so a hiring manager can follow how a feature grew from a failing test to a merged branch.

03 / Review threads

Feedback left open and readable

Line-anchored comments stay in the pull request after merge. Nothing is deleted to look cleaner. The thread is the record of how you respond to critique, and it is the part interviewers ask about most.