Why “Learn Linux First” Advice Hurts Windows-First Juniors
The advice is everywhere: if you want to be a real engineer, learn Linux first. Shell on Ubuntu. Dotfiles. Package managers that feel “clean.” Come back to Windows later, if you must.
For some careers, that path is fine. For Windows-first juniors—students on school-issued Windows laptops, IT helpdesk tracks, .NET shops, enterprise ops—the advice often delays competence and sneaks in shame.
The hidden curriculum in “Linux first”
It implies:
- Windows shells are a side quest.
- CMD/PowerShell knowledge is provisional.
- Seriousness is measured by distro fluency.
Meanwhile their actual homework, internships, and first jobs keep handing them powershell.exe, Group Policy realities, and vendor .bat files. They’re told to practice somewhere else.
That’s not rigor. That’s misaligned reps.
What Windows-first learners actually need early
- Paths, permissions, and process basics on the OS they own.
- CMD survival skills for constrained machines.
- PowerShell object pipelines (not Bash cosplay).
- Encoding, Execution Policy, and PATH diagnostics they’ll hit in week two.
- Permission to use Git Bash/WSL as tools, not as moral upgrades.
You can teach excellent operator habits on Windows. Transfer to Linux later is real—and easier when the person already understands exit codes, redirection, and “read the error.”
Where the advice comes from (charitably)
Many mentors lived Linux-heavy careers. Cloud images are Linux. Tooling docs assume Bash. None of that makes “abandon your daily driver” good pedagogy for a junior who only has a Windows laptop and four hours a week.
Charity doesn’t require copying their biography.
A better framing than culture war
Don’t replace “Linux first” with “Windows forever.” Replace it with platform-honest sequencing:
- Gain fluency on the machine you can touch daily.
- Learn concepts that transfer (pipelines, processes, files, networking basics).
- Add Linux deliberately when your goals need it (cloud, containers, specific jobs).
Cross-training is strength. Displacement-as-identity is noise.
What I tell students now
If your world is Windows, practice Windows deeply. Use a browser-based or local lab that doesn’t pretend the shell is something else. When a README assumes Bash, translate consciously—or enter the Bash contract on purpose (Git Bash/WSL)—without calling it “real” and yourself “fake.”
Transfer that does work
Once someone can:
- read errors calmly,
- check exit codes,
- reason about paths and permissions,
- say which shell contract they’re in,
…then Linux practice accelerates. The transferable core is operator temperament plus fundamentals—not a specific distro badge.
Harm reduction if a mentor still pushes Linux-first
Negotiate a split: keep daily Windows practice; add a weekend Ubuntu VM or WSL track labeled as cross-training. Dual track beats abandonment. The injury happens when Windows practice stops entirely in the name of purity.
What I’m not claiming
I’m not claiming Linux skills are optional forever in cloud-heavy careers. I’m claiming sequencing and dignity matter. Windows-first juniors aren’t broken. Misaligned practice is.
Signal vs noise in mentor advice
Mentor advice often encodes the mentor’s job market year. Cloud-heavy 2018 advice isn’t automatically correct for a 2026 Windows helpdesk apprenticeship. Ask: “What OS will this student touch daily for the next ninety days?” Sequence to that. Add Linux as intentional breadth, not as an entrance exam to self-respect.
That’s the stance behind the Windows-friendly drills I work on in CMD Master: meet learners where their keyboards already are.
Discuss: Did “learn Linux first” help you, delay you, or both—and what does your first job actually run?
Top comments (1)
tr.ee/dev-to