Timeline for Fail fast is brittle
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 19 at 12:02 | comment | added | Martin Maat | Why is the comment I responded to deleted? I found my own comment from a couple of days earlier deleted too. Is SESE playing YouTube these days? It smells like AI and it better end soon. | |
| Jul 18 at 21:56 | comment | added | Martin Maat | @IvovanderVeeken Failing fast can be more efficient. Like early exit. The alternative is to follow a fixed order of steps regardless, perhaps producing results that may need to be discarded later. The latter could be cleaner. If the fail is rare one might prefer the clean approach. Like exceptions (as an error handling mechanism) are expensive but you don't care because they are, well, exceptional. | |
| Jul 14 at 11:33 | history | answered | Martin Maat | CC BY-SA 4.0 |