Discussion on: How to code review in a start up?

Does anyone have any words of wisdom for code reviewing in small teams?

• Accept the views of each individual. Do not work against each other. By this I mean that it can quickly happen that critical comments on one's own code can be taken to heart, although they are only well-intentioned.

• Write down a small checklist.

• Always checkout the work.

• Run tests.

How do you make time to review code?

• Try to schedule it. Just like writing tests. I know the client does often not understand why you need tests or code reviews. Explain it to them well, so that they will understand it. For example they will get a better product and less bugs.

What do you do if there isn't a reviewer available who can understand that code or programming language?

• Simply wait. I know time is money, but do you really want to push unreviewed code to your master branch? If someone in your team does not understand what you've written, take the time and explain it. You are a team and as I said "Do not work against each other". Try to get the same knowledge base. Work together and try to push each other. This is not a competition.

How do you resolve disputes when the reviewers and the authors are the same technical level?

• Be honest with each other and with yourselves. Try to understand each other and stay reflected on yourself. I think the same "level" is not a problem. The most important thing is simply to discuss together and listen to the views of others! You can see it as a sort of "rubber ducking".

Hope this will help you and your team a little bit.