# Code reviews

DevFeed: [Code reviews](<https://devfeed.tech/articles/code-reviews-27278.md>)

Original publisher: [Read original article](<https://blog.pchudzik.com/201708/on-code-reviews/>)

Published: 2017-08-29T00:00:00Z

Content type: opinion

Language: en

Sources: [Paweł Chudzik](<https://devfeed.tech/sources/pawe-chudzik.md>)

Topics: [Code review](<https://devfeed.tech/topics/code-review.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Code quality](<https://devfeed.tech/topics/code-quality.md>)

Tags: [code-quality](<https://devfeed.tech/tags/code-quality.md>), [code-reviews](<https://devfeed.tech/tags/code-reviews.md>), [good-practices](<https://devfeed.tech/tags/good-practices.md>), [team](<https://devfeed.tech/tags/team.md>), [trust](<https://devfeed.tech/tags/trust.md>)

## AI overview

This opinion argues that code reviews should be a team effort rather than the responsibility of one person. It explains that shared reviews improve product ownership, expose more issues, spread knowledge, support learning, and contribute to better design.

## Source excerpt

Code review is a great process which gradually improves code quality. It is a system you can implement in many ways. In this post I'm going to grumble about one particular way of performing code reviews - when there is only one person responsible for doing code reviews and suggesting/accepting/rejecting changes. Read more