Simple Sabotage Field Manual by United States Office of Strategic Services
gutenberg.org
gutenberg.org
> Anyone can break up a showing of an enemy propaganda film by putting two or three dozen large moths in a paper bag. Take the bag to the movies with you, put it on the floor in an empty section of the theater as you go in and leave it open. The moths will fly out and climb into the projector beam, so that the film will be obscured by fluttering shadows.
How do you go about surreptitiously obtaining several dozen large moths?
I haven't seen one in decades. No idea if there are any left.
->
(10) To lower morale and with it, production, be pleasant to inefficient workers; give them undeserved promotions. Discriminate against efficient workers; complain unjustly about their work.
(11) Hold conferences when there is more critical work to be done.
(12) Multiply paper work in plausible ways.
(13) Multiply the procedures and clearances involved in issuing instructions, pay checks, and so on. See that three people have to approve everything where one would do.
(14) Apply all regulations to the last letter.
(It's no longer in my apartment, but that was a hell of an election.)
Then on top of all that you had the presidential election.
I ended up reading a lot of Sun Tzu and python books because of it.
> (1) Insist on doing everything through “channels.” Never permit short-cuts to be taken in order to expedite decisions.
> (2) Make “speeches.” Talk as frequently as possible and at great length. Illustrate your “points” by long anecdotes and accounts of personal experiences...
> (3) When possible, refer all matters to committees, for “further study and consideration.” Attempt to make the committees as large as possible—never less than five.
> (4) Bring up irrelevant issues as frequently as possible.
> (5) Haggle over precise wordings of communications, minutes, resolutions.
> (6) Refer back to matters decided upon at the last meeting and attempt to re-open the question of the advisability of that decision.
So what you're telling me is my coworkers are all saboteurs!
Not really:
> The FBI was particularly interested in learning this type of information about foreign diplomats or their agents.
> ...The area of greatest concern was the information at academic libraries that could be accessed through sophisticated databanks used for research. This point was illuminated by the report that a Soviet employee of the United Nations had been able to recruit a college student from Queens to obtain information at the library that was described as sensitive.
Let me introduce you to Kurt Saxon
https://m.youtube.com/watch?v=tsxGX5F5SXg
https://archive.org/details/The_Poor_Mans_James_Bond_Vol_1_K...
https://archive.org/details/Granddads_Wonderful_Book_of_Chem...
> https://m.youtube.com/watch?v=tsxGX5F5SXg
Wow, he's going on an on about keeping mung beans in jars, then I skip ahead and he's making homemade fuses for bombs? Then I noticed he's missing half his fingers on his right hand. WTF.
After that first part, the second really shouldn't be any surprise at all...
The surprising thing to me is that such a person feels they're qualified enough to instruct other people on this topic.
Kurt Saxon (born Donald Eugene Sisco on March 6, 1932) is an American neo-Nazi
He was also part of the church of Scientology for a bit. Imo his political opinions are less interesting than the content he was teaching.
Yeah I agree guy was kinda nuts. Lol so what?
It’s the content that’s interesting. Didn’t see anyone else share something like that, so I did. He was one of the first in the “survivalist” movement, seemed relevant to the discussion as the document in the post was from a similar time period.
2. Introduce scrum to direct the workflow.
3. The more layers of management, the better.
4. The more approvals for any simple action, the better.
5. The more meetings, the better.
6. ???
7. Profit!
9. Spend time “improving” the “UX” of your system. Use lots of metrics to justify hiding key functionality.
10. Tell everyone not to use code comments and make their code “self-commenting”.
11. Insist on 100% test coverage to waste time. Make most tests test the test suite and private methods.
12. Use O(n²) algorithms wherever possible, and ensure your test data sets are always small. Be sure to say you can’t replicate slowness when you close the ticket.
13. Delay updating software as long as possible. Never update to the latest version — if a new security fix comes out, deploy the old patch because the new one wasn’t audited. Disable automatic updates.
14. Validate data on the client side.
15. Never take tasks from an out-of-band request, no matter how easy or important. Always insist that tickets are properly triaged, assigned story points, and go through sprint planning first.
16. Actually use your vacation days.
hah, I saw some of that right here on HackerNews, on today's thread about someone cutting GTA's load time from 6 minutes to <2 with a few lines of code. A lot of stuff along the lines of "I can't believe you'd attack the engineers like that, they're just focusing on what's really important to the company"
> Mechanic tells crew what he found: "Tank was out of fuel & broken down as you said. I found a leaking fuel line, timing belt snapped, puncture in oil reservoir & cracked radiator" "A cracked radiator you say?" interjected one Russian soldier. "Huh. I don't remember doing that."