I still am in the small shops and we have taken advantage of
the fast turn-around inherant in Perl to produce 0.1 style
versions of what is requested. This prompts the user to
respond with more details. A rapid developement cycle gets
to the end result faster with more end-user satisfaction
(especially if they feel they've been in on the consultation
process). It's also a defensive manouver in an
environment where we get a lot of spurious requests.
The politics of the situation is that we have to be seen to
deal with poorly thought-out demands, with few staff, or be
labeled obstructionists to management by those with an axe
to grind. Our best weapon is a quick response, placing the
onus back on the user to specify what they really
want. That, and a web-based requisition system that users
are encouraged to use to track progress on their
whim^Wrequests.
Ea :wq
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|