When you get together technical people who understand management goals, and management staff that appreciate technical evaluations and decisions, the result can be really satisfying. It's great work, if you can get it.

More often, time is short, and so is the patientce to listen and understand. Competence comes up short too. We all have things we're not good at. Thus we work with what we've got. Things are often as your "rant" depicts them, and everyone loves reading dilbert because it strikes close to home all too often.

We can lament that things are not better, or be thankful that things are not worse, but either way the satisfaction comes from making some piece of the process work a little better. At least that's what works for me.

I enjoyed reading your thoughts. Thanks for sharing them.

---

---

• 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.