https://github.com/checkcheckzz/system-design-interview
Tuesday, May 14, 2019
Sunday, May 12, 2019
Be pythonic
The Zen of Python
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!
See https://legacy.python.org/dev/peps/pep-0020/
Python Code Style
https://docs.python-guide.org/writing/style/
Pytonic
"Pythonic" means something like "idiomatic Python"
The sense of how to use Python the right way.
The idiom the Python language encourages.
To be Pythonic is to use the Python constructs and datastructures with clean, readable idioms.
Exploiting the features of the Python language to produce code that is clear, concise and maintainable.
https://blog.startifact.com/posts/older/what-is-pythonic.html
Subscribe to:
Posts (Atom)
