Hacker News Reader

For "things that should not happen" and that might indeed propagate yuck further into the system, I prefer a brittle approach to stop THAT path ASAP and log it well and get it fixed.

Maybe allow other unrelated things to continue per "make -k" though, since we'd probably like to get as much as possible done anyway, safely.

View on HN

I do think that we need to pick one or the other approach, and not mix them, as mixing them at engineer's discretion just opens to unforeseeable outcomes, e.g. Engineer making the choice without understanding the implications or the code evolving to be sensitive from non-sensitive over time.

Different errors will warrant different approaches. Very much an engineering decision case by case, maybe with some senior engineering oversight where not clearcut. Insisting on all-brittle or all-muddle-through upfront is unlikely to be anything like optimal. IMHO, obvs.

But if the error should not happen, eg invalid types, stop that line of activity ASAP.

Reply on news.ycombinator.com