<\/a>#Mastery08<\/a> <\/span> <\/span><\/span> <\/span><\/span> <\/span><\/a>#TC1014<\/a> <\/span> <\/span>@PablO_CVi<\/span><\/a><\/p>\n Many years ago a Pythoneer Tim Peters succinctly channels the BDFL’s guiding principles for Python’s design into 20 aphorisms, only 19 of which have been written down. <\/p>\n “Beautiful is better than ugly. <\/p>\n Explicit is better than implicit. <\/p>\n Simple is better than complex. <\/p>\n Complex is better than complicated. <\/p>\n Flat is better than nested. <\/p>\n Sparse is better than dense. <\/p>\n Readability counts. <\/p>\n Special cases aren’t special enough to break the rules. <\/p>\n Although practicality beats purity. <\/p>\n Errors should never pass silently. <\/p>\n Unless explicitly silenced. <\/p>\n In the face of ambiguity, refuse the temptation to guess. <\/p>\n There should be one– and preferably only one –obvious way to do it. <\/p>\n Although that way may not be obvious at first unless you’re Dutch. <\/p>\n Now is better than never. Although never is often better than *right* now. <\/p>\n If the implementation is hard to explain, it’s a bad idea. <\/p>\n If the implementation is easy to explain, it may be a good idea. <\/p>\n Namespaces are one honking great idea — let’s do more of those!”(2004, p1).<\/p>\n Recuperado de: https:\/ <\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":" #Mastery08 … Continue reading <\/pre>\n