On a slightly different tact to most of the responses: there is a limit to how separated your design can be from your implementation. In theory, you can design all the details of an application, then build it exactly according to your spec, the details of the implementation being irrelevant. (Assuming, of course, your requirements don't change. They always do, but that's not my point here).
Time and again, however, I've found the design wasn't able to forsee all problems, or couldn't achieve the depth of understanding necessary to spec a full implementation. To actually do this requires the application to be implemented. Only then are all issues properly understood.
Except in very simple applications, your initial spec will almost always have to be altered, even if the requirements are static.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.