You’ve probably heard it said that if everyone is responsible, no one is responsible. That can happen, but that doesn’t make it a good thing.
Clean code is important. Being able to see what makes code unclean is also important.
Code reviews are part of almost all development workflows. How you write them, read them, and respond to them says a lot about a team’s culture. It’s also a way to adjust a team’s culture. How you use them is up to you.
Don’t just review it, review it BEFORE you show it to anyone. It’s good for you, it’s good for them, and it’s good for your code.
When you say you want quality software, what are you really asking for, and how can you get it?
Trying multiple things at once is NOT faster