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

why not both?


Because, as they state under another heading,

> It’s not in your interest as a worker to let capital think that its workers are saboteurs.

And although documentation can make you somewhat replaceable, it is a joyless and tiring experience to work on something that is quickly evolving yet completely undocumented. I'd rather be made slightly more replaceable if it meant my job wouldn't be a tiring, joyless grind.


The part about code reviews and meetings is about working to rule, to further delay progress. Don't take risks with bugs, review thoroughly. Don't ask for forgiveness, ask dor permission and escalate it in meetings.


The trick is to have documentation but keep it a secret.


it's not nice to the other workers — that's not very good class solidarity.


The article was missing the words "together" and "solidarity". It seemed to be a product of a culture of extreme individualism.


Yeah. "I, the individual, am going to do my best to make sure that I get mine, even if it harms the company and my coworkers". That's not "class warfare". That's narcissism.


As opposed to “I, the executive or founder, am going to do my best to make sure that I get mine, even if it harms the company and my employees." Who has the most incentive and power to be the narcissist? Employees would be smart to understand this dynamic.




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

Search: