2 micro-topics in Engineering Practice, 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.
2 topics · depth 0–1 of 16 · 1 internal link · 1 in · 1 out
Load-bearing links first. Each one says what in this domain rests on what outside it, and why.
1 link
Diagram a system before building it rests on Write user stories with acceptance criteria
A diagram is easier to draw once the requirement is stated.
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 · representational · scaffolded · M07 §7.2
Draws components and their interactions
Write user stories with acceptance criteria · Requirements
A diagram is easier to draw once the requirement is stated.
Depth 1 · representational · scaffolded · M07 §7.2
Captures context, decision and consequences
Diagram a system before building it
A decision record documents a choice made during design.
Everything downstream that names an idea here as a prerequisite, grouped by where it lives.
1 link
Handle a system design interview rests on Diagram a system before building it
A design interview asks you to do this aloud.
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