The Zen of Python
The Zen of Python
>Beautiful is better than ugly.
>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.
>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!
Related Pages
- →modeling×abstraction×pattern_discovery×(1.4)_what_is_abstraction?×modeling_or_abstraction_is_a_task_to_stack_boxes×abstract×stack×boxes×information_gathering×put_a_box_in_the_air×foundation×metaphor×pattern×(0.2.2) Compare and find patterns×model×concrete×python×list×tuple×search_engine→
- →douglas_carl_engelbart×augmenting_human_intellect:_a_conceptual_framework×grasp×concept×explicit×handle×symbol×(4.5.2.3)_get_the_tools_of_thinking×6.2.6_summary_of_verbalization×(column)_naming_the_pattern→
"Engineer's way of creating knowledge" the English version of my book is now available on [Engineer's way of creating knowledge]
(C)NISHIO Hirokazu / Converted from [Scrapbox] at [Edit]