Schools of thought

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
m (Reverted edits by Ebybymic (Talk); changed back to last version by Matthew Harward)
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
 
This page is an attempt to make sense of the overwhelming morass of OOD advice by identifying differences in underlying design philosophies, which lead to conflicting maxims.  
 
This page is an attempt to make sense of the overwhelming morass of OOD advice by identifying differences in underlying design philosophies, which lead to conflicting maxims.  
  
>== Reuse vs DTSTTCPW ==
+
== Reuse vs DTSTTCPW ==
  
 
The emergence of OO into the software mainstream was driven by [[Software reuse]], and this lead to a raft of maxims intended to encourage reusability.  But reuse flopped.  Today it isn't mentioned in polite company, and instead we say things like [[Do the simplest thing that could possibly work]] because [[You ain't gonna need it]].
 
The emergence of OO into the software mainstream was driven by [[Software reuse]], and this lead to a raft of maxims intended to encourage reusability.  But reuse flopped.  Today it isn't mentioned in polite company, and instead we say things like [[Do the simplest thing that could possibly work]] because [[You ain't gonna need it]].
Line 14: Line 14:
 
* [[Do the simplest thing that could possibly work]]
 
* [[Do the simplest thing that could possibly work]]
 
* [[Refactoring]]
 
* [[Refactoring]]
 
----
 
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
 
----
 
>=[http://ewozukyn.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
 
----
 
 
----
 
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
 
----
 
>=[http://amiqymywa.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
 
----
 
 
----
 
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
 
----
 
=[http://uxateja.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
 
----
 
=[http://uxateja.co.cc CLICK HERE]=
 
----
 
</div>
 
 
=[http://amiqymywa.co.cc CLICK HERE]=
 
----
 
</div>
 
 
=[http://ewozukyn.co.cc CLICK HERE]=
 
----
 
</div>
 
  
 
== One Ring to Rule Them All... ==
 
== One Ring to Rule Them All... ==

Latest revision as of 03:22, 25 November 2010

This page is an attempt to make sense of the overwhelming morass of OOD advice by identifying differences in underlying design philosophies, which lead to conflicting maxims.

Reuse vs DTSTTCPW

The emergence of OO into the software mainstream was driven by Software reuse, and this lead to a raft of maxims intended to encourage reusability. But reuse flopped. Today it isn't mentioned in polite company, and instead we say things like Do the simplest thing that could possibly work because You ain't gonna need it.

In the 'Reuse' corner:

In the 'DTSTTCPW' corner:

One Ring to Rule Them All...

... one ring to find them one ring to bring them all and in the darkness bind them

What rule(s) underpin whole families of maxims?

Personal tools