free hosting   image hosting   hosting reseller   online album   e-shop   famous people

 

Design Principles

My own:

Even though I say these are my own, some of them are what I've read, and merely translated to myself

• Don't reinvent the wheel, unless it's square
• Don't make useless objects(java should be famous for this)
• Test every feature before moving on to the next
• Name things like you name children, with premiditation
• If it's been solved twice, consider solving it again
• If it's been solved 100's of times, don't solve it again
• If its very general, It's generally useless
• When commenting, don't state the obvious
• Don't solve something before googling for it first

Some other cool ones

• Provide mechanism, not policy
• “Premature optimization is the root of all evil.” - Donald E. Knuth
• Principal Of least Astonishment(youll find this one in the FreeBSD handbook)

The Zen of Python, by Tim Peters

"I took this from typing import this in the python command prompt"

• 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!