There are still many principle descriptions that are only stubs, which means major parts are missing: List of Stubs

• GRASP
• Robert C. Martin's Principle Collection
• Unix Philosophy (Eric S. Raymond)
• Principles in "Object-Oriented Software Construction"
• Principles in "The Pragmatic Programmer"

• Don't Write Code To Find Code – origin unknown
• Minimize Intellectual Distance – generalization of MP; see also Davis: “201 Principles of Software Development”
• You Ain't Gonna Need It (YAGNI) – see KISS
• Once And Only Once (OAOO) – see DRY
• http://en.wikipedia.org/wiki/Composition_over_inheritance
• Fowler's First Law of Distributed Object Design (see “Patterns of Enterprise Pattlication Architecture p. 89”)
• Form follows function

• Portland Pattern Repository
  • Don't Create Verb Classes
  • Don't Name Classes Object Manager Handler Or Data (see also Clean Code p. 25)
  • Behavioral Completeness http://c2.com/cgi/wiki?PrinciplesOfObjectOrientedDesign
  • Principle of Essential Representation http://c2.com/cgi/wiki?PrinciplesOfObjectOrientedDesign
  • … http://c2.com/cgi/wiki?search=rule http://c2.com/cgi/wiki?search=principle
• Unix Philosophy
  • http://en.wikipedia.org/wiki/Unix_philosophy
  • http://www.catb.org/~esr/writings/taoup/html/ch01s06.html
• Joshua Bloch: How to Design a Good API & Why it Matters
  • alternative version of the talk: http://www.youtube.com/watch?v=aAb7hSCtvGw
  • slides: http://lcsd05.cs.tamu.edu/slides/keynote.pdf
  • principle-like summary: http://www.infoq.com/articles/API-Design-Joshua-Bloch
• 97 things
  • http://softarch.97things.oreilly.com/wiki/index.php/97_Things_Every_Software_Architect_Should_Know_-_The_Book
  • http://softarch.97things.oreilly.com/wiki/index.php/Other_Things_Software_Architects_Should_Know
  • http://programmer.97things.oreilly.com/wiki/index.php/Contributions_Appearing_in_the_Book
  • http://programmer.97things.oreilly.com/wiki/index.php/Other_Edited_Contributions
• The Zen of Python
• Clean Code
  • LeBlanc's Law: Later equals never
  • Blocks should be one line long (p. 35)
  • Functtion names should not be just a restatement of the function implementation (p. 36)
  • Stepdown Rule (p. 136)