Hacker News new | past | comments | ask | show | jobs | submit login
Four ways to a Practical Code Review (2007) (methodsandtools.com)
16 points by cfontes on Jan 21, 2015 | hide | past | favorite | 2 comments



I guess we're already doing these. We use a pull request workflow and I get an email when a developer creates the pull request. I inspect the changes in the request and approve and/or merge the changes into our main development branch. EZPZ


Missing figures, unfortunately.

EDIT: I was wrong. It's just that the figure is waaaay below the paragraph that mentions it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: