I think schumi hit it right on the with the end of his post.

Programming applications needs to be fluid. Fluid like a Glass of water. Rigid enough to hold in the water, (a la using standardization techniques) but fluid like the water so as to be able to adapt and cover the problem at hand.

I have noticed that this situation is usually brought about by persons who know what they want the system for, and who have very little understanding of software design processes and methods. Currently, I am in this situation writing a Java based reporting system, with a database backend, and have come to many of the same frustrated dead ends. Management wants the latest and greatest, and therefore, anything that is already written isnt good enough.


my apologies for restating some points mentioned earlier, but they were relevant.
_________________________________________
E-Bitch
Tempora Mutantur Nos et Mutamur in Illis
"The Times are Changed Even as We are Changed in 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.