564
edits
| Line 1: | Line 1: | ||
== Preface == | |||
I take my software design and engineering philosophy partially from Python's famous 'import this': | |||
<pre> | |||
ddahl-t500 ~ % python | |||
Python 2.6.2 (release26-maint, Apr 19 2009, 01:56:41) | |||
[GCC 4.3.3] on linux2 | |||
Type "help", "copyright", "credits" or "license" for more information. | |||
>>> import this | |||
The Zen of Python, by Tim Peters | |||
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! | |||
</pre> | |||
I Love these sayings, following these precepts where appropriate will help you design systems that people want to use, and more importantly, want to extend. | |||
== Places Observations == | == Places Observations == | ||
edits