3 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 1 domain.
3 topics · depth 0–1 of 16 · 2 internal links · 1 in · 1 out
Load-bearing links first. Each one says what in this domain rests on what outside it, and why.
1 link
Inspect running processes rests on Inspect file contents
Reading process output is reading structured text.
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.7
Reads ps, top and htop output
Inspect file contents · Filesystem
Reading process output is reading structured text.
Depth 0 · procedural · unassisted · M01 §1.7
Uses df, du and free to find pressure
Resource inspection is the same class of system query.
Depth 1 · procedural · unassisted · M01 §1.7
Backgrounds, foregrounds and kills processes
You signal processes you have identified.
Everything downstream that names an idea here as a prerequisite, grouped by where it lives.
1 link
Handle exit codes and errors rests on Control jobs and signals
Exit codes are the signal side of process control.
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