It's the same for me, I always ask what the problem is because usually the way our managers want to have something solved is by far not the perfect way.
All they usually come up with is "some way" they know because they've heard about it or seen something about it sometime ago while having no clue if it's still a good way to solve the problem nowadays. Or they just don't know the alternatives...
If I would just have to implement other people's solutions I would have quit my job already a long time ago, because it would just bore me to death.

But sometimes it also happens that they just want solution X to be implemented if it's a good idea or not. Managers sometimes just are like that, they get something in their brain and won't agree to that it's a bad idea whatever arguments you come up with. A good example here is "java/J2EE" which is IMO often used for things it shouldn't be. I really hate that but you finally just have to accept it sometimes I guess...

I really love it to say "see that's why I said we should use Y for that and not X!" once a project is finished and people start to realise that the result is a piece of crap....

kodo

In reply to Re: Enterprise development: Its ok to say No! by kodo
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.