Schools of thought
From CSSEMediaWiki
(Difference between revisions)
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 == | |
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]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== 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?
