People learn to discern quality by having multiple examples to compare and (most importantly) contrast. If all code that you deal with is good, then you'll never learn what makes it good - it just seems to naturally flow. If all code that you deal with is bad then you have no positive role models for your own code. Therefore you need exposure to both.
What is more helpful than exposure, though, is exposure with feedback from someone who can explain what to look at, why one is better than the other. (Feedback from trying to analzye the results of your project is also helpful.) Exposure to books that try to explain this is better than nothing, but far from perfect - we each make individual kinds of mistakes and books will only help you if your mistakes happen to match the ones that the books are trying to address.
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.