When you do have to play all three roles (UI-designer, tester,
coder), the best approach is to do the UI-design first (on paper),
then write your unit tests, then write the code. In this way, you
risk the least cross-contamination of design and testing with the
actual coding. Obviously you still have to be conscious of your role
(don't think about implementation while designing the UI, just focus
on the UI). And, of course, it doesn't all have to be up-front. You
can do the same thing in an iterative fashion so long as you make
sure you follow the design,test,code steps in that order for each
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] |