The dependency with one maintainer, and the week it went away
Bus factor is a property of your supply chain, not just your team.
architecture
70 posts
It was not a timezone bug, it was a day-boundary bug
Storing UTC is necessary and not sufficient. Any report bucketed by day needs a declared zone.
Adding a parameter with a default broke the ABI
Source compatibility and binary compatibility are different guarantees, and a default argument preserves only the first.
The null that meant three different things
Not-yet-loaded, absent, and explicitly-cleared share one representation, and the UI has to guess.
The queue had no maximum, so the failure was memory and not latency
An unbounded buffer converts a throughput problem into an out-of-memory crash.
The webhook that arrived twice, and the order that shipped twice
At-least-once is the contract every provider offers. Your handler is where exactly-once gets built.
Streaming a response changes your UI contract, not just your latency
Partial output means every intermediate state is user-visible, including the wrong ones.
The interface with one implementation, and the three years it cost
An abstraction written for a second implementation that never arrived is pure indirection.
The architecture decision nobody wrote down, re-litigated four times
Without the rejected options and the reason, every new engineer re-opens the question.
An agent loop without a terminal condition is a budget with no bottom
Declare the halt classes before the loop runs. 'Until it looks done' is not a condition.
The cache that returned someone else's data
A cache key missing the tenant is a data leak with a 100% hit rate.
Every timeout you set independently adds up to one that is wrong
Three services with 30-second timeouts give the user 90 seconds.