> Let’s also remember that reviewers aren’t always right—even when the majority opinion disagrees with the code author. After weeks (sometimes longer) spent tackling a problem, the code author is usually the most qualified in that specific problem’s domain, unlike team members or leads who’ve only engaged with it for the hour or so it takes to review the code. More often than not, it’s better to trust the code author’s judgment.
What a shit take. Code reviewers ask questions and point out issues. If your PR includes errors and fails to address problems that reviewers were able to spot just by looking at them, it means nothing how much time you took working on it. Just fix it instead of sulking in blog posts.
And then this gem.
> In fact, I’d argue that the code author, by virtue of their time and effort, deserves the chance to see their proposals in action.
What is this? A participation medal? It means nothing how much time and effort you invested. If your PR has errors and introduces obvious bugs and fails to comply with anything, just fix it. Push a commit that addresses remarks and learn from it. Or are you expecting your team members to post follow-up commits to fix the mess you are making? Perhaps you're just hoping to block pipelines when automated tests fail?
Yeehaw! Screw y’all and your lintin’ ‘n’ rules. I gets the final say!
Plenty of cowboy developers rejoicing reading this ;)
From the article:
> Let’s also remember that reviewers aren’t always right—even when the majority opinion disagrees with the code author. After weeks (sometimes longer) spent tackling a problem, the code author is usually the most qualified in that specific problem’s domain, unlike team members or leads who’ve only engaged with it for the hour or so it takes to review the code. More often than not, it’s better to trust the code author’s judgment.
What a shit take. Code reviewers ask questions and point out issues. If your PR includes errors and fails to address problems that reviewers were able to spot just by looking at them, it means nothing how much time you took working on it. Just fix it instead of sulking in blog posts.
And then this gem.
> In fact, I’d argue that the code author, by virtue of their time and effort, deserves the chance to see their proposals in action.
What is this? A participation medal? It means nothing how much time and effort you invested. If your PR has errors and introduces obvious bugs and fails to comply with anything, just fix it. Push a commit that addresses remarks and learn from it. Or are you expecting your team members to post follow-up commits to fix the mess you are making? Perhaps you're just hoping to block pipelines when automated tests fail?
Absurd.