|. . . 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.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.