Watching CLI tutorials feels like progress. You nod at PATH diagrams. You pause a video to copy a command. You finish a playlist titled “Windows Command Line Full Course.” Then a production incident hands you a blank prompt and the playlist doesn’t play in your head.
That gap—tutorial consumer → operator—is the product problem I’m building around with CMD Master.
What tutorial consumption trains
- Recognition of concepts when cued.
- Happy-path sequences in the author’s order.
- Confidence that is bound to narration.
What operators need
- Initiation without a narrator.
- State awareness (cwd, env, shell identity).
- Recovery from errors under mild stress.
- Transfer across CMD, PowerShell, and sometimes Bash contracts on one OS.
Those are different muscles. Screenshots and lectures can support them. They can’t replace them.
The skills gap in concrete behaviors
When someone is still a consumer, you see:
- Panic on a non-zero exit they can’t name.
- Paste of PowerShell into CMD (or the reverse) without noticing.
- PATH “fixes” without verifying with
where/Get-Command. - Avoidance of spaces/non-ASCII until reality forces a corruption bug.
When someone is becoming an operator, you see:
- They inspect before they escalate.
- They change one variable at a time.
- They can explain which shell they’re in and why the quoting looks that way.
- They write thin glue instead of mythic one-liners.
What CMD Master is (without launch-speak)
Curriculum pillars mapped to the gap
| Consumer habit | Operator replacement drill |
|---|---|
| Watch PATH video | Break PATH on purpose; repair with verification |
| Copy pipe examples | Pipe objects; then pipe native text; name the difference |
| Read Execution Policy thread | Reproduce block; list scopes; narrow bypass |
| Finish playlist | Cold prompt: complete a six-step mission without narration |
CMD Master’s job is to make the right column cheaper to practice than the left column is to binge.
What success looks like (non-vanity)
Not DAU cosplay. Success is: a Windows-first junior who can enter an unfamiliar shell, identify it, run a safe diagnostic, and recover from a non-zero exit without waiting for a YouTube reassuring voiceover.
Soft CTA philosophy (why one link)
This article is showdev with a point of view, not a landing page. One contextual link is enough; the work should make the next click optional rather than begged. Profile bio can carry the rest.
Build roadmap (honest, unfinished)
- Better early pacing (post–prompt #3 scar).
- More diagnostic missions (PATH, encoding, policy).
- Clearer multi-shell labeling.
- Covers and distribution experiments (this Dev.to Plan A queue).
Operators aren’t manufactured by a single article. They’re manufactured by repeated, honest practice under mild friction.
CMD Master is free interactive browser-terminal learning for CMD, PowerShell, and Bash, aimed at Windows-first learners. The design bet is simple: reps at a real prompt with feedback beat passive tours.
What we’re targeting in drills:
- Early wins without lying about difficulty.
- Explicit shell contracts.
- Diagnostics (PATH, exit codes, quoting, encoding) as first-class—not appendices.
- Soft boundaries so prompt #3 isn’t a cliff (learned the hard way).
What we refuse
- Shame about CMD.
- “Linux first or go home” gatekeeping.
- Mega CTAs and hype posts pretending a trainer replaces a job.
Showdev status
This is still product work with fingerprints: quit points, myth-driven curriculum rewrites, comparison lessons for 5.1 vs 7 realities. If you teach Windows CLI, steal the sequencing ideas even if you never click the link.
The gap won’t close because someone watched one more video. It closes when the blank prompt stops feeling like a test they didn’t study for—and starts feeling like a tool they know how to pressure-test.
Top comments (0)