Next cohort starts 12 January · 14 seats

Learn to write code the way a reviewer reads it.

Twelve weeks of project-based programming courses in Ukraine, closed each week by a numbered code review you resubmit before the next module opens.

Apply to the cohort Read a real review
Olena K.lead reviewer · 2h ago
Line 41: the fetch is never awaited. Blocker. Fix it and resubmit. The second version is where the learning happens.
src/api/user.js+12 −9
  1. −const user = fetch(url)
  2. −return user.data
  3. +const res = await fetch(url)
  4. +if (!res.ok) throw new Error(res.status)
  5. +return res.json()
Reviewer's desk with a laptop, a printed rubric and a pen

Ledger / Proof

The checks behind the cohort.

Numbers we track, plus the limit we will not hide.

Reviews per student
6
Cohort cap
14 students
Portfolio repos
3 shipped
Outcome caveat
No guarantee

Hiring depends on completed work, interview performance and market conditions. We publish the review method so you can inspect the process before you apply.

Read the review method

04

Review Method

Every submission returns a numbered list within 72 hours

A reviewer opens your branch, quotes the exact lines that broke, tags the severity, and names the direction to try next. One reviewer covers seven students, so nobody waits in a queue.

  1. 01

    Line-quoted finding blocker

    order.js:42, the fetch resolves after unmount and throws into an empty tree. Suggested direction: abort the controller in cleanup before you touch the loading flag.

  2. 02

    Behaviour note should-fix

    Filters.tsx:118, the list re-renders on every keystroke because the memo depends on a fresh array. Suggested direction: memoise the derived list, not the handler.

  3. 03

    Readability note nit

    api/client.ts:9, data hides three shapes under one name. Suggested direction: call it orderLines and the type narrows on its own.

  4. 04

    Resubmission mandatory

    You clear the blocker and the should-fix, then push again. The second version is where the learning happens, so a week never closes on the first draft.

Notes stay in the thread, dated and signed. Read a full review thread from week 6 before you apply.

04Curriculum timeline

Eight modules, each one closed by a review gate.

Modules run in order. The next one does not open until the previous review has been answered, so a gate works as a dependency rather than a formality. Weekly workload below assumes no prior professional experience.

  1. w01

    Toolchain and version control

    Git history, commit messages, and repository hygiene, checked line by line.

    +90 lines12 h / weekReview gate
  2. w02

    Semantic markup and layout

    Accessible markup and responsive breakpoints, read against a fixed checklist.

    +240 lines13 h / weekReview gate
  3. w03

    JavaScript fundamentals

    Functions, data flow, and error paths, each one explained in writing.

    +310 lines14 h / weekReview gate
  4. w04

    Browser APIs and async

    Event handling and fetch states. The second version is where the learning happens.

    +280 lines15 h / weekReview gate
  5. w05

    Component architecture

    State boundaries and prop contracts. Blocker notes must be closed before w06 opens.

    +420 lines16 h / weekReview gate
  6. w06

    Server and HTTP APIs

    Request validation, status codes, and the failure paths most tutorials skip.

    +380 lines16 h / weekReview gate
  7. w07

    Persistence and data models

    Schema review, migration order, and one reversible rollback you write yourself.

    +260 lines15 h / weekReview gate
  8. w08

    Portfolio and career preparation

    Portfolio audit, CV review, and a mock interview signed off by the reviewer.

    +180 lines10 h / weekSigned off

Reviewers are assigned at 1 per 7 students, with a 72-hour turnaround on every submitted module. The cost breakdown lists what each module includes and the instalment total.

Evidence / portfolio

Open the repository. Read the note. Then read what changed.

Four files taken from reviewed student repositories, each with the reviewer's numbered note and the diff that closed it. Names are cut to initials at the student's request.

Resubmission is mandatory and re-reviewed by the same person within 72 hours. Read a full review thread or ask admissions a question.

Cost disclosure

The full price, before you apply

One fee covers twelve weeks of project work, numbered code reviews on every submission, and a portfolio audit at the end. Nothing is billed later and nothing is sold separately.

Program costs, one cohort
ItemAmount
Program fee, 12 weeksUAH 42,000
Review and assessment, 14 reviews per studentIncluded
Portfolio audit and career preparationUAH 7,500
Total, paid in fullUAH 49,500
Instalments, 3 payments of UAH 16,500UAH 49,500
Materials, tooling and repository hostingUAH 0

Spreading the fee across three instalments does not add a margin: the instalment total is UAH 49,500, the same figure as paying once.

Refund terms

Cancel up to seven days before the start date and the fee is returned in full. Withdraw during the first two weeks and you are charged for the weeks attended at UAH 3,500 each, with the remainder refunded within ten working days. After week two the fee is not refunded, but your seat stays open for the next cohort.

See the same table on AdmissionsRead the full refund policy

Contact

Ask a reviewer before you apply

Questions about the 72-hour review turnaround, cohort dates, or the schedule reach a reviewer, not a call center. The UAH 49,500 instalment total is printed in full in the cost disclosure table.

Open the admissions form

Email
contact@thraxioz.com
Phone
+380 634 969 4483
Address
Business Center Gulliver, 1A Sportyvna Square, Kyiv, 01023, Ukraine
EDRPOU
48718231