coder000

Series

Our best work comes in courses, not fragments — each series takes you from the very first step to genuinely capable, in order, with nothing assumed. Pick one and see it through.

Learn the stack

The whole path →

The Windows PC, Docker, Git, Blazor, PostgreSQL and database design, each as a complete series that assumes nothing and ends with you capable.

6 parts · ~38 min total · starts at Part 1

Set Up a Windows PC for .NET Development

Six hands-on parts for a Windows 11 PC used for .NET work: SDKs, runtimes and global.json, WSL, ports and the firewall, LocalDB and PostgreSQL in Docker, the Git for Windows settings that stop the warnings, and the HTTPS developer certificate. Every command was run on a real machine and every output is quoted.
All 6 parts →🧭 The next series for this PC: Docker for .NET Developers on Windows🔧 Every setup error we have reproduced, in the Fixes category
8 parts · ~51 min total · starts at Part 1

Docker for .NET Developers on Windows

Eight hands-on parts that take a .NET developer on Windows from a fresh Docker Desktop to an app and its PostgreSQL database running from one compose file and shipped as an image: what Desktop actually runs, containers, bind mounts and volumes, ports and networking, PostgreSQL, Compose, building the image, and the daily loop. Every command was run on a Windows 11 PC and every output is real.
All 8 parts →📥 The sample API's Dockerfile, as built in Part 7📥 The compose.yaml for the API and its PostgreSQL, from Part 6🧭 The PC itself: Set Up a Windows PC for .NET Development🔧 Every Docker error we have reproduced, in the Fixes category
12 parts · ~74 min total · starts at Part 1

Database Design for Developers

Twelve hands-on parts from an ER sketch to a production schema, on SQL Server and PostgreSQL side by side: keys, relationships, column types, constraints, normalisation, naming, indexes, soft delete and history, migrations, and search. Every script was run on both engines; every output shown is real.
All 12 parts →📥 The finished clinic schema for PostgreSQL (every part has its own script to download)📥 The finished clinic schema for SQL Server🧭 The series this one continues: Conversation to System Design📦 ClinicLive, the clinic whose tables start the series
9 parts · ~63 min total · starts at Part 1

Student Projects: From Conversation to Database

Nine classic student projects, each designed from a conversation with the person who needs it: library, school, attendance, hostel, hospital, inventory, hotel, railway reservation and online shop. Entities, relationships, keys and CREATE TABLE scripts run on SQL Server and PostgreSQL, the viva questions answered with real output, the textbook mistake repaired, and an ER diagram for every one.
All 9 parts →🔧 Draw your own ER diagram from CREATE TABLE statements🔧 Check a spreadsheet for normalization problems🧭 The series this one follows: Conversation to System Design🧭 The next step after a project: Database Design for Developers

Build with AI

The whole path →

ClinicLive, a clinic app built with an AI pair programmer from the first prompt to a private on-premises assistant, every prompt shown and every mistake kept.

12 parts · ~97 min total · starts at Part 1

From Prompt to Pocket

The trilogy's third season: put a working app in a patient's pocket with .NET MAUI Blazor Hybrid — one set of Blazor screens for Android, Windows and the browser, real push notifications, haptics, geolocation, a QR scanner and offline support, built with AI across twelve parts. Every native feature is a capability interface; every screenshot is real; every dead end is kept in.
All 12 parts →📦 Same repo, season three — tags pocket-02…11📱 Setup & publishing runbook (docs/pocket.md)
12 parts · ~89 min total · starts at Part 1

From Prompt to Private

Season four: the clinic gets its own AI, on its own server, because patient data cannot leave the building. Free open-weight models on Ollama, a 16 GB GPU (and an honest CPU-only minimum), knowledge in PostgreSQL with pgvector, a staff assistant and a patient assistant on the kiosk and the phone — built with AI across twelve parts, every number measured, every wrong answer kept in.
All 12 parts →📦 Same repo, season four — tags private-02 onward🦙 Ollama, the local model runtime the season uses
6 parts · ~38 min total · starts at Part 1

Claude Code for .NET Developers

Six hands-on parts that make Claude Code work the way a .NET repository works: a CLAUDE.md that earns its tokens, permissions for dotnet on Windows, hooks that format and test, a skill for EF Core migrations, a reviewer subagent, and a read-only MCP server in C#. Every file was used in real sessions on one sample solution, and each part reports what did not work as well as what did.
All 6 parts →🚀 Not installed yet? Start with Set Up Claude Code for .NET Like You Mean It📥 AppointmentDesk, the sample solution every part works on (zip, 19 KB)📚 Anthropic's Claude Code documentation, the source for every feature claim in the series
5 parts · ~45 min total · starts at Part 1

Blazor vs React vs Angular

One app, four clients, one measurement. The same todo application was built in Blazor WebAssembly, Blazor Server, React 19 and Angular 22 by headless Claude Code sessions from one spec, judged by one frozen suite of 61 tests, then measured the same way: bytes, startup, a 10,000-row list, memory, lines of code, accessibility, and how many turns the AI needed. Five parts: the method, the two Blazor builds, React, Angular, and the results with seven hypotheses settled one by one.
All 5 parts →📦 coder000-todo-four-ways: the API, the suite, the reference client and the four AI-built clients with their per-step commits📄 SPEC.md, the contract every client implements📊 sessions.csv, one row per metered Claude Code session🧭 The render-mode post this series measures: Blazor Server vs WebAssembly vs Hybrid

Prepare for interviews

The whole path →

Two series that take a .NET developer and an AI engineer through the questions they will actually be asked, with worked answers.