This wiki is a place to collect, examine, and discuss software design knowledge in a systematic way. Currently there is a strong focus on (object-oriented) design principles (SOLID, GRASP, DRY, KISS, …). In the future other forms of experience reuse, like patterns and anti-patterns, will also be explored and interconnected with the principles.
Just like common solution schemes to recurring problems are documented using patterns, common assessment rules telling good solutions from bad ones can be described using principles. So principles are another form of experience reuse. There are dozens and maybe hundreds of such principles, some of which are examined here.
Principle languages similarly to pattern languages interconnect principles such that the consideration of one principle inevitably leads to other principles which are likely to be relevant in the same context. Currently there is one principle language described here (OOD Principle Language) and others will follow in the future.
We are currently creating playing cards with principles. While the wiki is best for looking up principles, cards are ideal for learning them. Furthermore the cards can be used during discussions about software design. The key rule is that you can only play one card at a time. As a result you have to think about the most convincing argument to play out first. So the quality of the argument counts and not the quantity.
Have a look at our Kickstarter campaign. It'll run until the end of July.
The validity a a certain principles is rarely disputed. But that different developers put different weight on them. Almost no-one would claim that KISS is not a valid principle. But there are ones who think GP is more important.
It turns out that developers can be characterized by which principles they favor when making design decisions. Understanding these different attitudes helps in communicating about design.
design-types.net describes a system of 16 design types characterizing developers in the aforementioned way. Each design type links back here to those principles each type favors or disregards. There is a questionnaire for testing yourself, a questionnaire for assessing colleagues and some statistics about those who already took part.
Start exploring the wiki with the full list of principles, the OOD Principle Language or the list of (principle) collections. This wiki is organized in several namespaces. One for each kind of experience reuse (principles, patterns, anti-patterns, …) plus some organizational ones. Get an overview of the different kinds of content in the wiki page about experience reuse or the sitemap.
Contributions to the wiki are welcome. Registration is not required (but appreciated). Almost all namespaces are world-editable. It's an open wiki so you are encouraged to share your knowledge.