---
title: "Discussion on \"Is Pushing Code Through Review...Correct?\" | Hashnode"
description: "Discussion on \"Is Pushing Code Through Review...Correct?\". What's the best way to get code reviews pushed through? Assigning them to the most-familiar dev, assigning them to the quickest dev, or less familiar devs?\nIf they are to minimize the bus factor, are we asking the right question?"
url: "https://hashnode.com/posts/is-pushing-code-through-reviewcorrect/6407d27f41f3ed9f91f1cb27"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Is Pushing Code Through Review...Correct?](https://codereviews.hashnode.dev/is-pushing-code-through-reviewcorrect?utm_source=hashnode&utm_medium=feed)

What's the best way to get code reviews pushed through? Assigning them to the most-familiar dev, assigning them to the quickest dev, or less familiar devs? If they are to minimize the bus factor, are we asking the right question?

Mar 8, 2023 · 1 min read · codereviews.hashnode.dev  
Read the article

-   [#dev-effectiveness](https://hashnode.com/tag/dev-effectiveness)
-   [#code-quality](https://hashnode.com/tag/code-quality)
-   [#developer-experience](https://hashnode.com/tag/developer-experience)
-   [#code-review](https://hashnode.com/tag/code-review)

## Written by

[Eric Meadows](https://hashnode.com/@EricMeadowsDev)

@EricMeadowsDev

  
[View profile](https://hashnode.com/@EricMeadowsDev)

On a mission to solve the code review problem - to make code reviews suck less.

I am the founder at SourceField - I'm on a mission to solve the code review problem - to make code reviews suck less.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.