Most linked-to pages
From CSSEMediaWiki
Showing below up to 50 results starting with #251.
View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)
- User:Johannes Pagwiwoko (9 links)
- Class hierarchies should be deep and narrow (9 links)
- Erich Gamma (9 links)
- Goto considered harmful (9 links)
- William Brown 1998 (9 links)
- Analysis patterns (9 links)
- Interface should be dependent on model (8 links)
- Architectural patterns (8 links)
- Hillside Group (8 links)
- Defer identification of state variables pattern (8 links)
- Resources (8 links)
- Avoid interface bloat (8 links)
- God class (8 links)
- Many to many association idiom (8 links)
- Avoid multiple inheritance (8 links)
- User:Yugan Yugaraja (8 links)
- The top of the class hierarchy should be abstract (8 links)
- User:Paul Williams (8 links)
- Avoid equals (8 links)
- Avoid becomes (8 links)
- Common closure principle (8 links)
- User:Douglas Wall (8 links)
- Reduce the size of methods (8 links)
- Split large classes (8 links)
- User:BenjaminTaylor (8 links)
- Keep accessors and mutators separate (7 links)
- MVC (7 links)
- User:Jenny Harlow (7 links)
- Encapsulate concrete state pattern (7 links)
- Class Encapsulation (7 links)
- Johnson and Foote's heuristics (7 links)
- Reduce the number of arguments (7 links)
- JUnit (7 links)
- Double Dispatch (7 links)
- Beware of many accessors (6 links)
- Named constants (6 links)
- Robert Cecil Martin 1996b (6 links)
- OO wisdom (6 links)
- Big ball of mud (6 links)
- Separate methods that do not communicate (6 links)
- Stable dependencies principle (6 links)
- A class should not depend on its users (6 links)
- No concrete base classes (6 links)
- Inheritance for implementation (6 links)
- OO gurus (6 links)
- Law of demeter (6 links)
- Parse tree design (6 links)
- Favour deep hierarchies (6 links)
- Minimize number of methods (6 links)
- User:BenMcDonald (6 links)
