Comments on: Correctness vs Robustness http://richarddingwall.name/2010/02/10/correctness-vs-robustness/ The adventures of a young kiwi software developer in London Thu, 10 May 2012 16:20:46 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Tungano http://richarddingwall.name/2010/02/10/correctness-vs-robustness/comment-page-1/#comment-12817 Tungano Fri, 26 Feb 2010 17:21:34 +0000 http://richarddingwall.name/?p=1552#comment-12817 Hey Richard, yes of course it's a bug. Just saying that when implementing robustness you have to be very careful you don't provide robustness against bugs accidentally. It requires very explicit checking of what you want to be robust against. Correctness first and then adding robustness is safest in my eyes. I am not so sure if one actually has to choose between one or the other, robustness typically happens at the presentation logic level. Hey Richard, yes of course it’s a bug. Just saying that when implementing robustness you have to be very careful you don’t provide robustness against bugs accidentally. It requires very explicit checking of what you want to be robust against.
Correctness first and then adding robustness is safest in my eyes. I am not so sure if one actually has to choose between one or the other, robustness typically happens at the presentation logic level.

]]> By: Richard http://richarddingwall.name/2010/02/10/correctness-vs-robustness/comment-page-1/#comment-12803 Richard Wed, 24 Feb 2010 09:19:07 +0000 http://richarddingwall.name/?p=1552#comment-12803 Tungano : Encountering an internal error like that and proceeding anyway is not robust... that's just a bug ! Tungano : Encountering an internal error like that and proceeding anyway is not robust… that’s just a bug !

]]> By: Tungano http://richarddingwall.name/2010/02/10/correctness-vs-robustness/comment-page-1/#comment-12800 Tungano Tue, 23 Feb 2010 18:10:08 +0000 http://richarddingwall.name/?p=1552#comment-12800 Robustness can be very risky and when implemented poorly will serve as 'sweaping dirt under the rug". E.g a webpage responding with "Thank you for your order!" while nothing was processed. The code crapped out during processing somewhere: customer will be billed, nothing will be delivered. Stuff like that... Best to be correct 1st and then stack up to robustness. Robustness can be very risky and when implemented poorly will serve as ‘sweaping dirt under the rug”.

E.g a webpage responding with “Thank you for your order!” while nothing was processed.
The code crapped out during processing somewhere: customer will be billed, nothing will be delivered. Stuff like that… Best to be correct 1st and then stack up to robustness.

]]> By: Martin Aatmaa http://richarddingwall.name/2010/02/10/correctness-vs-robustness/comment-page-1/#comment-12758 Martin Aatmaa Thu, 18 Feb 2010 02:14:45 +0000 http://richarddingwall.name/?p=1552#comment-12758 Excellent and informative analysis. Thank you Richard! Excellent and informative analysis. Thank you Richard!

]]> By: Chris http://richarddingwall.name/2010/02/10/correctness-vs-robustness/comment-page-1/#comment-12757 Chris Thu, 18 Feb 2010 01:49:40 +0000 http://richarddingwall.name/?p=1552#comment-12757 Good post man. A further issue with Robustness that I find is that while its expected, it can be very difficult to specify and budget against, especially when many edge cases are not found until a user brings down your application. Good post man. A further issue with Robustness that I find is that while its expected, it can be very difficult to specify and budget against, especially when many edge cases are not found until a user brings down your application.

]]>