Improving the code review process is considered the #1 way for a development team to improve the quality of their code base. But code reviews are tedious. And they happen too late in the coding process.
What if you can comment or ask a question on any line of code at any time and discuss that with your team or your reviewer?
Code Reviews are widely used to improve code quality and facilitate knowledge transfer. Yet, they are dreaded by many developers and managers. And while they represent an opportunity to capture knowledge for the whole organization, the knowledge transfer is typically one-on-one and somewhat ephemeral.
In the Streamline Your Code Reviews white paper by CodeStream founders Claudio Pinkus and Peter Pezaris, we analyze common code review practices and propose a new approach to code reviews that solves both the dread factor and the knowledge leakage problem. This is achieved by implementing a new approach to code discussion. Until now, discussions about code that is yet to be merged took place in third party tools or pull request comments that took developers away from their IDE, and thus required them to switch context. We introduce the notion of a code discussion in-editor, while coding, that allows faster feedback, lowers resistance to change, and automatically attaches itself to the code it refers to, turning conversations into documentation.
We refer to this approach as a Fluid Code Review.
CodeStream customers are leveraging the Fluid Code Review methodology to shorten their code review times by as much as 50%. Armed with knowledge described in the Streamline Your Code Reviews white paper you'll be able to start implementing recommended best practices and procedures and experience shorter, more productive code reviews within your next few sprint cycles.