After reading Ovid's specify,specify,specify i first had the urge to laugh because it has been for me that way ever I started the developer's job. But then began wondering why is it that you always end up whit either incomplete or completely wrong specs? Because they don't know.

In my time as a developer no customer / project coordinator or whatever has had any clue what he / she really wanted. So you had to come up with a draft first, then specs changed, you had to rewrite 80% of the code (mostly) or with that changing specs in mind you will write a lot of unnecessary overhead (which it turns out to be in the end).So are we doomed like Sysiphos to recode all of our works?

I don't think so. We just need to talk more to our customers and give them more time to influence the project. That is also a caveat. We have to make it clear to the customers that in order to satisfy exactly their needs they also will have to invest time in the project instead of leaning back in that siwel chair and waiting for results.

But this might be a long way and we are just at the beginning of that road (I always wanted to say that :-)) My boss calls in for another project's review. I have the strange feeling that the specs will change...

Yours,
C-Keen

In reply to They don't specify because they don't know what they want by C-Keen

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.