PowerShell & the Windows Developer Mental Model Learn the shell, paths, PATH lookup, environment variables, working directories, and failure evidence before frameworks enter the picture.
Book 1 · Windows & terminal foundations Course baseline: September 17, 2026 · Windows-first · Project-driven · Production-oriented
Contents 1. The shell mental model 6. Exit codes
Phase 01 | Page 2 of 6
Your terminal is an engineering instrument Many learners treat a terminal as a place where tutorials tell them to paste commands. A full-stack developer needs a better model: the shell is a programmable interface to the operating system. It has a current working directory, environment variables, executable lookup rules, command parsing rules, and an exit status.
You type a command → PowerShell parses it →
Windows locates executable → Program runs → Exit/output returns
Get-Location
Get-ChildItem
Get-ChildItem -ForceGet-Location answers one of the most important debugging questions in this entire course: where is this command running? Get-ChildItem lists directory contents; -Force also reveals hidden items such as .git .
A relative path is interpreted from the current working directory. If the current directory is wrong, a perfectly valid command can appear broken.
Set-Location $HOME
New-Item -ItemType Directory -Path "$HOME\Developer" -Force
Set-Location "$HOME\Developer"
Get-LocationPowerShell aliases such as cd and ls are convenient, but the course sometimes shows the full cmdlet name so you understand what PowerShell is actually doing.
Phase 01 | Page 3 of 6
Set-Location "C:\Users\YourName\Desktop\Full Stack Learning"Quotes are not decoration. They tell the shell that spaces belong to one path argument.
Get-Command node -ErrorAction SilentlyContinue
Get-Command git -ErrorAction SilentlyContinue
Get-Command pnpm -ErrorAction SilentlyContinue
$env:Path -split ';'Get-Command tells you which executable PowerShell will run. This becomes crucial when two Node installations exist and the wrong one appears first on PATH.
Figure 2 - PATH lookup - Version mismatches often come from executable lookup, not from the project.
Environment variables are named values inherited by processes. They are how shells and applications discover paths, configuration, and later secrets.
Phase 01 | Page 4 of 6
$env:Path $env:USERPROFILE $env:APPDATA $env:LOCALAPPDATA
$env:Path += ";C:\something" changes PATH for the current PowerShell process. It does not automatically rewrite the user's persistent environment settings. This distinction prevents the classic “it worked until I opened a new terminal” confusion.
git --version $LASTEXITCODE
Human-readable output is useful, but programs also communicate success or failure through exit codes. Later, CI/CD systems rely on exactly this behavior.
Environment value $env:NAME $NAME
Set environment value $env:NAME="x" export NAME=x
Home $HOME $HOME
1. Create $HOME\Developer\full-stack-2026-lab . 2. Move into it. 3. Create notes.txt with New-Item . 4. List normal and hidden files. 5. Print your PATH one entry per line. 6. Use Get-Command for PowerShell itself.
Phase 01 | Page 5 of 6
“The term ... is not recognized” PowerShell could not resolve the command. Check whether the tool is installed, then Get-Command , then PATH. Do not reinstall the entire project.
Path not found Check Get-Location , spelling, quoting, and whether the directory actually exists.
1. Why can the same command work in one terminal and fail in another? 2. What does PATH control? 3. Why does a working directory matter to project tools? 4. What is the difference between shell output and an exit code?
Phase 01 · Book 1 · Windows & terminal foundations
Phase 01 | Page 6 of 6
PowerShell and Windows Mental Model matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “PowerShell and Windows Mental Model” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: source file → tool/runtime → process → OS environment → terminal evidence. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: A verified toolchain report showing shell, Git, Node, Corepack/pnpm, editor, PATH, ports, and diagnostic commands.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
Input -> owner -> transformation -> observable output -> failure evidenceDo not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “PowerShell and Windows Mental Model” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Open ordinary PowerShell and record pwd, whoami, and PATH-related observations.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Terminal still using an old executable after installation
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.