Formal Code Review Process 👎🏽 and Collective Code Ownership 👍
Avoid the Formal Code Review Process and embrace “Collective Code Ownership.”
Substack version of this article.
I have written two articles on the Code Review process.
In this article, I will discuss Code Review with an Agile term: “Collective code ownership,” which many of this generation of software professionals are unfamiliar with.
“Collective code ownership, as the name suggests, is the explicit convention that “every” team member is not only allowed, but in fact has a positive duty, to make changes to “any” code file as necessary: either to complete a development task, to repair a defect, or even to improve the code’s overall structure.”
— Agile Alliance
Yes, encourage the developers to change code without permission or waiting. I led a few client projects this way, which worked very well. I know many readers might have doubts. Check out this thought-provoking interview with Steve Jobs.
