VS Code & the Professional Developer Workspace Use the editor as a transparent view of the repository, keep extensions intentional, and understand future quality gates.
Book 5 · Editor & workspace Course baseline: September 17, 2026 · Windows-first · Project-driven · Production-oriented
Contents 1. Editor philosophy 6. Formatter vs linter vs types vs tests
Phase 01 | Page 2 of 5
Your editor should reveal the system, not hide it A good editor improves navigation, feedback, refactoring, and inspection while keeping the project understandable outside the editor. The terminal and repository remain authoritative.
If VS Code is already installed, verify rather than reinstall. If not, use the official installer or WinGet according to your organization's policy. After installation:
code --version Get-Command code
If code is not recognized but VS Code opens normally, the shell command may not yet be on PATH. Reopen the terminal after installation and inspect PATH before reinstalling the editor.
Set-Location "$HOME\Developer\full-stack-2026-lab" code .
The dot means “this directory.” This habit matters because the folder you open becomes the editor's workspace context.
PowerShell working directory → code . → VS Code workspace root →
Phase 01 | Page 3 of 5
Explorer Search File tree. Use it to understand structure, not Search across the repository. Essential for to create random folders. tracing usage and avoiding duplicate abstractions.
Source Control Integrated Terminal Convenient view of Git changes. Still verify Useful, but remember that each terminal with git status and diffs. has its own process environment and working directory.
Do not install dozens of extensions before the project needs them. Start with language/editor support that provides clear value. JavaScript/TypeScript support is built in. Later phases can add ESLint, framework-specific helpers, database tooling, and formatting once the corresponding configuration exists.
Formatter How should code be laid out?
Linter Does the code violate style or correctness rules?
Type checker Are values used consistently with their types?
Tests Does observable behavior meet expectations?
These are different quality gates. Later CI will run them separately so failures are diagnosable.
Use one project root. Avoid nesting accidental duplicate repositories such as taskflow/taskflow . Avoid placing projects inside folders aggressively synchronized by enterprise backup software if it causes file-locking or node_modules issues. Prefer a simple development path such as:
Phase 01 | Page 4 of 5
$HOME\Developer\taskflow
Windows commonly uses CRLF while many developer tools and servers use LF. Git can normalize line endings. We will add an explicit .gitattributes only when the repository exists in Phase 02 rather than generating configuration before there is a project to own it.
□ code . opens the current folder. □ You can distinguish editor conveniences from project configuration. □ You understand formatter, linter, type checker, and tests as separate checks. □ You have chosen a clean developer workspace path.
Phase 01 · Book 5 · Editor & workspace
Phase 01 | Page 5 of 5
VSCode and Developer Workspace 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 “VSCode and Developer Workspace” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: repository root → workspace package → dependency graph → task runner → artifact. 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 “VSCode and Developer Workspace” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Verify git, node, npm/corepack, pnpm, and editor command availability from a fresh terminal.
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.