From 5fd154f3fdc69f03929d384977d159db7d0d43db Mon Sep 17 00:00:00 2001
From: bt3gl <1130416+bt3gl@users.noreply.github.com>
Date: Tue, 26 Nov 2019 22:18:50 -0800
Subject: [PATCH] =?UTF-8?q?=F0=9F=8C=B2The=20Zen=20of=20Python?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 README.md | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/README.md b/README.md
index 1da4015..3a6c8a0 100644
--- a/README.md
+++ b/README.md
@@ -14,6 +14,32 @@ It's loosely based on the exercises & theory from the book [Cracking the Code In
 Even after the years, this book can be useful if you are aiming to learning Python and/or practicing for software engineering interviews.
 
 
+---
+
+## [The Zen of Python](https://www.python.org/dev/peps/pep-0020/)
+
+```
+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!
+```
+
 -----
 
 This work is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License](http://creativecommons.org/licenses/by-sa/4.0/).