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.