1. Tips for a successful code review

2. “Introduction to the Personal Software Process – PSP”
by Watts S. Humphrey.

3. how can they achieve a level of code quality that
causes pride among the professionals involved?
The answer: CODE REVIEW.

4. There are three types of code reviews:
pair programming,
formal code review,
lightweight code review.

5. benefit of code review

6. “good idea; bad execution”

7. Worst code Review

8. intellectually vain can make code reviews a
nightmare of shouting and hurt feelings.
But despite all that they are very useful.

9. Learn to enjoy the code reviews.

10. how do we make code reviews useful?

11. Code reviews SHOULD’T be performed to find errors in the code.
Code reviews SHOULD’T be performed to enforce coding standards.

12. Keep a positive attitude. remember: you are not the code!

13. Time, Your coworkers are waiting for you.

14. Code writer (before code review)
1. Document
2. At least 2 days before
3. Code revision number – JIRA open

15. Code writer (ing)
일단 각오해라.

16. Reviewer
Ask questions rather than make statements.

17. Reviewer
Avoid the "Why" questions.

18. Reviewer
Make sure the discussion stays focused on the code and not the coder.

19. Standard / Checklist

20. Moderator

21. Beware the "Big Brother" effect.