RSS feed [root] /weblog /software_engineering




login:

password:

title search:




 


Fri Aug 25 16:03:07 HKT 2017

review



Why code review beats testing: evidence from decades of programming research - http://kev.inburke.com[..]the-best-ways-to-find-bugs-in-your-code/

1: Review often
2: Review informal and short
3: Review with difference people
4: Keep it positive
5: Enjoy it

http://www.makinggoodsoftware.com[..]/08/06/5-tips-to-make-good-code-reviews/

Why review on naming is important - http://swreflections.blogspot.com.au[..]code-and-code-reviews-whats-in-name.html

Maybe useful... can take a look - https://www.ibm.com[..]ary/11-proven-practices-for-peer-review/ http://spin.atomicobject.com/2013/10/18/code-review/ http://www.yegor256.com/2015/02/09/serious-code-reviewer.html

checklist - http://technotes.towardsjob.com[..]com/java/code-review-checklist-for-java/ http://blog.fogcreek.com[..]-with-our-code-review-checklist-example/

another doc about review - http://www.lornajane.net[..]ode-reviews-before-you-even-run-the-code

https://www.infoq.com/articles/effective-code-reviews <- also a list

giving-better-code-reviews - https://medium.com[..]ter-code-reviews-16109e0fdd36#.hvku9f942

Measuring software engineering competency - http://www.savvyclutch.com[..]asuring-software-engineering-competency/


(google search) (amazon search)
second
download zip of files only