analyzing and programming is best not done by one guy. Because or your a good analyzer or you are a good programmer, but being good at both is almost impossible.

<rant mode="on">
With all due respect with the poeple you work with this is a load of BS.

It is very easy to write a perfect design... as long as you don't have to implement it. Only going through the actual writing of the code will reveal the flaws in the design. Programming is the messy part, the part when clean abstractions hit reality.

I agree that separating the analysis and the programming is a good thing but saying that you can't be good at both is non-sense. Analysis must take implementation into account. And analysis needs to be refined as programming progresses. It is too easy for the author of a neat but un-implementable design to put the blame on the darn programmers who can't write what he told them too.

Programming is not a "detail" as I heard it once!
<rant mode="off">

Ranting aside it is generally a good idea for the designers to be good coders, and most of all to have to be part of the coding team. Makes them more responsible about what they design.

In reply to RE: Just thinking ... by mirod
in thread Just thinking ... by toadi

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.