Principles Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Experience Reuse ======

This wiki is essentially about experience reuse. Some developers made some experience, gained some knowledge, and got expertise. Then they codified this knowledge as patterns, anti-patterns, principles and the like. This wiki collects these and describes and examines them in a structured way.

The following table shows the different forms of codified experience:

^   Form ^ Description ^ Notable [[Collections:]] ^ List ^
^   [[glossary:Principles]] | Rules of thumb telling good solutions from bad solutions | [[collections:OOD Principle Language|OOD-PL]], [[collections:SOLID]], [[collections:GRASP]], ... | [[principles:|list]] |
^   [[glossary:Patterns]] | Known good solutions | [[collections:GoF Patterns|GoF]], [[collection:POSA1 Patterns|POSA1]], ... | [[patterns:|list]] |
^   [[glossary:Anti-Patterns]] | Known bad solutions | [[collection:Code Smells in "Refactoring"|Fowler]], ... | [[anti-patterns:|list]] |
^   [[glossary:Refactorings]] | Procedures for transforming solutions structurally (typically from bad to good) | [[collection:Refactorings in "Refactoring"|Fowler]], ... | [[refactorings:|list]] |
^   Terms | Any terms used in software development | --- | [[Glossary:|list]] |
^   [[glossary:Non-Principles]] | Rules which look like principles but are not principles in the sense discussed here. | --- | [[non-principles:|list]] |

Currently this wiki has a strong focus on principles. In the future the wiki will extend in order to describe also the other forms and more than that: interconnect them.
  * The advantages and disadvantages of (anti-)patterns can be described using principles
  * Refactorings are cures for anti-patterns
  * Refactorings may be used to transform a solution in a way that adheres more to a certain principle
  * Refactorings may lead to certain patterns
  * ...