9 micro-topics in Systems & Tooling, each with the evidence that proves you have it and the written reason behind every link. Nothing outside this domain sits under it — you can start here. Downstream, it holds up 8 domains.
9 topics · depth 0–4 of 16 · 8 internal links · 0 in · 9 out
Load-bearing links first. Each one says what in this domain rests on what outside it, and why.
Nothing outside this domain sits under it. It is an entry point — you can start here.
In prerequisite order. Each idea names the artifact that closes it, the market demand that put it on the map, and what it stands on.
Depth 0 · conceptual · unassisted · M01 §1.1
Knows what lives in /, /home, /usr, /etc, /var and why
Depth 1 · procedural · unassisted · M01 §1.1
Moves between directories with cd, pwd and ls confidently
Read the Unix directory hierarchy
You cannot move through a structure you cannot describe.
Depth 2 · conceptual · unassisted · M01 §1.1
Chooses the right path form for the situation
Navigate the filesystem from the command line
Path forms only matter once you are moving between directories.
Depth 2 · procedural · unassisted · M01 §1.2
Uses touch and mkdir -p to build structure
Navigate the filesystem from the command line
You create files somewhere, and you have to get there first.
Depth 2 · procedural · unassisted · M01 §1.2
Reads with cat, less, head, tail and follows with tail -f
Navigate the filesystem from the command line
You open files by path.
Depth 3 · procedural · unassisted · M01 §1.2
Applies cp and mv, including recursively
Moving and copying assume files exist to move.
Depth 3 · procedural · unassisted · M01 §1.2
Searches with find, locate, which and whereis
Distinguish absolute from relative paths
Search returns paths you have to be able to interpret.
Depth 4 · conceptual · unassisted · M01 §1.2
Understands what rm -rf does before running it
Copy, move and rename from the shell
Deletion is the destructive end of the same file operations.
Everything downstream that names an idea here as a prerequisite, grouped by where it lives.
2 links
Search text with grep rests on Inspect file contents
Filtering text assumes you can already read the file.
Count and compare text rests on Inspect file contents
Counting operates on files you can already open.
1 link
Connect to remote systems with SSH rests on Navigate the filesystem from the command line
A remote session drops you into a filesystem you must navigate.
1 link
Explain shell startup files rests on Work with hidden files and dotfiles
Startup files are dotfiles.
1 link
Reason about stdin, stdout and stderr rests on Inspect file contents
Streams are the abstraction behind reading and writing files.
1 link
Explain Git's object and reference model rests on Navigate the filesystem from the command line
Git's working directory is a filesystem.
1 link
Navigate an editor without the mouse rests on Navigate the filesystem from the command line
Editor navigation mirrors filesystem navigation with a UI on top.
1 link
Route with the file system rests on Read the Unix directory hierarchy
File-based routing rewards filesystem intuition.
1 link
Inspect running processes rests on Inspect file contents
Reading process output is reading structured text.
Retool. Retrain. Relaunch.
375 ideas. 17 weeks. No tuition, ever.
Vets Who Code is a veteran-run 501(c)(3). The accelerator is free, remote, and we don’t take a share of your first paycheck.
Free · Remote · 17 weeks · EIN 86-2122804