Code review vs. static code audits-2

After discussing this post with colleagues, I was pointed to one more reason to not neglect code reviews.

The reason is that after a code review there are two people who know how the piece of code is written, not just the original developer, who wrote it.

They know how it works. And, more importantly, they know what it was written for, be it fixing a bug, implementing a new feature or just getting rid of a piece of technical debt.

The code review makes people share knowledge - not just some technical tricks, but a deep understanding of the project's requirements, architecture and code base. And it is hard to think of anything more important.

Comments

Popular posts from this blog

Multi-threading skills - what do you mean by that?

Code reviews, recommended reading

Spring Framework and Code Obscurity