3 ms·

You describe an appeal to accomplishment fallacy. Whether or not someone has done x or y themselves has no bearing on whether your code has quality issues.

• samsquire 3y ago
  The merit of the code quality issues is in question based on the authoritativeness of the person doing the criticising. I don't like the pride, superiority and smugness that comes from criticizing code and the assumption that they're the ones in the right because of their criticism, rather than the expertise of the one who wrote the code and solved the problem and did the work. I've noticed people pay more attention to the stones that people throw rather than those throwing them. Edit: In other words, criticism is cheap if you have no skin in the game. I don't think it's a fallacy, it's like hosting a wedding and inviting a guest and then being criticised for the entertainment on offer. People pay attention to the criticism, not that the criticism is coming from a guest and that their criticism is not as valuable coming from the guest than the people paying for and tastes of those hosting the wedding. Whether or not the code quality issues are true or not, their importance is dependent and weight of someone's criticism is not that high as everyone thinks.
• yobbo 3y ago
  "Quality" is not an indisputable property of the code. Someone's judgement about code quality can only have as much weight as their competence.