4 micro-topics in Reliability & Operations, 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 3 domains.
4 topics · depth 0–1 of 16 · 3 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
Reason about the testing pyramid rests on Write and call functions
Test placement is easier once you have code worth testing.
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 · M11 §11.1
Places unit, integration and end-to-end tests
Write and call functions · JavaScript Core
Test placement is easier once you have code worth testing.
Depth 0 · meta · scaffolded · M11 §11.1
Removes nondeterminism from a test suite
Both are lessons about what a green suite does not prove.
Depth 1 · meta · scaffolded · M11 §11.1
Drives design from a failing test
Reason about the testing pyramid
TDD assumes you know what kind of test to write.
Depth 1 · conceptual · unassisted · M11 §11.1
Knows what coverage does and does not prove
Reason about the testing pyramid
Coverage is interpreted against test type.
Everything downstream that names an idea here as a prerequisite, grouped by where it lives.
1 link
Test Python with pytest rests on Reason about the testing pyramid
The same placement logic applies.
1 link
Unit test JavaScript rests on Reason about the testing pyramid
Unit tests are the base of the pyramid.
1 link
Build an evaluation dataset rests on Reason about the testing pyramid
An eval set is a test suite for a nondeterministic system.
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