Amen! They really don't know.

But, remember - the specs will always change. Always.

The important thing to do is make sure the customer SIGNS off a valid spec sheet - so that when rep A from a company says "This should be blue"and you change to blue, and then rep B says "This should be red" and you change to red, and then rep A comes back and says "Why didn't you make the change the blue" - you have some kind of proof to justify your fee.

Having to do work is not a bad thing - not getting paid for that work is a bad thing.

We can't escape having to work, otherwise we wouldn't need jobs. Now the lottery, however . . . ;)

jeffa

In reply to (jeffa) Re: They don't specify because they don't know what they want by jeffa
in thread 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.