---
title: "Comment by uzlopak on \"Most teams are doing code reviews wrong. Here are 3 warning signs, and 3 fixes.\" | Hashnode"
description: "Actually no real advice was given by this article. Also Lacks of hacker mentality. If you have a better idea on solving an issue in a PR then provide a poc or b"
url: "https://hashnode.com/posts/most-teams-are-doing-code-reviews-wrong-here-are-3-warning-signs-and-3-fixes/61f0512ae247b2151e61f746/comment/61f2df2b52c7824742748756"
---

[Discussion](https://hashnode.com/posts/most-teams-are-doing-code-reviews-wrong-here-are-3-warning-signs-and-3-fixes/61f0512ae247b2151e61f746)

Comment [Most teams are doing code reviews wrong. Here are 3 warning signs, and 3 fixes.](https://hashnode.com/posts/most-teams-are-doing-code-reviews-wrong-here-are-3-warning-signs-and-3-fixes/61f0512ae247b2151e61f746)

[uzlopak](https://hashnode.com/@uzlopak)

[Jan 27, 2022](https://hashnode.com/posts/most-teams-are-doing-code-reviews-wrong-here-are-3-warning-signs-and-3-fixes/61f0512ae247b2151e61f746/comment/61f2df2b52c7824742748756)

Actually no real advice was given by this article. Also Lacks of hacker mentality. If you have a better idea on solving an issue in a PR then provide a poc or branch off and make your fixes there. The original coder can then adapt it by merging and then there is less back and forth. Or atleast provide pseudocode and/or offer pair programming.

I already had cases, where the team thought a solution was good enough, despite my "nitpicking". I finally branched off, added a poc exploit and branched again off and fixing it properly...

Last advice has to be, like Aristotle already wrote, if you have somebody, who is not able to discuss, than don't discuss with him. It means in our world, to leave the team or maybe the company.

[Curtis Einsmann](https://hashnode.com/@einsmanntech)

[Jan 27, 2022](https://hashnode.com/posts/most-teams-are-doing-code-reviews-wrong-here-are-3-warning-signs-and-3-fixes/61f0512ae247b2151e61f746/comment/61f2df2b52c7824742748756#reply-61f2fcc522a38747671d6f6d)

The article specifically calls out 3 things that should be documented in the code review guidelines. If they were unclear, I’m open to suggestions on how they can be clarified.

A code reviewer isn’t expected to fix the author’s code. They’re reviewing, not doing the work for them.
