Preparatory
Set up your machine, learn how computers work, and see what backend engineers build.
View 3 units +
- Orientation9
- Computer and Environment Setup7
- How Computers Actually Work6
C# and .NET first. Then Python and AI systems.
Start from zero and work toward production backend engineering through one ordered curriculum. Learn the concept, build in real files, submit your work, and use the feedback to decide what comes next.
1record Order(string Id, string Status,2 decimal Total);34string RouteOrder(Order order) =>5 order switch6 {7 { Status: "Shipped", Total: > 250 }8 => "Priority",9 { Status: "Pending" } => "Queue",10 _ => "Standard"11 };
Go from your first program to senior-level systems work. Open a card to inspect its units; every count comes directly from the course spine.
Set up your machine, learn how computers work, and see what backend engineers build.
C# and .NET from the first line through classes, LINQ, generics, async, testing, Git and the shell.
Discrete math, probability and statistics, plus data structures and algorithms measured in C#.
HTTP, SQL, ASP.NET Core, EF Core, Redis, Docker, authentication, testing and deployment.
Python as a second language for a C# developer, its idioms, ecosystem and FastAPI.
Classical ML, data engineering, deep learning, production AI, safety and evaluation.
Three applications built end to end: a dashboard, real-time chat and a portfolio API.
Architecture, scale, security, performance, observability and owning problems end to end.
Timed challenges, interview simulation, whiteboards and a 72-hour take-home project.
The curriculum is generated from the same spine and lesson frontmatter that build the course navigation. Published and coming-soon work stay visible.
Each step has a job. Together they turn reading into engineering practice.
Read a focused lesson built on the concepts that came before it.
Write and upload a real project from your own editor, not a toy browser sandbox.
Get a breakdown of correctness, quality, style, and the concepts being assessed.
Use progress and weakness tracking to choose what to practice next.
Not a collection of disconnected tutorials. The lessons, exercises, grading, and progress model share one curriculum.
Upload your .cs files for feedback on correctness, code quality, idiomatic style, and the concepts the exercise teaches.
Repeated mistakes are recorded across submissions and quizzes, with clear pointers to what to revisit.
Users, orders, invoices, and accounts keep the examples close to the services backend engineers build.
Exercises sit directly after the sections that teach them, so reading and writing code stay connected.