3 ms·

> They reduce us to our produce. They ignore the very thing that materializes the creation: the human. This viewpoint doesn't make much sense to me. When somet

by catach 3y ago

> They reduce us to our produce. They ignore the very thing that materializes the creation: the human. This viewpoint doesn't make much sense to me. When something I make is reviewed, it's that work that's being reviewed, not me. I'm not being reduced as I'm not the thing being reviewed. And as the primary purpose of a review is to inform others if the work in question is good for them, talking about the work and not the creator seems entirely the right approach.

gymbeaux 3y ago
This is a variant of the “you are not your code” thing, and what I said with that post is that I don’t agree with the spirit of the expression. While yes I am not literally my code, that isn’t a reason to remove all emotion from it, especially in the review process. Surely there’s a logical fallacy where one believes something to be true because it sounds logical, but in reality logic is not applicable and the fallacy is applying logic where it probably shouldn’t be applied.
- nuancebydefault 3y ago
  "you are not your code" is what this article made me think about as well. In theory, that expression is true, but in practice every person is an emotional being. Why do programmers program? Because it pays the rent or because they like to solve problems? Well, it is a combination of both. Constructive feedback works. Feedback about subjective details usually have an adverse effect. In that sense, it is very good if you can shake off/try to ignore the 1 or 2 star reviews, and learn from the 3-4 star reviews,showing the good and what can be improved as well.
- nextaccountic 3y ago
  But if you were to be your code, how can one possibly criticize the code without criticizing you, or even fix a bug, or redesign it to be better? Nobody wants to fix the "you" that is in the code, they don't want to redesign "you" to be better, they want to fix the code itself. This probably requires that you distance yourself from the code your produce, in order to let it go. Can this be done at all?
  - sroussey 3y ago
    I agree: there needs to be separation. In a typical corporate environment with teams, I like to say the team own the code. It’s the teams responsibility after all.
- catach 3y ago
  To me, the distinction here is not one of total emotional detachment vs full emotional investment. It's more: criticism of your work is criticism of something you've done, not criticism of who you are.

by catach 3y ago

gymbeaux 3y ago

This is a variant of the “you are not your code” thing, and what I said with that post is that I don’t agree with the spirit of the expression. While yes I am not literally my code, that isn’t a reason to remove all emotion from it, especially in the review process. Surely there’s a logical fallacy where one believes something to be true because it sounds logical, but in reality logic is not applicable and the fallacy is applying logic where it probably shouldn’t be applied.

nuancebydefault 3y ago
"you are not your code" is what this article made me think about as well. In theory, that expression is true, but in practice every person is an emotional being. Why do programmers program? Because it pays the rent or because they like to solve problems? Well, it is a combination of both. Constructive feedback works. Feedback about subjective details usually have an adverse effect. In that sense, it is very good if you can shake off/try to ignore the 1 or 2 star reviews, and learn from the 3-4 star reviews,showing the good and what can be improved as well.
nextaccountic 3y ago
But if you were to be your code, how can one possibly criticize the code without criticizing you, or even fix a bug, or redesign it to be better? Nobody wants to fix the "you" that is in the code, they don't want to redesign "you" to be better, they want to fix the code itself. This probably requires that you distance yourself from the code your produce, in order to let it go. Can this be done at all?
- sroussey 3y ago
  I agree: there needs to be separation. In a typical corporate environment with teams, I like to say the team own the code. It’s the teams responsibility after all.
catach 3y ago
To me, the distinction here is not one of total emotional detachment vs full emotional investment. It's more: criticism of your work is criticism of something you've done, not criticism of who you are.