DEV Community

loading...

How is code review organized in your company?

Milan Latinović
Enterprise Architect and Software Developer contributing to companies and products such as Codeable, TimeTac, apilayer, Eversign.
・1 min read

Code review is a process, which has a goal to assure the quality of delivery. In this specific case, the team is reviewing the quality of the code. This is accomplished by one or more developers examining the code which their colleagues wrote.

How are you doing code review? Do you pick someone who will review your code or is it voluntary? How much time does it take? When do you do it?

Discussion (2)

Collapse
marcelofarias profile image
Marcelo Bukowski de Farias

We do what we call continuous code review.

From the reviewer's perspective, it's all done from the IDE, as soon as he/she receives a feedback request, without switching branches.

From the code author's perspective, feedback is requested automatically as soon as the commit happens (even in local branches) or even before a commit, if needed.

We use a tool that we developed to do that (it's an open-source cross-IDE plugin called CodeStream).

Collapse
milanlatinovic profile image
Milan Latinović Author

hmm, interesting, I was expecting more responses to these questions. Not sure if these are taboo topics or just haven't reached the right audience.