Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Clever framing of the authors own biases. I'd argue that for at least some of these, the opposite behaviour would be the true sabotage.


Let’s make a committee to discuss! we need all the key players involved, so let’s invite all of dev and QA, ~60 people for an hour long discussion?


What? You think the meeting was unnecessary? Well, you're the only one who disagrees with the outcome. Sounds like you're not being a team player. Let's have a meeting with HR tomorrow.


In fact, a sabotage manual should include the opposite action for each point. These are not the methods of sabotage, they're the methods of shrouding your sabotage in plausibility. It wouldn't provide you plausible deniability if doing the things on the list was never reasonable.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: