Code review is another fundamental part of being an open team. You should make your code available for code review. Not because the reviewer will find bugs, but because it will make you write better code.
The code you write is the final output of your development process. It shouldn’t be left out of the knowledge sharing of your open team. Some teams have specific policies for when and how code should be reviewed. Others are more relaxed about it. Either is fine as long as the code review remains positive and focuses on specific ways to make improvements.