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
component.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|