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.
Italian Striking by forcing the CHUDdy devs on my team to learn a (not-very-)convoluted Git branching strategy and apply it to every single software project in our repositories, regardless of the scope of the feature, enhancement, or defect tickets that come in. One line change? Sorry, you gotta make a milestone for your target version, make a release candidate branch that will be your eventual merge target, make an issue and track it against the milestone, make a branch for the issue and a merge request that targets the release candidate branch, and keep your work the fuck out of Main/trunk until it has been reviewed by a team lead.
Oh, you didn't add trace loggers in this one function? You failed code review, go back and create another issue, a branch for the issue, and a merge request targeting the release candidate branch. Oh, you forgot to update the version string in the Maven POM file to indicate that this is a
-SNAPSHOTrelease? Undeploy your non-Prod code and fix it. Yes, that means another issue, a branch, and a merge request targeting the release candidate branch. The control plane should not be reporting a non-snapshot version on a pre-release, god damn it!...except this is all ultimately just good housekeeping because it makes sure those motherfuckers are very intentional about what they do in that codebase, given that we had a revolving door contractor situation for a few years that left us with more tech debt than any small team could ever hope to address.
sounds more like making life miserable for your coworkers than anti-boss action tbh (with the caveat that i know exactly nothing about how coding/software development works)
Yeah but it says in the first like 5 words they're chuds so it would annoy chuds and slow productivity. Win-win.