The Spike Clock Is an Instrument
说明与用途
spike‑clock 脚本将每个阶段记录为 JSON 行,接近预算时发出警告,预算耗尽时停止编辑,提供透明的时间日志。
问题
A developer’s spike often ends without recording why it ran long, leading to untracked overruns and vague feelings of delay.
结果
The spike-clock script turns subjective time tracking into a reproducible log, enabling developers to see exactly when a spike exceeded its budget and to document the reason for overruns.
工作流
- 1. Create spike.yml with question, falsifier, budget, and artifacts.
2. Run
./spike-clock.sh startbefore writing the question. 3. Execute spike steps, calling./spike-clock.sh steporprobeas needed. 4. Run./probe-cold-start.sh <URL>to collect three spaced hits. 5. Summarise CSV into a verdict and write to spike.yml. 6. Run./spike-clock.sh verdictto log final outcome. 7. Review the generated JSONL log for budget compliance.
证据
A developer is ninety‑one minutes into a spike, and the original question … has quietly been replaced by a retry wrapper nobody asked for.
The instrument is small on purpose. A heartbeat script appends one JSON line every time the operator starts a phase, finishes a step, or runs a probe, and it refuses to stay silent about the budget.
The probe is where the clock earns its keep, because it converts a subjective impression of speed into three rows that either match the falsifier or do not.
- 记录日期: 2026-10-20T10:41:31.426Z