An Introduction to Class Warfare for the Software Engineer
1–10 of 353 posts
Re: An Introduction to Class Warfare for the Software Engineer
#2Had me in the first half, lost me in the second. Why not try to create unions instead of "don't document anything because you're making yourself replaceable"?
Re: An Introduction to Class Warfare for the Software Engineer
#3Had me in the first half, lost me in the second. Why not try to create unions instead of "don't document anything because you're making yourself replaceable"?
why not both?
Re: An Introduction to Class Warfare for the Software Engineer
#4Had me in the first half, lost me in the second. Why not try to create unions instead of "don't document anything because you're making yourself replaceable"?
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.
Re: An Introduction to Class Warfare for the Software Engineer
#5Had me in the first half, lost me in the second. Why not try to create unions instead of "don't document anything because you're making yourself replaceable"?
This is called, "The Tyranny of Competence", and is hostile to other workers.
Companies also don't have a way to quantify this, and sometimes will hesitate to term someone, until they are fed up and will just decide it is worthwhile at all costs.
I have worked with or been the successor to folks who did this and it made me absolutely furious, and reflected poorly on my performance.
Re: An Introduction to Class Warfare for the Software Engineer
#6Earlier quoted context omitted.
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.
Re: An Introduction to Class Warfare for the Software Engineer
#7I don't live in NY or Seattle. The tech sector is much smaller where I am. I've never seen it be advantageous to treat other people as someone I'm in competition with. I've been laid off. Yeah it sucks, but no job is forever, and being nice to people means I get to sleep at night. I've also never seen anyone who can't be replaced. Time and time again something wasn't documented, and other devs/dbas/admins stepped in and figured it out. I'd rather be the guy people say, "I help out when there is a problem" instead of, "I hate working with him, because I never know what he's doing." It's nicer, and makes it easier to work with someone you did before. That's just me though.
Edit: I've also been on the hiring side and passed on people I know like that. My job is to mitigate risk, and those people are a liability.
Re: An Introduction to Class Warfare for the Software Engineer
#8Earlier quoted context omitted.
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 trick is to have documentation but keep it a secret.
Re: An Introduction to Class Warfare for the Software Engineer
#9This is plain bad advice that sounds smart because it comes from the "ultra-practical" but short-term corner of thinking.
In reality being a good person is what pays off long-term. If I'm laid off, I will continue my professional journey elsewhere - perhaps on my own, maybe even with more satisfaction?