DEV Community

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

Collapse
 
kjocevicius profile image
Karolis Jocevičius

I actually don't see much need to overcomplicate this. Especially when you have only 5 people.

While I don't work in a startup, my team consists of 4 people. For all our projects, we have rules, set in version control:

  • 'master' branch is protected and you can't push to it directly at all.
  • Pull requests must be approved (by anyone from the team)
  • CI checks must be successful

Also, preferably, code reviews shouldn't be too big, because then nothing ever will be reviewed.

That's it! Technical level doesn't really matter. Junior devs can both spot stuff and learn something by reviewing code. Time allocation shouldn't be an issue - send it for whoever is free at the moment.

Also remember that code reviews are not there for bug prevention, but rather for code quality improvement.