4 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 1 other domain. Downstream, it holds up 2 domains.
4 topics · depth 0–6 of 16 · 4 internal links · 1 in · 3 out
Load-bearing links first. Each one says what in this domain rests on what outside it, and why.
1 link
Install system packages rests on Configure PATH
Installed binaries are only usable if PATH resolves them.
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 · procedural · unassisted · M01 §1.6
Installs with npm, global versus local
Package manager concepts transfer across ecosystems.
Depth 0 · procedural · unassisted · M01 §1.6
Installs with pip and reads requirements.txt
Package manager concepts transfer across ecosystems.
Depth 1 · representational · unassisted · M01 §1.6
Interprets package.json and pyproject.toml
A manifest describes what the package manager installs.
A manifest describes what the package manager installs.
Depth 6 · procedural · unassisted · M01 §1.6
Uses apt or brew for OS-level software
Configure PATH · Shell Configuration
Installed binaries are only usable if PATH resolves them.
Everything downstream that names an idea here as a prerequisite, grouped by where it lives.
2 links
Manage virtual environments rests on Manage Python packages
Environments isolate the installs you can already perform.
Structure a Python project rests on Read a dependency manifest
Project metadata lives in the manifest.
1 link
Containerize an application rests on Read a dependency manifest
An image installs a project's declared dependencies.
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