Martin Fowler

When people think of code reviews, they usually think in terms of an explicit step in a development team’s workflow. These days the Pre-Integration Review, carried out on a Pull Request is the most common mechanism for a code review, to the point that many people witlessly consider that not using pull requests removes all opportunities for doing code review. Such a narrow view of code reviews doesn’t just ignore a host of explicit mechanisms for review, it more importantly neglects probably the most powerful code review technique – that of perpetual refinement done by the entire team.

One of the most pervasive perspectives in software is the notion that it’s something we build and complete – hence the endless metaphor of building construction and architecture. Yet the key property of software is that it is soft, and can be as easily modified after it’s released as it was when

To read the full article click on the 'post' link at the top.