Text of post

Do you disagree with how the company you work for is run? Are they on the BDS list? Are they a fossil fuel company or SUV manufacturer? Is strike action not an option? Try hiding under a rock! Alternatively, adopt ‘slow-down’ tactics among your colleagues. These methods of industrial action are intended to slow down the efficiency of companies without risking disciplinary action. ‘Slow-down’ might take the form of playing everything ‘by the book’ and taking procedural processes VERY SERIOUSLY. In practice, corners are cut, so why not become that sticker for the rules and make sure everything is signed off exactly how the bosses intended? In an industrial dispute in 2011, right-handed Australian workers at the airline Qantas started using their left-hands. So get out from beneath that rock, and if you’re stuck by circumstances working for a bad-guy, get creative with your resistance - and organise offline with your colleagues. Crab Museum takes no responsibility for you getting the sack, but it’s worth thinking about what power we still have over the world around us.

    • SwitchyandWitchy [she/her]@hexbear.netEnglish
      8·
      6 days ago

      The coworkers being chuds is the implied justification for this, but I do want to caution against individual action. It’s very easy to find yourself out of luck and good will when taking action against both the company and coworkers, even if the latter isn’t the main target.

      It’s always better to find a route that results in at least passive support from your coworkers. In my experience this usually isn’t difficult and just takes patience, since the bosses inevitably screw things up and make more work for everybody by cutting corners and searching for more productivity while keeping pay and benefits as low as they can get away with.

    • 30_to_50_Feral_PAWGs [she/her]@hexbear.netEnglish
      2·
      6 days ago

      (with the caveat that i know exactly nothing about how coding/software development works)

      spoiler

      What I described above is just how most public open-source projects operate their public source code repositories. It’s not even overkill for a private company’s setup; depending on the org, it might not even be quite enough. At my company, I have seen – and personally shot down – far worse branch management strategies (e.g., git-flow, which may have its own SCP entry).

      Granted, it’s probably overkill for a personal project unless you’re collaborating with someone else and/or actively trying to track deliverables or target milestones or some such. Or, as I like to call it, “mitigating my own unmedicated ADHD symptoms by tracking EVERY GODDAMNED THING so I don’t need to think back and remember it three weeks from now when I actually see this half-abandoned project again.” Sometimes it even works!