7 connected subjects
Web developer
From a meaningful document to a typed, accessible application.
Outcome: Build a responsive application and explain how the browser renders it.
Start from the outcome
Choose a direction, not a permanent identity. Lessons and progress are shared wherever paths overlap.
7 connected subjects
From a meaningful document to a typed, accessible application.
Outcome: Build a responsive application and explain how the browser renders it.
10 connected subjects
Follow a request from a typed interface to a database policy.
Outcome: Build a synthetic business system with trustworthy tenant boundaries.
7 connected subjects
Make a game feel right, save reliably, and fit a frame budget.
Outcome: Build a browser game and extend it into a measured 3D scene.
4 connected subjects
Transfer programming ideas into C# and the .NET runtime.
Outcome: Model data, compose behavior, query collections, and handle asynchronous work.
8 connected subjects
Make a change observable, testable, reviewable, and recoverable.
Outcome: Explain and verify the path from a commit to a secure deployment.
5 connected subjects
Use AI for reach while retaining your own engineering judgment.
Outcome: Navigate code, frame changes, reproduce bugs, and verify generated work.