Kickingbear: Regarding Simplicity:

Always implement the simplest possible solution that fits your understanding of the problem space modulated by your anticipation of the inputs you'll be dealing with.

Big words (for me at least), but my friend (and noted Canadian) Guy English goes on to explain something which I've been trying for years to tell peers and fellow co-workers (way back when I was working for The Man). There are many things I'd like to quote, but I'd end up just reprinting his whole (and lovingly short) post. Here's just one more bit:

The trick is never in building the best possible implementation — the trick is in building the implementation that will provide the best possible future.

If you're a coder, please read it. And when you're done with that, find a copy of The Pragmatic Programmer and read that as well.

And while I'm on the subject, here's a bonus quote from Brian Kernighan:

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.