Plan a design before you start.[...]
Plan to throw away at least one design and start over.
Try to keep your design fairly compartmentalized, and
loosely coupled. That way, when you do find a flaw
in your first design, you don't have to throw everything
away: some of the code you've already written will easily
work with your new code. (For instance, if you're always
updating a database the same way, and you keep the database
update code well-separated from everything else, you won't
need to make any changes to it when you realize that your
interface code is hopelessly screwed, trash it, and start
over.)
--
The hell with paco, vote for Erudil!
:wq
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.