To elaborate what I meant by "Research/Design/Thinking", I meant to say that all cogitation about a project, be it on the problem domain, the answer domain, the implementation domain, and/or the testing domain ... all of that should consist of at least 3/4 of a given project's time.

You cannot build a good set of test suites unless you've thought about how the requirements need to be tested. This includes black and white box testing, as well as other methods. (Bounds testing comes to mind...)

You cannot build a good implementation without thinking about the ramifications of a given concept. A few things I like to think about would include:

And every other domain you can think of falls into this catch-all category. I thought about possibly breaking it down further, but realized that you might have to research a lot of non-programming stuff (like I've been having to do) for one project, but have to research a lot on algorithms in another. Or, you might be spending a lot of time designing the test suite. Maybe the implementation is conceptually easy, but the testing is damnably hard. Or, it could be the other way round, or a mixture of both. Code Complete makes it very clear that what goes into the pre-coding aspect of a project is impossible to determine for all projects. That's why they pay us the big bucks. :)

------
/me wants to be the brightest bulb in the chandelier!

Vote paco for President!

In reply to Re: Re: What efforts go into a programming project? (Somewhat OT) by dragonchild
in thread What efforts go into a programming project? (Somewhat OT) by dragonchild

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.