comment on

My thought on Train as you fight (Which sounds the opposite to "More sweat in training is less blood in war" to me, as that implies training before fighting.. but whatever.. ):

Train/learn during development/design, as opposed to during the "war", which I would define as crisis times when a customer has found a bug that needs to be fixed yesterday. At this point, there shouldnt be learning going on, just application of knowledge.

Overall, it sounds like a good set of anologies, that make quite a bit of sense.. (Why does it remind me of of the Marcinko books?)

In reply to Re: Programming is combat by castaway
in thread Programming is combat by brian_d_foy

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.


laziness, impatience, and hubris
	PerlMonks