Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
http://www.python.org/dev/peps/pep-0020/
and some humor...
http://www.python.org/doc/humor/
Monday, September 16, 2013
Friday, September 13, 2013
This code sucks
"If you don’t code, imagine for a moment that you have been tasked with painting a wall in a house. The first thing you have to do is scrape the old peeling paint off the wall. When you do, you find deteriorating sheetrock. When you pull off a patch of sheetrock, you find rotting studs. When you cut out the studs, you get to the foundation and realize it’s gravel on quicksand. HEY!! WHEN ARE YOU GONNA BE DONE PAINTING THAT WALL?!?! Next we have to replace the light fixtures—please supply a time estimate."
Taken from this excelent article: http://steve.svbtle.com/this-code-sucks
Subscribe to:
Comments (Atom)