You left out the biggest component.
- Design/Research/Thinking/Coding/Testing/Documentation: 10%
- Maintenance: 90%
With that in mind, anything that can be done in the 10% to make the 90% easier is well worth the time and trouble.
I'm all for thinking and research and design, but 75% seems excessive. Then again, I don't make a distinction between Coding and Testing. As bikeNomad implies, my approach resembles more design-one-feature -> write-tests-for-the-feature -> code-the-feature.
You can put a lot of time into design up front, but what if you get something wrong? You can put of the tests until later, but what if you don't remember exactly what you were thinking when you were writing the code you're now trying to test?
Make safe bets.
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.