How peer review leads to quality code
-
What if you could deploy resources you already have at your disposal to improve quality, get projects done earlier – with fewer errors and with less budget impact – by simply implementing a software quality control method that most likely already exists in other parts of your organization?
"Many hands make light work."
-
What if you could deploy resources you already have at your disposal to improve quality, get projects done earlier – with fewer errors and with less budget impact – by simply implementing a software quality control method that most likely already exists in other parts of your organization?
"Many hands make light work."
Yeah? Well you're not gettin a look at mine as you'll make me rework this and that and this and that. :-D
-
What if you could deploy resources you already have at your disposal to improve quality, get projects done earlier – with fewer errors and with less budget impact – by simply implementing a software quality control method that most likely already exists in other parts of your organization?
"Many hands make light work."
Earlier in my career, I was a ASQ Certified Software Quality Engineer. One of the things I learned in my studies was that Code Reviews was the most effective means of removing defects from project deliverable. Defect removal is usually greater than 75% and as it can occur earlier in the project, finds the defects when it is least expensive to repair. Also, Reviews are not only applicable to code, but can be applied to specifications, design, prototypes, almost anything, and the earlier the better. One important reason why it is good to have other eyes look at your work is that you will not see the kinds of mistakes that you make, or else you would have fixed it already. It requires someone who thinks, works, and programs slightly, or extremely, differently than you to real savage your deliverables, looking for problems. Just remember to practice egoless coding. You are not your code, be proud that you can make it better. Also remember that you write code for people, not computers, otherwise we would just be inputting ones and zeroes. I personally consider it a great day of coding when I end up with less code that I started with, it does more, and reads like a book so almost anyone can understand it.
-
What if you could deploy resources you already have at your disposal to improve quality, get projects done earlier – with fewer errors and with less budget impact – by simply implementing a software quality control method that most likely already exists in other parts of your organization?
"Many hands make light work."
Assert.That(NumBadProgrammers * 2 == NumBadProgrammers)MarcImperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
Assert.That(NumBadProgrammers * 2 == NumBadProgrammers)MarcImperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
We'll have to get someone to review that ;)
TTFN - Kent
-
Assert.That(NumBadProgrammers * 2 == NumBadProgrammers)MarcImperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
Assertion failed due to Arithmetic Overflow Error
-
Earlier in my career, I was a ASQ Certified Software Quality Engineer. One of the things I learned in my studies was that Code Reviews was the most effective means of removing defects from project deliverable. Defect removal is usually greater than 75% and as it can occur earlier in the project, finds the defects when it is least expensive to repair. Also, Reviews are not only applicable to code, but can be applied to specifications, design, prototypes, almost anything, and the earlier the better. One important reason why it is good to have other eyes look at your work is that you will not see the kinds of mistakes that you make, or else you would have fixed it already. It requires someone who thinks, works, and programs slightly, or extremely, differently than you to real savage your deliverables, looking for problems. Just remember to practice egoless coding. You are not your code, be proud that you can make it better. Also remember that you write code for people, not computers, otherwise we would just be inputting ones and zeroes. I personally consider it a great day of coding when I end up with less code that I started with, it does more, and reads like a book so almost anyone can understand it.
I could not agree more. I would just add that code reviews are a great way to learn. I enjoy being shown where my code could be improved! Valery.
-
I could not agree more. I would just add that code reviews are a great way to learn. I enjoy being shown where my code could be improved! Valery.
Absolutely. Reading other peoples code is a great way to learn new patterns and language features. I've been writing .NET code since the original beta, and still find new ideas and techniques from code reviews and reading code from articles and GitHub. You also see some great examples of how NOT to do things as well, typically over-architected, 40 layers of abstraction, theoretically correct horrors.