I've fantasized about writing my own, but applying it to programming.
Several years back I had some discussions along these lines with a coworker who'd been in the Isaeli army. One of the sticking points we had was on the subject of collateral damage. In a military campaign, particularly in a "take that hill, dammit" action, you expect collateral damage as a matter of course, but it's most often someone else's problem to clean up. In software development, collateral damage is another source of defects; you might try to shove it out of the way (or define it away), but it still represents a pile of new defects, and you're unlikely to be able to avoid dealing with those defects for long without taking a reputation hit.
Dealing with collateral damage is where a number of approaches to reframing software development as X fall down. The level of precision, correctness, and robustness that software development requires is rarely understood or appreciated outside of our domain.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||