성공적인코드리뷰 문화 사내 발표
•Download as PPTX, PDF•
0 likes•511 views
The document discusses tips for a successful code review. It outlines three types of code reviews: pair programming, formal code review, and lightweight code review. It emphasizes that code reviews should focus on improving code quality and sharing knowledge, rather than finding faults. Reviewers are advised to ask questions instead of making statements, avoid "why" questions, and keep discussions focused on code instead of people. Writers should document code and allow time before reviews.
성공적인코드리뷰 문화 사내 발표
- 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 ܳپDz”
- 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.
- 20. Moderator
- 21. Beware the "Big Brother" effect.