2018-11-09 16:59:21.566793+01 by Dan Lyke 2 comments
Assert yourself - some notes on programming defensively and hiding bugs. Some good stuff to think about, especially as we're moving into a world of high failure probablistic systems (eg: distributed and networked)
[ related topics: Software Engineering ]
comments in ascending chronological order (reverse):
#Comment Re: Assert Yourself made: 2018-11-10 01:13:08.217141+01 by: TheSHAD0W
Programming offensively would be even better... Rather than:
if (info == None)
return
instead, do:
assert info != None
This will rapidly tell you where your code went wrong.
#Comment Re: Assert Yourself made: 2018-11-11 03:19:53.152296+01 by: TheSHAD0W
... And I didn't even realize I'd literally done what the title of the article instructed...
We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.
Flutterby™ is a trademark claimed by
Dan Lyke for the web publications at www.flutterby.com and www.flutterby.net.