Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>That the code is delivering the best business value possible. Additionally code reviews aren't just for the code that has been written, it's also to help shape the code that will be written in the future. With the tools that are available these days much of what we used to look for is already (at-least mostly) taken care of by the time code is committed to source control. At-least that's how I think it should be done. To elaborate here's a snippet of something I wrote before on this subject.</p> <p>".Net code review tools have been improving over recent years and removing some of the traditional necessity of code review, but not the most valuable aspect. There are static analysis tools like FxCop to automatically review for all the code-deterministic industry standard guidance. There are source analysis tools like Microsoft’s recently released Source Analysis (a.k.a. StyleCop) to review all the source code style choices made. With Continuous Integration and TDD code is reviewed to make sure it builds and meets the expected business scenarios. Products like NDepend have been recently introduced to review code and provide statistical information to help determine if designs are following principles that lead to sustainability. All of these types of tools augment the ecosystem in which we review our software. However, none of them provide any help in one of the most critical aspects of code review - the answer to the question “does this code deliver the best value for the business domain?” Just because code passes FxCop, StyleCop, looks good in NDepend and passes automated tests doesn’t mean it provides the best business value. Those tools are part of a domainless code review ecosystem, they don’t have any insight into any of the businesses we create software for or how well our code serves that domain. The answer to the “best value” question is in some ways subjective, but the most capable people to provide the answer are the coders in that domain using the tacit technical and business knowledge that only they retain. Code reviews are the way to apply and share that tacit knowledge and find the answer to the “best value” question." - <a href="http://jb-brown.blogspot.com/2008/06/teamreview-new-business-value-from-code.html" rel="nofollow noreferrer">TeamReview - New Business Value From Code Review</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload