Flutterby™! : Blarghs Rule of Programming #666

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Blarghs Rule of Programming #666

2013-01-31 16:53:08.182435+01 by ebwolf 0 comments

Never disable error messages in your static code checker. The people who maintain the static code checker probably know more about the cause and consequences of labeling something an error versus a warning versus not reporting at all. If it's an error, it's likely always a bad thing.

Found in the team .pylintrc:

disable E1101

E1101 is what you get when you make a typo in a function name from another module. I'm just glad I checked my email last night before bed and was able to fix my stupid mistake that was holding up the regression testing.

[ related topics: Interactive Drama Mathematics Furniture hubris ]

comments in descending chronological order (reverse):

Comment policy

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.