Scribd
Upload
56 views

I Had A Little Dog That Said Bow-Wow! I Had A Little Cat That Said Meow-Meow!

The document provides guidelines for writing clear and readable code, stating that code should be simple rather than complex, avoid ambiguity, have a single obvious way to accomplish tasks, and use namespaces to avoid naming collisions. Special cases should not contradict the overall rules and errors should never go unreported. Readability and practicality are more important than purity or brevity.

Uploaded by

Mayur Patil
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
56 views

I Had A Little Dog That Said Bow-Wow! I Had A Little Cat That Said Meow-Meow!

The document provides guidelines for writing clear and readable code, stating that code should be simple rather than complex, avoid ambiguity, have a single obvious way to accomplish tasks, and use namespaces to avoid naming collisions. Special cases should not contradict the overall rules and errors should never go unreported. Readability and practicality are more important than purity or brevity.

Uploaded by

Mayur Patil
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Beautiful is better than ugly. I had a little dog that said bow-wow!

Although practicality beats purity. I had a little cat that said meow-meow!
Errors should never pass silently. Although never is often better than
*right* now.
Explicit is better than implicit.

Simple is better than complex.

Complex is better than complicated.


Flat is better than nested.
Unless explicitly silenced.

Sparse is better than dense.

Readability counts.
Special cases aren't special enough to break
the rules.

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.

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!

You might also like