. . . in a organization of any significant size, it's generally a bad idea for developers to make unilateral decisions about how the product should be changed.

Yes, you are absolutely correct. Now, if only Marketing or the business units would get their heads out of the collective asses long enough to actually provide usable direction to us developers, we could all go home and have milk and cookies before naptime.

I have worked at 9 different places in the past 7 years. At 5 of them, developers wrote specifications. At 2 of them, developers co-wrote specifications. So, in less than a quarter of the places I have worked at, developers received usable specs.

I've been lucky.

My wife's blog

In reply to Re^7: Analyzing large Perl code base. by dragonchild
in thread Analyzing large Perl code base. by dmitri

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.