Verify tools from the terminal instead of assuming an installer succeeded.
Course navigationPhase 01⌄
Windows Development Environment & Professional Tooling
Build and verify a reproducible Windows development environment without relying on hidden machine state.
Phase outcome and project increment
Learning outcome
Build and verify a reproducible Windows development environment without relying on hidden machine state.
Concrete deliverable
A verified toolchain report showing shell, Git, Node, Corepack/pnpm, editor, PATH, ports, and diagnostic commands.
Principles to keep while coding
Understand PATH, ports, processes, shells, and working directories because they explain many setup failures.
Prefer user-level development tooling when administrator privileges are unnecessary.
Record exact versions and verification commands so another developer can reproduce the environment.
Guided phase lab
Do these in order. Each step should end with evidence before the next one starts.
- 01
Open ordinary PowerShell and record pwd, whoami, and PATH-related observations.
- 02
Install or verify Git and VS Code with user-level installation where possible.
- 03
Install the course Node line with a version manager and prove which executable is active.
- 04
Enable Corepack and activate the repository package-manager version.
- 05
Verify git, node, npm/corepack, pnpm, and editor command availability from a fresh terminal.
- 06
Deliberately create a PATH or port conflict in a safe sandbox and diagnose it with Get-Command/Get-NetTCPConnection.
Get-Location
Get-Command node
node --version
corepack --version
pnpm --version
git --versionPredict what each command proves before running it. A command is useful only when its output answers a question.
Failures you should know how to diagnose
Terminal still using an old executable after installation
Predict the symptom, capture evidence at the nearest boundary, change one variable, and verify the same reproduction after the fix.
EPERM caused by writing to protected locations
Predict the symptom, capture evidence at the nearest boundary, change one variable, and verify the same reproduction after the fix.
Different shells resolving different PATH values
Predict the symptom, capture evidence at the nearest boundary, change one variable, and verify the same reproduction after the fix.
Port already in use by a forgotten development process
Predict the symptom, capture evidence at the nearest boundary, change one variable, and verify the same reproduction after the fix.
Lessons
The source chapters come first. Every phase now ends with a guided build, a debugging workshop, and an independent challenge so reading turns into transferable skill.
PowerShell and Windows Mental Model
Node Runtime and Version Management
pnpm Package Management and Permissions
Git and Professional Version Control
VSCode and Developer Workspace
PATH Permissions and Troubleshooting
Hands On Lab Exercises and Phase Exit
Guided Build Lab
Purpose Build and verify a reproducible Windows development environment without relying on hidden machine state.
Debugging Workshop
Goal Learn to diagnose this phase's failures systematically instead of reinstalling packages, changing random configuration, or copying a fix without understanding it.
Phase Synthesis & Independent Challenge
Mission Rebuild the capability of Phase 01 without following the exact code line-by-line. The goal is transfer: can you use the ideas when the variable names, UI, or route shape changes?
Mastery Capstone Lab
Integrate Phase 01 without following a transcript.
Exercises that increase independence
Open ordinary PowerShell and record pwd, whoami, and PATH-related observations.
Install the course Node line with a version manager and prove which executable is active.
reproduce and diagnose — Terminal still using an old executable after installation.
deliver A verified toolchain report showing shell, Git, Node, Corepack/pnpm, editor, PATH, ports, and diagnostic commands.
Can prove which executable a command resolves to and Can explain user PATH vs system PATH.
Do not leave the phase only because you reached the bottom
Phase exit criteria
Scenario and concept quiz
These questions test engineering choices rather than whether you remember a lesson title.