Episode Details

Episode 5 of the build series confronts the central question: what does this component do that nothing you already own can do? We introduce the workload map—a file that justifies every hardware purchase by tracing each part back to a real workload. The philosophy is ruthless: requirements come from code, logs, or actual instrumentation. Every part must survive the question, or it's just a purchase looking for a reason. 00:00 - Introduction & Episode Overview 02:45 - The Build Series Context 04:30 - The Central Philosophy: A Build is Only Defensible if it Traces 08:15 - Shopping Carts vs. Arguments 11:00 - The Workload Map File 13:45 - Requirements, Measurements & the Legend 16:20 - Building with Intention --- Sources & further reading: • ComputerBuild repo — workloads/workload-map.md (the stated purpose, the (measured) legend, sections A and D) • ComputerBuild repo — inventory/machines.md, cross-cutting section ("a GPU wouldn't accelerate an existing local practice; it would create one") • ComputerBuild repo — decisions/decision-log.md, D3 (one card not two; refuted dual-GPU benchmarks; the honest "unanswered" framing) • ComputerBuild repo — decisions/decision-log.md, P11 (the $3,000 ceiling, still open) This podcast episode was fully generated by AI — research, script, voices, and production. Built with Claude, Piper TTS, and automated pipeline tooling.