Why this lesson exists
You’ve spent hours writing a csperf lab, but the knowledge never leaves your desk. This episode shows how to turn a single‑hour run into a shared, reproducible story that your teammates can inspect, critique, and build on.
Recap — where we are in the series
Ep 1 — Why a Single ./a.out Time Misleads Your Performance Claims — Use csperf to capture reproducible evidence.
Ep 2 — Warm vs Cold: Why a Single Trial Misleads Performance Claims — Warm‑up and repeat are essential.
Ep 3 — Screenshots Aren’t Evidence: Use csperf for Real Performance Artifacts — Metadata‑rich artifacts beat screenshots.
Ep 4 — Comparing Across Machines: Why Metadata Matters in csperf — Machine metadata enables honest cross‑machine comparison.
Ep 5 — csperf: A Lightweight Observatory for Honest Performance Tracking — Observatory commands give quick evidence.
Ep 6 — csperf Doctor: First Command to Diagnose Toolchain Issues — Validate your toolchain before measuring.
Ep 7 — csperf list‑artifacts: Explore what…