Phil Haack has a great post listing 19 different laws of software development. Everything from Postels Law, to The Pareto Principle (a.k.a. the 80/20 rule), to Wirth’s Law (software gets slower faster than hardware gets faster), to Sturgeon’s Revelation, even Murphy’s Law gets a mention.
One I hadn’t heard of before, but which definitely marries with my experience:
“Conway’s Law: Any piece of software reflects the organisational structure that produced it.”
What’s the shape of your org chart? And how is that manifesting itself in your code?
UPDATE: Wikipedia has a much longer list, if you’re into this sort of thing. :-)