The difference between "design what the customer needs
and no more" and over design is clear and also doesn't
To clarify, I'm not an unthinking follower of "design what the customer
needs and no more"; I feel that's a dangerous over-simplification.
While writing code that is never used is certainly waste,
and one has to beware of over-engineering,
I don't view this as a black and white issue.
I touched on this in the
"Agile Design" section where I stated:
Software design is an art requiring experience, talent, good taste, and
deep domain, computer science and software usability knowledge.
I feel there's a bit more to it than the four simple rules above.
and then continued on to present my twenty tortuous rules. :)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||