Like the man said, "there's more than one way to do it."
That being said, I like to aim for the following in my code:
And I look for them in that order. I suppose when I have a boss who disagrees with my methods, I may have to rethink them, but so far neither employer nor co worker has yet to take issue with the way I do things.
I have to admit to not having sat down and read PBP yet (I've skimmed it), but that's largely because I was fortunate enough to have good CS profs who taught me to start by writing out step by step, in plain English, what I wanted to do and how I want to do it. It's amazing how big projects suddenly become a series of smaller, simple ones that way.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||