The Pathway

Four stages. One continuous path.

From first page to full stack.

Fourteen courses across four stages. Every course is built around one project you keep, and each project follows you forward into the next rather than being thrown away.

A webpage becomes interactive, then version controlled, then a React application, then gains a backend, and finally becomes a complete production system you can show an employer.

Foundations

Stage 1 of 4

Programming literacy. These courses do not try to make you a professional developer, they make you fluent enough that everything after them makes sense.

Application Development

Stage 2 of 4

Actual engineering. Each course is built around one substantial application rather than a sequence of disconnected exercises.

Software Engineering

Stage 3 of 4

The practices that separate somebody who can build a thing from somebody a team can hire. Databases in production, testing as a discipline, authentication done properly, and the way real work is planned and shipped.

Full-Stack Engineering

Stage 4 of 4

This does not repeat the individual courses. Those teach the technologies. This teaches you to combine them into a software system, which is a different skill entirely.

Capstone Projects

Apply what you have learned

A separate learning mode, not a gallery. You receive requirements and acceptance criteria, but no tutorial. This is where student becomes developer.

What portfolio-ready actually means

It is a measurable state, not a phrase. A project does not earn the label until every one of these is true.

FunctionalityResponsive designAccessibility reviewError handlingTestingGit historyREADMEDocumentationDeploymentScreenshotsTechnical explanationA working live URL