Beefy Boxes and Bandwidth Generously Provided by pair Networks DiBona
Keep It Simple, Stupid
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??

Combat as aprogramming metaphor is indeed interesting. Some thoughts for you: Soviet Military Doctrine was to "attack along organizational divisions" so for instance the Fulda Gap was the expected site of WWIII as that was the dividing line between the US and British Forces. This meant that they would exploit the inablity of the opposing forces to communicate with each other. Also the the Soviet Doctrine was "a full speed ahead" strategy. With troops (armor etc) moving at high speeds, Nato doctrine was the "sponge" (backed up by action point lines.) So while the soviets would try to go as fast as possible through the opposition (while exploiting poor coms between organizational units) the NATO strategy was to wait for them to pass through the lines then attack them from the sides and back. They didnt try to outright prevent the Sovs from getting through, they would essentially let them go and then get them in their vulnerable behind instead. All of this was backed up by a tactical nuclear posture that stated that if the Soviets crossed certain lines the response would be to turn much of Germany into a nuclear wasteland.

Personally I can see various aspects of these strategies in software development. The place where your development efforts are going to go wrong is when you have poor comms because of organizational "ownership". Sometimes its no good trying a strong defence against various issues, instead its better to structure your systems for graceful failure followed by preventitive shut down.

No doubt you could work these metaphors further... Anyway, nice node. ++ to you.


---
demerphq

    First they ignore you, then they laugh at you, then they fight you, then you win.
    -- Gandhi



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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • 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:
    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
  • Outside of code tags, you may need to use entities for some characters:
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others studying the Monastery: (11)
    As of 2014-04-18 12:28 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      April first is:







      Results (466 votes), past polls