comment on

++ "...and none of them are changing."

This. It seems that it is the rare project that doesn't have changing requirements of some form.

When I was in college, lo these many years ago, I did house construction for a while. It was not uncommon to hear "Can you (move|add|remove) this (door|window|wall|other)?" in the course of things. As it's a lot easier to (move|add|remove) things before you've run the electrical, plumbing, mechanical, or closed up the walls than it is after-- getting the feedback a.s.a.p. is essential to minimizing cost/schedule.

Actually, now that I think of it, not everything WAS on the blueprints as the assumption seemed to be that the contractor would figure out the missing details as they went along.

In reply to Re^2: OpEd: Programming is not Team Sports by gsiems
in thread OpEd: Programming is not Team Sports by sundialsvc4

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.


Problems? Is your data what you think it is?
	PerlMonks