in reply to Programming is combat
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?)
C.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: Programming is combat
by Paulster2 (Priest) on Jul 09, 2004 at 11:50 UTC |
In Section
Meditations