RSS feed [root] /weblog /software_engineering




login:

password:

title search:




 


Sun Jul 29 23:13:36 HKT 2018

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/

http://www.funretrospectives.com/

code review something you don't know - https://maxbittker.com/code-review/ https://dev.to[..]w-to-review-code-you-dont-understand-pc7

https://dev.to[..]ood-code-reviews-and-win-colleagues-2dc8

https://medium.com[..]/code-review-best-practices-19e02780015f


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