Re:Simple, correct, fast: in that order
by koolba on Monday July 09, 2018 @09:57AM
(#17490161)
My read of this that simple means not necessarily handling all possible edge cases yet having enough of a skeleton in place that the core functionality is there. Correct is extending (or replacing) that skeleton with coverage for all cases.
[ Parent
| on HN ]
Edge cases? You mean we can't test for leap year by simply checking if the year is a multiple of four?
No that’s a silly example.
I meant more for dealing with edge cases like an external API invocation failing. A final “correct” implementation would need to handle failures but an initial simple one would only handle success.