Simple Sabotage for the 21st Century – Specific Suggestions

You see this happening in russia these days.<p>My favourite was from the start of the war when the guys who were supposed to plant incriminating evidence on the scene were they arrested some &quot;terrorists&quot; put the Sims 3 game on the scene instead of 3 sim cards and literally signed the fake documents they planted with &quot;Signature Unclear&quot;. (Yes, real story, just search for Sims 3 and Signature Unclear.)<p>As I understand it I understand this was FSB (or someone elses) way of &quot;getting even&quot; after their boss had been publicly humiliated for proposing to not invade Ukraine. (But that - except for the public humiliation which is well documented - is just speculation on my part although I might have heard it from someone else thinking loud.)<p>Although sometimes I wonder if it was a genuine misunderstanding. I feel I have unusually many Russian friends and ex-colleagues, people who live outside of russia for good reasons and do not support it. Z-russians on the other hand does not strike me as the brightest bulbs in the box.

&gt; Log users out frequently for &quot;security reasons&quot;.<p>This is exactly what happens on a contract I work on. Any software that is authenticated through our OKTA SSO very frequently signs users out and redirects to a logout page. This is especially annoying when using the project management software, where you typically have many tabs open to see various requirements, epics, stories, tasks, etc. Any inactivity more than 15 minutes, and all the tabs are logged out. Just like that, everything is gone. It forces us to use strategies such as saving redundant copies of things in notes and spreadsheets. I don’t think it’s necessarily sabotage but it feels extremely negligent. Moreover it’s completely unnecessary since everything is behind a VPN anyway.<p>Another similar thing that does feel as if it’s somewhat malicious is the very aggressive logout and shutdown policy of our virtual desktops - these are the desktops we do everyday active development on and where we set up IDEs, database clients, web servers, testing tools, API references - anything you can think of. We use this in combination with our regular desktops where we attend meetings or do other non-development tasks such as using the above-mentioned requirements software. It takes a lot of time to set all of this up! If you’re inactive for more than 2 hours, your session is not only closed, it’s completely destroyed so that it can be reclaimed for another user. I don’t need to explain to experienced developers how incredibly frustrating and counterproductive this is, but leadership has been extremely dismissive of any complaints, and tell us that we should use our time more wisely or that we shouldn’t be inactive for so long (which is complete BS, there are a thousand valid reasons foe this). Apparently this is done for cost-cutting reasons, but something feels more nefarious here, because this very obviously leads to reduced productivity and demotivation. This has actually lead to me purposefully overestimating complexity and demanding a user story for every single little trivial action I take, whereas before I used to just go in and make quick fixes or knock out certain operational things in my spare time. It’s a waste of time for us and ends up being worse for our customers.

This is a takeoff on a well known WWII pamphlet, the Simple Sabotage Field Manual.[1]<p>That&#x27;s not the real worry today. Today we have to worry about remote sabotage of key systems - water, power, comms. It&#x27;s quite possible that we will see major blackouts in the US, Russia, Europe, or China as side effects of the various wars in progress.<p>[1] <a href="https:&#x2F;&#x2F;www.cia.gov&#x2F;stories&#x2F;story&#x2F;the-art-of-simple-sabotage&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.cia.gov&#x2F;stories&#x2F;story&#x2F;the-art-of-simple-sabotage...</a>

Another one: when a colleague asks for something that is wrong, implement it as requested without questioning.

Looks like government has already implemented a lot of these suggestions.

Just love this. My particular favorite is sending the <a href="http:&#x2F;&#x2F;" rel="nofollow">http:&#x2F;&#x2F;</a> version of everything instead of <a href="https:&#x2F;&#x2F;" rel="nofollow">https:&#x2F;&#x2F;</a>.

That site is kind of a riot.<p>Click on &quot;Exit&quot;.

&quot;These seem kind of dated.. I feel like you could have more speci-&quot;<p>&gt; Require wet signatures (ink on paper) for documents instead of digital<p>Jesus Christ.

This is very funny. I just wish the Slack unfurls showed the specific suggestion from the link.

heisenhelpful.

We are all now immediately suspicious of certain coworkers...

I may be having an old fuddy duddy moment but I really dislike this site. My first suggestion was at least interesting. My second was to superglue things into place.<p>Will supergluing things in place actually help the oppressed? Are you the Harriet Tubman of adhesives? Or will someone who makes minimum wage get yelled at and then forced to clean it?<p>This is Tik Tok level pranks applied to serious political issues and frankly, oppressed people deserve better than this.

This reads like a guide on how to get fired for cause. Additionally its quite childish. Why not just throw a tantrum and save the trouble?