News for hackers. Stuff that matters.
Re:Simple Sabotage Field Manual (1944) [pdf] by uncle_d on Sunday August 27, 2017 @06:03AM (#15110045)
Sounds like standard .gov operating procedure:

«When possible, refer all matters to committees, for "further study and consideration." Attempt to make the committee as large as possible — never less than five.»

Re:Simple Sabotage Field Manual (1944) [pdf] by aluhut on Sunday August 27, 2017 @06:29AM (#15110107)
Or standard office procedures:

> Hold conferences when there is more critical work to be done.

> To lower morale and with it, production, be pleasant to inefficient workers; give them undeserved promotions.

And there is also the standard "I want to keep my job move":

> Never pass on your skill and experience to a new or less skillful worker.

Re:Simple Sabotage Field Manual (1944) [pdf] by QAPereo on Sunday August 27, 2017 @07:17AM (#15110243)
A committee is a cul-de-sac down which ideas are lured and then quietly strangled. Barnett Cocks
Re:Simple Sabotage Field Manual (1944) [pdf] by otp124 on Sunday August 27, 2017 @08:01AM (#15110393)
I had a thought that this might have been the intelligence community taking a humorous jab at the US government, and also happened to be true. But have no information on if committees were better or worse at that point in history.
Re:Simple Sabotage Field Manual (1944) [pdf] by 0xbear on Sunday August 27, 2017 @03:24PM (#15112243)
That whole chapter reads like SOP of any large corporation in the US today.
Re:Simple Sabotage Field Manual (1944) [pdf] by marcosdumay on Sunday August 27, 2017 @12:13PM (#15111342)
I am still holding the opinion that this piece was sarcastic until I get evidence to the contrary. It is way more plausible than the CIA creating something that effective.