Design Rules
li#font {font-color: #000000}
Obscurely labelled as the The Zen of Python (by Tim Peters) offers some lighthearted pragmatism and welcome relief in the face of TheCheeseMovement.
- 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 [personally don't get the Dutch connection but it does apply to some i have in mind
] - 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[erm... well.. mmm...]
Continue reading » · Written on: 06-17-06 · No Comments »
Leave a Reply