99% of what you're talking about is in the book Code Complete. It's probably the best US$50 on programming knowledge I've ever spent. If you're serious about wanting to have programming be your (current) career, read it. It's a very long book, and it assumes some knowledge of programming. But, it will explain, not only what, but why as well.

The best non-literary way of making sure you're doing things right is to write a bunch of stuff, then not look at it for six months. (Yes, I know that's a long time!) Then, go back and look at it. If you could understand what you were doing without scratching your head too much, you did it right. If you can't, fix those issues in the code you're working on right now. (Leave the crap you wrote before ... it's worthless now.)

A number of monks have always said that code should be self-commenting, irregardless of the other documentation. I whole-heartedly agree with this and, 3 years out of school for Computer Science, I've been improving my coding style. (Just to let you know you're not alone. *grins*)

Good luck!

------
/me wants to be the brightest bulb in the chandelier!

Vote paco for President!

In reply to Re: best practice by dragonchild
in thread best practice by George_Sherston

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.