You will want to read Code Complete
by Steve McConnell.
One simple trick that this book taught me is to write
a high-level, natural-language description of your task,
comment it out, and write the code corresponding to each
modular part of the description. This way, you even get
comments for free.
Another good thing is to acquire a feeling for when
top-down styles (structured programming, most OO stuff,
flow-charts, etc.) and bottom-up styles (interactive
environments, rapid prototyping, tool development)
of programming are appropriate. Unfortunately,
this is very hard. Since most of today's techniques are
top-down style, I think it is good practice to learn a functional
programming language (Scheme, Lisp, Haskell, etc.), since
these tend to encourage bottom-up style.
Christian Lemburg
Brainbench MVP for Perl
http://www.brainbench.com
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.
|
|
