3 ms·
That's fine, but saying "this code makes my eyes bleed" is very obviously meant to demean the human being who wrote the code, not the code itself.
by nollidge 14y ago
That's fine, but saying "this code makes my eyes bleed" is very obviously meant to demean the human being who wrote the code, not the code itself.
- Dylan16807 14y agoI honestly don't see that. It insults their coding ability, or at least their focus when coding that particular thing, but disparaging a single skill that a person has is not being demeaning to that person. At least in my mind.
- scott_s 14y agoI think most people would find it demeaning to hear it said about their code.
- jtheory 14y agoThat's pretty much what demeaning means, though. It's not "a single skill" as if you were telling Torvalds that his juggling skills were crap and he should keep his day job; if someone has enough coding experience that they're releasing OSS on GitHub, coding is quite likely their job (or they're in school to make it their job). So yeah, snarkily saying that the product of someone's career activity makes your eyes bleed (or whatever) is demeaning to them -- i.e., directly attacking their dignity and others' respect for them.
- Dylan16807 14y agoTheir dignity should not be dependent on their job area being flawless. Thinking they screwed up on a single hobby project should not cause a loss of respect for the person.
- jtheory 14y agoThere's a big gap between "not flawless" and "my eyes are bleeding" or "I can't make this stuff up". Also: "should" != "is", I'm afraid.
- Dylan16807 14y agoI'm trying to make a distinction between 'a code project' and 'all the code they make'. Generally speaking, having one shit project doesn't do much to someone's overall record. 25 good, 1 shit is better than 10 good, 0 shit.