That's why I say test and verify - you can do this while implementing .
Basically I agree with this other AM at Re: Re: Re: My number 1 tip for developers..
You and BrowserUk both seem to have a different understanding of the steps.
Perhaps I should have emphasized basic in the basic software engineering steps.
There are no subcategories.
There are no metrics.
BrowserUk says The whole point of the tip is the idea that you learn to recognise (as early as possible) when you are wasting time trying to 'get something to go',
and that's a good tip if you get writers coders block. I suppose my only uneasiness with BrowserUks original node is that he first tips on the mechanics of banging a keyboard, when spec/analysis and then design is what you always need to start with.
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.
|
|
