Roadmap · Build products
.NET developer (Blazor)
Opens with creditsFor people who want a .NET developer job, the stack behind banks, telecoms and enterprise software houses across Pakistan, the Gulf, India and beyond. By the end you can build, test, secure and ship a production-ready ASP.NET Core application with EF Core and SQL Server, with a Web API, Angular, React or Blazor front end, and explain the choices behind it.
Curated by Tauseef Fayyaz10 stages, 59 topics~18 months at a few hours a weekBy the end, you will be able to
- Write modern C# on .NET 10 (records, pattern matching, nullable reference types, LINQ and async) and drive everything from the dotnet CLI
- Build an ASP.NET Core API with the right DI lifetimes, a correct middleware order, validation and one consistent error shape
- Model data with EF Core and SQL Server, write migrations, and find and fix N+1 queries and tracking mistakes
- Secure it with Identity or JWT bearer tokens and policy-based authorisation, and connect a front end or client safely
- Test it with xUnit, test doubles and WebApplicationFactory integration tests against a real database
- Make it production-ready: health checks, OpenTelemetry, rate limiting, versioning, structured logs, caching, SSE, feature flags, ProblemDetails and resilience
- Ship it with Docker and GitHub Actions to Azure App Service and Azure SQL, with secrets in Key Vault, and talk about it the way enterprise teams expect
The path
10 stages, in the order to learn them. Open one to start.
1C# and the .NET platformInstall the .NET 10 SDK, learn how the platform fits together and drive it from the dotnet CLI. Then learn the modern C# that every ASP.NET Core codebase uses: types, records, pattern matching and nullable reference types.7 topics · ~7 weeks
- 1What .NET is, and which version to useModern .NET is a free, open source, cross-platform runtime and set of libraries from Microsoft.
- 2The SDK, the runtime and the dotnet CLIThe SDK is what you install as a developer: the compilers, templates and the
dotnetcommand. - 3Projects, solutions and NuGetA project (
.csproj) builds one assembly, usually a .dll. - 4Types, classes and interfacesC# is statically typed: every variable has a type the compiler checks before the program runs.
- 5Records and pattern matchingRecords are types built for data.
- 6Nullable reference typesNullReferenceException is the most common crash in .NET.
- 7Exceptions and disposing resourcesWhen code meets a situation it cannot handle, it throws an exception, and the nearest matching
catchup the call stack deals with it.
7 in this stageOpen this stage2C# for real work: LINQ, collections, generics and asyncThe C# you use every day at work: picking the right collection, querying it with LINQ, writing generic code and making slow I/O async without blocking threads. EF Core and ASP.NET Core build directly on all four.6 topics · ~2 months
- 1Collections and when to use eachMost code is moving data through collections, so choose them on purpose.
- 2LINQ: filter, shape, sort and groupLINQ (Language Integrated Query) is a set of methods you chain to work with data.
- 3Deferred execution, IEnumerable and IQueryableA LINQ query does nothing when you write it.
- 4Generics, delegates and lambdasGenerics let you write code once for many types while staying type-safe:
List<T>,Task<T>,ILogger<T>andIRepository<T>are all generic. - 5async/await and TasksMost server work is waiting: for SQL Server, an HTTP call or a file.
- 6Blocking, cancellation and async streamsThree async habits separate juniors from people a team trusts.
6 in this stageOpen this stage- ASP.NET Core basicsHow an ASP.NET Core app starts, how a request travels through middleware to an endpoint, and how services and settings reach your code. Learn minimal APIs and controllers side by side, because enterprise code uses both.6 topics · ~2 monthsOpens with credits
- Data with EF Core and SQL ServerModel your data with EF Core, evolve the schema with migrations and query it efficiently. Most .NET jobs pair EF Core with SQL Server, and most slow .NET apps are slow because of the queries, so learn the traps as well as the features.6 topics · ~2 monthsOpens with credits
- Authentication, authorisation and securityKnow who is calling and what they may do. Use ASP.NET Core Identity or JWT bearer tokens, express rules as policies, and check your API against the OWASP risks that matter most to banks and enterprise clients.5 topics · ~7 weeksOpens with credits
- Blazor components and render modesBlazor lets you build the web UI in C# with Razor components, no JavaScript framework required. Learn render modes first, because they decide where your code runs, then components, forms, auth and calling your API.5 topics · ~2 monthsOpens with credits
- Testing .NET applicationsProve your code works and keeps working. Unit test business rules with xUnit, replace slow or external dependencies with test doubles, and run integration tests through the real pipeline with WebApplicationFactory and a real database.5 topics · ~6 weeksOpens with credits
- Production-ready ASP.NET CoreThe difference between a demo and something a bank will run: health checks, metrics and traces, rate limits, versioning, structured logs, caching, live updates, feature flags, one error shape and resilient outgoing calls. Each is a few lines in Program.cs once you understand it.9 topics · ~2 monthsOpens with credits
- Ship it: Docker, CI/CD and AzurePackage your app in a container, build and test it on every push with GitHub Actions, and deploy to Azure App Service with Azure SQL, with configuration and secrets handled properly through Key Vault.5 topics · ~6 weeksOpens with credits
- The enterprise .NET jobWhat banks, telecoms and enterprise software houses actually expect: sensible architecture without over-engineering, background jobs, working in large existing codebases, and one portfolio project that proves everything in this roadmap.5 topics · ~2 monthsOpens with credits
8 more stages, 46 more topics, free with an account.
You have seen the open stages of the .NET developer roadmap. Every topic it covers is listed above, and an account opens the rest: what each topic means, a question to check yourself, the courses, the practice and Tauseef's advice for every stage. Early access is open: sign up and your account is active shortly after.
Everything here is free to learn from. A few things, like adding a roadmap, keeping a cheat sheet or asking Tauseef a question, use credits. You get 15 when you join, your first roadmap is free, and if you are learning seriously and run out, you can ask for more. Credits only make sure the platform goes to people who are actually learning.
Build a project
A finished project proves more than a certificate.
- Start with this oneintermediate1 semester · 1 to 2 studentsProduction-Ready ASP.NET Core API for Intercity Bus Seat Booking
Built for this roadmap: seat holds under concurrency plus every item from the production stage, tested against a real database
- C#
- ASP.NET Core
- Entity Framework Core
- PostgreSQL
- Redis
- intermediate2 semesters · 3 studentsSchool Report Card System with Configurable Grading Rules and Batch PDFs
Configurable rules and form-heavy screens in C# end to end, a good fit for Blazor
- Next.js
- NestJS or Laravel
- PostgreSQL
- Job queue (BullMQ or Laravel Queues)
- Headless Chromium for PDFs
- advanced2 semesters · 3 studentsDouble-Entry Ledger Service for Marketplace Wallets and Payouts
Transactions, idempotency, concurrency and audit: the problems banks and fintechs hire .NET developers for
- Go or Kotlin
- PostgreSQL
- gRPC or REST API
- Property-based testing
- Docker Compose
Related on Sefism
Picked from the other libraries by shared topics.
Best practices
See all- TypeScript Best PracticesModern TypeScript best practices for 2026: strict settings, TypeScript 7, modeling data with unions, safe narrowing, runtime validation, generics and typed linting.
- Spring Boot Best PracticesBuild Spring Boot 4 services that are easy to change and safe to run: injection, configuration, REST layer, JPA, virtual threads, Actuator, tests and shutdown.
- ASP.NET Core Best PracticesBuild fast, safe ASP.NET Core 10 APIs: DI lifetimes, validated options, minimal APIs, problem details, async rules, EF Core, rate limits, tests and health checks.
Checklists
See all- Production Readiness ChecklistCheck a service before it takes real traffic: ownership, SLOs, capacity, timeouts and retries, alerts, rollout and rollback, backups, security and on-call.
- API Security ChecklistCheck your REST or GraphQL API against the OWASP API Security Top 10: authentication, object authorization, rate limits, input validation, SSRF, CORS and logging.
- Database Migration ChecklistCheck a schema or data migration before it ships: expand and contract, lock behaviour, online indexes, batched backfills, rehearsal on real data, backups, rollback, deploy order and monitoring.
Project structures
See all- Express with TypeScript project structureFor students who know a bit of JavaScript and want a backend that looks like the ones teams actually run. Express gives you almost no structure, so this layout supplies it: one folder per feature under src/modules, each split into routes, controller, service and repository, with Zod at the edge and Vitest plus Supertest for tests.
- NestJS project structureFor people who want a structured TypeScript backend with clear rules about where code goes. Every feature is a Nest module that owns its controller, service, DTOs, entities and tests, so the app grows by adding folders, not by stretching old ones. The tree follows one orders API from nest new to a codebase a whole team can run for years.
- FastAPI project structureA typed Python API for an orders app, built the way the FastAPI docs and the official full stack template lay it out: one
apppackage, a router per feature, Pydantic schemas at the edges, services in the middle and SQLAlchemy models with Alembic migrations underneath. For students who have finished the FastAPI tutorial and want to know where the second, tenth and fiftieth file go.
Career questions
See all- Should I use PostgreSQL or MongoDB for my project?For most student and startup projects, PostgreSQL is the safer default: relational data, joins, constraints and transactions fit most apps, and it handles JSON and vector search too. MongoDB is a good fit when your data is naturally document-shaped and varies a lot, or your team already knows it well. Model your data first, then choose.
- How do I choose between frontend, backend, mobile, cloud, cybersecurity, data and AI without trying them all for years?Do not try to pick the best field; pick the one whose daily problems you can tolerate on a bad day. Run a short, cheap experiment in two or three candidates, compare what you enjoyed doing rather than what sounded exciting, check the local job market, and commit for six to nine months.
- Should I use Firebase or Supabase for my app?Both let you ship an app fast with auth, a database, storage and hosting-style services. Supabase is built on PostgreSQL, so it suits relational data and SQL skills you will reuse anywhere. Firebase is a mature Google platform with a document database and strong mobile tooling. Choose by your data shape, your platform, and how much you want to learn transferable database skills.
Cheat sheets
See allWork with me
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com