Most linked-to pages

From CSSEMediaWiki
Jump to: navigation, search

Showing below up to 250 results starting with #251.

View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)

  1. Analysis patterns‏‎ (9 links)
  2. Presentation separation idiom‏‎ (9 links)
  3. Ken Auer‏‎ (9 links)
  4. Object Encapsulation‏‎ (9 links)
  5. Premature optimization‏‎ (9 links)
  6. Beware singletons‏‎ (9 links)
  7. Many to many association idiom‏‎ (8 links)
  8. Avoid multiple inheritance‏‎ (8 links)
  9. User:Yugan Yugaraja‏‎ (8 links)
  10. The top of the class hierarchy should be abstract‏‎ (8 links)
  11. Avoid becomes‏‎ (8 links)
  12. Avoid equals‏‎ (8 links)
  13. User:Paul Williams‏‎ (8 links)
  14. Common closure principle‏‎ (8 links)
  15. Reduce the size of methods‏‎ (8 links)
  16. User:Douglas Wall‏‎ (8 links)
  17. Split large classes‏‎ (8 links)
  18. User:BenjaminTaylor‏‎ (8 links)
  19. Hillside Group‏‎ (8 links)
  20. Interface should be dependent on model‏‎ (8 links)
  21. Architectural patterns‏‎ (8 links)
  22. Resources‏‎ (8 links)
  23. Avoid interface bloat‏‎ (8 links)
  24. Defer identification of state variables pattern‏‎ (8 links)
  25. God class‏‎ (8 links)
  26. MVC‏‎ (7 links)
  27. Encapsulate concrete state pattern‏‎ (7 links)
  28. Class Encapsulation‏‎ (7 links)
  29. Johnson and Foote's heuristics‏‎ (7 links)
  30. Reduce the number of arguments‏‎ (7 links)
  31. Double Dispatch‏‎ (7 links)
  32. JUnit‏‎ (7 links)
  33. Keep accessors and mutators separate‏‎ (7 links)
  34. User:Jenny Harlow‏‎ (7 links)
  35. Inheritance for implementation‏‎ (6 links)
  36. Parse tree design‏‎ (6 links)
  37. Law of demeter‏‎ (6 links)
  38. User:John Hofman‏‎ (6 links)
  39. Favour deep hierarchies‏‎ (6 links)
  40. Minimize number of methods‏‎ (6 links)
  41. User:BenMcDonald‏‎ (6 links)
  42. User:Josh Oosterman‏‎ (6 links)
  43. Object pool‏‎ (6 links)
  44. Equals vs the Encapsulation Boundary‏‎ (6 links)
  45. Beware inheritance over composition‏‎ (6 links)
  46. Common reuse principle‏‎ (6 links)
  47. Martin Fowler 2003‏‎ (6 links)
  48. Test Driven Development‏‎ (6 links)
  49. Robert Cecil Martin 1996b‏‎ (6 links)
  50. OO wisdom‏‎ (6 links)
  51. Beware of many accessors‏‎ (6 links)
  52. Named constants‏‎ (6 links)
  53. Big ball of mud‏‎ (6 links)
  54. A class should not depend on its users‏‎ (6 links)
  55. Separate methods that do not communicate‏‎ (6 links)
  56. Stable dependencies principle‏‎ (6 links)
  57. OO gurus‏‎ (6 links)
  58. No concrete base classes‏‎ (6 links)
  59. User:Michael Madamba‏‎ (5 links)
  60. OO tools‏‎ (5 links)
  61. User:Joey Scarr‏‎ (5 links)
  62. User:Michael Price‏‎ (5 links)
  63. The Alexander conspiracy‏‎ (5 links)
  64. No Global Variables‏‎ (5 links)
  65. User:Mujtaba Alshakhouri‏‎ (5 links)
  66. 427 assessment‏‎ (5 links)
  67. Dependency injection‏‎ (5 links)
  68. User:Stephen Fitchett‏‎ (5 links)
  69. User:Nelson Shaw‏‎ (5 links)
  70. Patterns‏‎ (5 links)
  71. One responsibility rule‏‎ (5 links)
  72. Robert Cecil Martin 2003‏‎ (5 links)
  73. UML‏‎ (5 links)
  74. User:Linda Pettigrew‏‎ (5 links)
  75. Hide your decisions‏‎ (5 links)
  76. Favour composition over inheritance‏‎ (5 links)
  77. Enum idiom‏‎ (5 links)
  78. Jim Coplien‏‎ (5 links)
  79. Reuse release equivalence principle‏‎ (5 links)
  80. Model View Controller‏‎ (5 links)
  81. User:Jenny Harlow/Design study‏‎ (5 links)
  82. Option-operand separation‏‎ (5 links)
  83. User:James Ashford‏‎ (5 links)
  84. Bertrand Meyer‏‎ (5 links)
  85. Implement behavior with abstract state pattern‏‎ (5 links)
  86. Wals library‏‎ (5 links)
  87. Abstract classes should be base classes‏‎ (5 links)
  88. Subclasses should be specializations‏‎ (5 links)
  89. User:LukeRobinson‏‎ (4 links)
  90. State pattern‏‎ (4 links)
  91. Robert Cecil Martin 1996e‏‎ (4 links)
  92. User:RobertLechte‏‎ (4 links)
  93. No silver bullet‏‎ (4 links)
  94. Paul Clark's Design Study‏‎ (4 links)
  95. Amelioration patterns‏‎ (4 links)
  96. Contain contents not parents‏‎ (4 links)
  97. Reusable frameworks over reusable components‏‎ (4 links)
  98. Reduce implicit parameter passing‏‎ (4 links)
  99. Kent Beck 2003‏‎ (4 links)
  100. Paul Clark's Whiteboard‏‎ (4 links)
  101. Observer pattern‏‎ (4 links)
  102. Robert Cecil Martin 1997b‏‎ (4 links)
  103. State machine design‏‎ (4 links)
  104. Class diagram‏‎ (4 links)
  105. Limit hierarchy depth‏‎ (4 links)
  106. DBC‏‎ (4 links)
  107. User:Nick Molhoek‏‎ (4 links)
  108. 427 design standard‏‎ (4 links)
  109. Christopher Alexander 1977‏‎ (4 links)
  110. Domain model pattern‏‎ (4 links)
  111. Robert Cecil Martin 1996a‏‎ (4 links)
  112. User:Chen Qing‏‎ (4 links)
  113. User:Oliver Cardwell‏‎ (4 links)
  114. Distribute system intelligence‏‎ (4 links)
  115. Inheritance for specialization‏‎ (4 links)
  116. Encapsulation is hierarchical‏‎ (4 links)
  117. Cay Horstmann 2002‏‎ (4 links)
  118. PLoP‏‎ (4 links)
  119. User:Filip Kujikis‏‎ (4 links)
  120. Getter and setter policy‏‎ (4 links)
  121. Design Patterns‏‎ (4 links)
  122. Robert Cecil Martin 1996c‏‎ (4 links)
  123. Beware of non-communicating methods‏‎ (4 links)
  124. Sign your work‏‎ (4 links)
  125. Agile methods‏‎ (4 links)
  126. Robert Cecil Martin 1996d‏‎ (4 links)
  127. User:Ryan Mallon‏‎ (4 links)
  128. Agent classes irrelevant‏‎ (3 links)
  129. Design examples‏‎ (3 links)
  130. Alan Davis 1995‏‎ (3 links)
  131. Combining design patterns‏‎ (3 links)
  132. Single choice principle‏‎ (3 links)
  133. Management antipatterns‏‎ (3 links)
  134. Make all Member Variables Private‏‎ (3 links)
  135. User:Bertrand Roussel‏‎ (3 links)
  136. Kent Beck 2000‏‎ (3 links)
  137. Analysis Patterns‏‎ (3 links)
  138. User:Scott Parlane/DesignStudy‏‎ (3 links)
  139. Robert Cecil Martin 1997a‏‎ (3 links)
  140. One hour tour‏‎ (3 links)
  141. Limit compositions in a class‏‎ (3 links)
  142. Richard Helm‏‎ (3 links)
  143. Extensibility‏‎ (3 links)
  144. Rebecca Wirfs-Brock 1990‏‎ (3 links)
  145. Refactoring and design‏‎ (3 links)
  146. About COSC427‏‎ (3 links)
  147. Uncle Bob‏‎ (3 links)
  148. Empty method over-rides‏‎ (3 links)
  149. Separate non-communicating behaviour‏‎ (3 links)
  150. Maxim Hierarchy‏‎ (3 links)
  151. Spaghetti code‏‎ (3 links)
  152. Organisational patterns‏‎ (3 links)
  153. User:Aidan‏‎ (3 links)
  154. Template:Documentation‏‎ (3 links)
  155. Richard Gabriel 1996‏‎ (3 links)
  156. GenA: A Genetic Algorithms Framework‏‎ (3 links)
  157. Alan Kay‏‎ (3 links)
  158. Avoid verb classes‏‎ (3 links)
  159. Methods should use most fields of a class‏‎ (3 links)
  160. Joshua Bloch‏‎ (3 links)
  161. Mujtaba's design study‏‎ (3 links)
  162. User:Paul Clark/US-001-Add Task‏‎ (3 links)
  163. Strategy pattern‏‎ (3 links)
  164. Trains design‏‎ (3 links)
  165. OO culture‏‎ (3 links)
  166. User:Darryl Anderson‏‎ (3 links)
  167. Arthur Riel‏‎ (3 links)
  168. Exam questions‏‎ (3 links)
  169. Minimal public interface‏‎ (3 links)
  170. PLoP (Software Patterns Series)‏‎ (3 links)
  171. Identify message layers pattern‏‎ (3 links)
  172. Design patterns break rules‏‎ (3 links)
  173. Christopher Alexander 1979‏‎ (3 links)
  174. Strategy Pattern‏‎ (3 links)
  175. User:Paul Clark/US-002-Claim an Open Task‏‎ (3 links)
  176. Beware accessors‏‎ (3 links)
  177. Martin Fowler 2004‏‎ (3 links)
  178. Shalloway and Trott 2002‏‎ (3 links)
  179. Frogs second design‏‎ (3 links)
  180. User:Paul Clark‏‎ (3 links)
  181. Barbara Liskov‏‎ (3 links)
  182. Ward and Kent‏‎ (3 links)
  183. Do not change the state of an object without going through its public interface‏‎ (3 links)
  184. No global variables or functions‏‎ (3 links)
  185. Establishing priorities‏‎ (3 links)
  186. Impedance mismatch‏‎ (3 links)
  187. Send messages to components instead of to self‏‎ (3 links)
  188. User:Paul Clark/US-003-Execute Task‏‎ (3 links)
  189. Steve McConnell 2004‏‎ (3 links)
  190. A froggy visitor‏‎ (3 links)
  191. Factor implementation differences into subcomponents‏‎ (3 links)
  192. Managing complexity‏‎ (3 links)
  193. Greg Searle's project blackjack‏‎ (3 links)
  194. Gang Of Four 1995‏‎ (3 links)
  195. Refactoring and performance‏‎ (3 links)
  196. Double dispatch‏‎ (3 links)
  197. AlexsLibrary‏‎ (3 links)
  198. Andrew Hunt 1999‏‎ (3 links)
  199. Agile manifesto‏‎ (3 links)
  200. Poker Simulator Design Log‏‎ (3 links)
  201. User:Tanmay Bhola‏‎ (3 links)
  202. Idioms‏‎ (3 links)
  203. Put semantic constraints in class definition‏‎ (3 links)
  204. Immutable object‏‎ (3 links)
  205. Inventory and Accounting‏‎ (2 links)
  206. Michal's Design Study‏‎ (2 links)
  207. Main Page‏‎ (2 links)
  208. Scrum‏‎ (2 links)
  209. Parallel hierarchies‏‎ (2 links)
  210. User:Benjamin Kearns‏‎ (2 links)
  211. Delegation‏‎ (2 links)
  212. Data mapper pattern‏‎ (2 links)
  213. Michael's Log‏‎ (2 links)
  214. Account setup‏‎ (2 links)
  215. Resource materials‏‎ (2 links)
  216. Rebecca Wirfs-Brock‏‎ (2 links)
  217. Template:Ambox/core‏‎ (2 links)
  218. Define default values via explicit protocol pattern‏‎ (2 links)
  219. Access levels‏‎ (2 links)
  220. LukasKorsikaDesignStudy‏‎ (2 links)
  221. Observations and Measurements‏‎ (2 links)
  222. EXtreme programming‏‎ (2 links)
  223. Active record pattern‏‎ (2 links)
  224. Data transfer object pattern‏‎ (2 links)
  225. Identity map pattern‏‎ (2 links)
  226. Keep behaviour with data‏‎ (2 links)
  227. Peter Coad 1995‏‎ (2 links)
  228. Tell dont ask‏‎ (2 links)
  229. Sorcerers design‏‎ (2 links)
  230. David Parnas‏‎ (2 links)
  231. Teaching and learning style‏‎ (2 links)
  232. Trygve Reenskaug‏‎ (2 links)
  233. Avoid accidental multiple inheritance‏‎ (2 links)
  234. Law of leaky abstractions‏‎ (2 links)
  235. Martins Design Study‏‎ (2 links)
  236. Planning‏‎ (2 links)
  237. Program to the interface not to the implementation‏‎ (2 links)
  238. Kent Beck 2007‏‎ (2 links)
  239. Visitor pattern‏‎ (2 links)
  240. One Into Many‏‎ (2 links)
  241. Oliver Cardwell/Project‏‎ (2 links)
  242. Page controller pattern‏‎ (2 links)
  243. Row data gateway pattern‏‎ (2 links)
  244. Table data gateway pattern‏‎ (2 links)
  245. Greg Searle's captains log star date‏‎ (2 links)
  246. Grady Booch‏‎ (2 links)
  247. Contained objects should not use each other‏‎ (2 links)
  248. User:Jenny Harlow/Design study/Final design detail‏‎ (2 links)
  249. Model classes not roles‏‎ (2 links)
  250. Software crisis‏‎ (2 links)

View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)

Views
Toolbox