Track A
Software Development (Full-Stack JavaScript)
HTML and CSS fundamentals, JavaScript, React on the client, Node and SQL on the server. The track ends with a deployed full-stack application and a written review of its architecture.
01 / Curriculum overview
Track A
HTML and CSS fundamentals, JavaScript, React on the client, Node and SQL on the server. The track ends with a deployed full-stack application and a written review of its architecture.
Track B
Accessible markup, modern CSS layout, component state, and performance budgeting. The track ends with a multi-page interface build and an accessibility review you can walk a hiring team through.
Both tracks follow the same weekly release and review cycle. See the 16-week module schedule for week-by-week deliverables, or check the admissions requirements before you apply.
02 / Module schedule
Every module ends with a reviewed project. Weeks 1 to 6 are shared by both tracks; frontend and backend split at week 7.
Weeks 1 to 4
HTML, CSS layout, Git workflow and debugging. A task merges only after line-level comments are resolved.
Project: static profile page3 reviews
Weeks 5 to 8
DOM work, async requests, state handling and a small API client you can explain line by line.
Project: interactive dashboard3 reviews
Weeks 9 to 12
Frontend covers components and accessibility; backend covers databases, auth and tests. Same review rules in both.
Project: full-stack feature set3 reviews
Weeks 13 to 16
Team-sized build, deployment, README, CV structure and portfolio narrative. Hiring decisions stay with employers.
Project: capstone and case study3 reviews
A project closes only when the reviewer marks every comment resolved. Attendance alone does not pass a module.
04 / Review rhythm
Cadence is one written review per week, comments land within 48 hours, and a module closes only when no blocker is open.
Front-end track / sprint 3 / cart module / open
const total = items.reduce((a, b) => a + b.price, 0);
BlockerPrices arrive as strings. Convert before summing, or checkout totals break on the second item.
renderCart(cart, { currency: 'UAH' })
NitCurrency is hardcoded here and again in the summary. Pass one config object instead.
Back-end track / sprint 5 / auth middleware / resolved
if (!token) return res.status(401).json({ error: 'no token' });
ResolvedGuard added in the revision commit. The reviewer confirmed the fix on line 12 and closed the thread.
Revision step: you reply to each blocker with the commit that answers it, and nits stay optional. See the full module schedule.
06 / Enrollment
Applications for the next cohort close once the last seat is taken. Admissions runs a short assessment and an interview to check fit, then confirms your track, deposit, and start date.