Well i guess it depends. If you can figure out what the underlying problem is and identify a better solution then you have a number of options. You can provide several quotes for how much work will be involved, naturally the dumb solution will take longer. :-) Alternatively you can simply implement your own solution as a "proof of concept" and then point out they can have it Right Now, or wait some time for the dumb solution.

Another approach that works is use deductive reasoning to identify potential issues in the design, then write a very carefully worded mail saying that you wont procede until the issues are resolved to your satisfaction, or until a manager provides you with written instructions stating that they understand the issues that you have raised and want to go ahead anyway. This is useful because very few people like this want to be put in the hot seat. By forcing them to provide documentation you are making clear that in no way in the future will you be held responsible for the poor design, and that instead they will.

I suspect the truth is tho that the only really good solution is to find a different place to work.

---
$world=~s/war/peace/g


In reply to Re^4: Enterprise development: Its ok to say No! by demerphq
in thread Enterprise development: Its ok to say No! by demerphq

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.