Türker Yıldırım
Reproducing a problem with a header is far better than “try again while I watch the dashboard”, and it must not be a way for anybody to trace…
Moving failed messages out of the main flow keeps the system healthy and does nothing on its own about the messages. The replay path is the part that…
It passed on staging four times and failed in production four times. The same code, a different outcome, and five differences nobody had enumerated.
A trace that ends when a job is enqueued covers the fast half of the work and none of the half that fails. The identifier has to be…
“Take the morning if you need it” puts the judgement on the person who was woken up, at the moment they are least able to make it. Making…
A person woken at three in the morning should not be searching a wiki, and an alert without a runbook link is a decision deferred to somebody asleep.…
A report query with eleven joins, run on every dashboard load. One model cannot be shaped for both writing and reading past a certain size.
A grep that needed three regular expressions and a sort. A log line written for a person to read at leisure is not a record you can query.
A price change that took eleven days to reach one page. Three caches, and only one of them was being cleared.
3.1 lands in February with real JSON Schema. Generating docs from code fixes half the problem; making the document the contract fixes the other half.