13 micro-topics in Systems & Tooling, each with the evidence that proves you have it and the written reason behind every link. Before you start, it rests on 2 other domains. Downstream, it holds up 5 domains.
13 topics · depth 2–6 of 16 · 12 internal links · 2 in · 6 out
Load-bearing links first. Each one says what in this domain rests on what outside it, and why.
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
Configure Git and ignore rules rests on Write aliases and shell functions
Git aliases are the same idea as shell aliases.
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 2 · conceptual · unassisted · M03 §3.1
Knows working directory, staging, commits, HEAD and refs
Navigate the filesystem from the command line · Filesystem
Git's working directory is a filesystem.
Depth 3 · procedural · unassisted · M03 §3.2
Uses add, add -p and writes atomic messages
Explain Git's object and reference model
Staging and committing only make sense against the object model.
Depth 3 · procedural · unassisted · M03 §3.3
Creates and switches branches with a naming convention
Explain Git's object and reference model
A branch is a reference, which is part of the object model.
Depth 4 · procedural · unassisted · M03 §3.2
Navigates log, diff and status
History is the record of commits you made.
Depth 4 · conceptual · unassisted · M03 §3.4
Understands fast-forward and three-way merges
Merging integrates branches.
Depth 4 · procedural · unassisted · M03 §3.5
Works with origin and upstream across forks
Remotes track branches on another machine.
Depth 4 · procedural · unassisted · M03 §3.7
Sets identity, aliases, .gitignore and .gitattributes
Ignore rules matter once you are choosing what to stage.
Write aliases and shell functions · Shell Configuration
Git aliases are the same idea as shell aliases.
Depth 5 · conceptual · unassisted · M03 §3.2
Chooses between restore, reset and revert
Undoing requires reading what you are undoing.
Depth 5 · procedural · scaffolded · M03 §3.4
Applies rebase and interactive rebase deliberately
Rebasing is the alternative to a merge you already understand.
Depth 5 · procedural · unassisted · M03 §3.4
Reads conflict markers and picks the right resolution
Conflicts arise from integration.
Depth 5 · meta · unassisted · M03 §3.5
Writes reviewable PRs and gives useful feedback
A pull request proposes merging a pushed branch.
Depth 5 · procedural · guided · M03 §3.6
Binary-searches history for the breaking commit
Bisecting searches history.
Depth 6 · procedural · scaffolded · M03 §3.6
Rescues work from awkward states
Recovery extends the undo operations to harder cases.
Everything downstream that names an idea here as a prerequisite, grouped by where it lives.
2 links
Automate workflows with CI rests on Manage remotes
Workflows are triggered by pushes to a remote.
Gate merges on checks rests on Open and review pull requests
Checks block a merge.
1 link
Build a portfolio of shipped work rests on Open and review pull requests
The portfolio is merged work.
1 link
Review code for correctness and risk rests on Open and review pull requests
Review happens on pull requests.
1 link
Version prompts as templates rests on Stage and commit changes
Versioning prompts requires version control.
1 link
Version schema changes with migrations rests on Stage and commit changes
Migrations are versioned artifacts, and versioning habits carry over.
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