Code review is crucial for the software development process. In his presentation, Sebastian explains why this is so important.

1. Have you ever wondered
about code review?
Sebastian Rabiej

2. https://wall.alphacoders.com/big.php?i=159225

3. About me
Java Developer
4 years professionally, 12 as a hobby
Looking for the meaning of words „being professional”
Mail: SebastianRabiej[AT]o2.pl
Twitter: @sebastianrabiej
Blog: pomiedzyliniamikodu.blogspot.com

4. How did it begin?

5. Code ReviewPeer Review

7. Code ReviewPeer Review

8. Ethics of the Physician
Ishāq ibn ʻAlī al-Ruhāwī (854 - 931)

10. I am a senior

11. You are not omnipotent

12. You are a unicorn

13. Kinda...

14. Know your teammates skills

15. 1. Novice
1. Advance Novice
1. Competence
2. Proficient
3. Expert
Skill levels

16. 1. Novice
1. Advance Novice
1. Competence
2. Proficient
3. Expert
4. Ninja Rockstar
Skill levels

17. Let them choose.

19. “Each junior’s mistake in production is a
mistake of a senior who did the code
review”
- Sebastian Rabiej

20. I am a junior

21. Or even a baby developer

22. Let them ask

24. Let's improve!

25. What do we gain from code review?

26. We are learning.

27. Increasing bus factor.

28. Can improve delivery time.

29. It is a marathon

30. Make decisions with the team

31. 1. Fagan inspection
1. Pair programming
1. Lightweight code review
Review types:

32. Do it the correct way

33. Know your enemy

34. My code
defines me

35. It is not a metric

36. Appreciate the effort

37. Evaluate code, not the author

38. Create an emotional sandwich

40. Only I can
approve

41. Everyone can do it

43. Don’t blame for bad review.

44. It is not my
code

45. We have blinkers.

46. Do a checklist

47. Focus on the domain

48. Use tools

49. Add to the development cycle

50. Brace yourself. Code review is coming!

51. Size of your code matters

52. Check yourself

53. Our goal

54. It is not a silver bullet

55. It is one of many tools

56. Thank you!