4 ms·
That's such a bad take after reading the article. If you're going to write a system that preallocates and is based on hard assumptions about max size - the pani
by rafaelmn 11mo ago
That's such a bad take after reading the article. If you're going to write a system that preallocates and is based on hard assumptions about max size - the panic/unwrap approach is reasonable.
The config bug reaching prod without this being caught and pinpointed immediately is the strange part.
- kevin_thibedeau 11mo agoIt's reasonable when testing protocols exercise the panic scenario. This is the problem with punting on error recovery. Nobody checks faults that propagate across domains of responsibility.
- AtNightWeCode 11mo agoExactly. The newbie mistake in SQL is also way worse than this. But the whole design is also bad. Clearly implementing things at the wrong place. And, it took like over an hour between the problem started til my sites went down. That is just crazy.
- thatoneengineer 11mo agoI agree there's no way to soft-error this, though "truncate and raise an alert" is arguably the better pattern.