--Originally published at Hector Martinez Alcantara
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!
What’s this for me?
Its an ideal form of programming not only to python, for all the languages, but it’s very ideal, you often have to use other methods to do a code, usually because of the time.
The problem maybe it’s not very difficult to solve with the zen of python, but the time is running out and other solutions solve the problem easily and quickly, so you have to finish it.
Thats my opinion, tan tan.
Images from:
https://pbs.twimg.com/profile_images/556094082456383489/jfoAAmDG.png
https://upload.wikimedia.org/wikipedia/commons/thumb/c/c3/Python-logo-notext.svg/2000px-Python-logo-notext.svg.png
