---
title: "Discussion on \"Building Confidence in Code Reviews\" | Hashnode"
description: "Discussion on \"Building Confidence in Code Reviews\". Advice for productive code reviews and becoming a more confident developer"
url: "https://hashnode.com/posts/confidence-code-reviews/630f466175af73ad1f060ce9"
---

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

Discussion

# [Building Confidence in Code Reviews](https://blog.kthorpe.co/confidence-code-reviews?utm_source=hashnode&utm_medium=feed)

Advice for productive code reviews and becoming a more confident developer

Aug 31, 2022 · 6 min read · blog.kthorpe.co  
Read the article

-   [#junior-developer](https://hashnode.com/tag/junior-developer)
-   [#impostor-syndrome](https://hashnode.com/tag/impostor-syndrome)
-   [#code-review](https://hashnode.com/tag/code-review)
-   [#beginners](https://hashnode.com/tag/beginners)
-   [#programming](https://hashnode.com/tag/programming)

## Written by

[Kyle Thorpe](https://hashnode.com/@kjthorpe)

@kjthorpe · Pittsburgh, PA

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

Software Engineer

Software engineer based in Pittsburgh, PA with interests in cloud computing, cybersecurity, and professional growth. Some other things I like: history, exercise, rock climbing, coffee shops, live music, reading, podcasts

## Responses 2

Markdown supported · ⌘↵ to post

[Danyal](https://hashnode.com/@danyal)

[Aug 31, 2022](https://hashnode.com/posts/confidence-code-reviews/630f466175af73ad1f060ce9/comment/630fad8156df9e8e5025a07b)

Great post, Kyle!

I remember joining a company as an intermediate developer where everyone else was at Senior level.

When I would be doing code reviews, my first action was to run it and check whether the functionality works and try to break it.

This inspired the whole team put flags on PRs on whether it should be at least run and checked because I was catching a lot of bugs that would show up in running it.

I think anyone can do good code reviews as long as they are diligent about it and in an open enough environment where they can ask why something is done in a specific way.

PRs are a great way to learn the codebase and how everyone else writes code.
