Member-only story
How to Sabotage Your Team: A Guide to Pull Request Pandemonium
Are you bored at work and want to rustle up some division within the team? Is everything running along a little too smoothly for your liking and you feel it would be fun to throw a few spanners in the works? Are your team mates irritating you and you want to get back at them with some good old fashioned passive aggression? Then I have some great tips for you! (Assuming you’re a Software Developer and you work with a team doing Pull Requests… if not then you will just have to divert to ChatGPT and ask him/her/them what are some good tactics for team destruction in whatever field you happen to be working in. I’m sure it will come up with some great suggestions).
The following “tips” are for when you are working on Pull Requests. Pull requests are a necessary evil in the software world.
Software Developers love to work alone, huddled over their laptops in dark rooms with streams of fluorescent green text shimmering up and down their monitors. That’s a fact.
However, on occasions they have to peer out from their murky dens and ask their fellow Software Developer to look upon what they have just created and deem whether it fits the standards of the greater team.
It is at this point that you can commit your stealthy sabotage of the team’s ever fragile and tenuous…
