23. Why when what
When do I need to do it?
Early as possible because …
❏ I want to help
❏ I know that code rots
❏ I don’t like to do repeated work
❏ I have knowledge to pass
❏ I have a strong opinion about how it should be done
❏ I am new in the project
❏ I want to learn
30. Why when what
What exactly am I looking for?
As machine ...
❏ code standards/style
❏ tests (units, functional, end2end)
❏ acceptance criteria
❏ etc ...
As human ...
❏ readable code
❏ design & architecture
❏ solution achieved
40. Effective code review
1. Fully understand the 'why', 'when' and 'what' of receiving or doing a
code review.
1. 10 commandments of Egoless Programming
41. 10 commandments of
Egoless Programming
Egoless programming is a style of computer programming in which personal factors are minimized so that quality
may be improved. The cooperative methods suggested.
43. 2. You are not your code.
10 commandments of
Egoless Programming
44. 10 commandments of
Egoless Programming
3. No matter how much “karate” you know, someone else will always know
more.
45. 4. Don’t rewrite code without consultation.
10 commandments of
Egoless Programming
46. 5. Treat people who know less than you with respect and patience.
10 commandments of
Egoless Programming
47. 6. The only constant in the world is change.
10 commandments of
Egoless Programming
48. 7. The only true authority comes from knowledge, not from position.
10 commandments of
Egoless Programming
49. 8. Fight for what you believe, but gracefully accept defeat.
10 commandments of
Egoless Programming
50. 9. Don’t be “the guy in the room.”
10 commandments of
Egoless Programming
51. 10 commandments of
Egoless Programming
10. Critique code instead of people — be kind to the coder, not to the code.
52. Effective code review
1. Fully understand the 'why', 'when' and 'what' of receiving or doing a
code review.
1. 10 commandments of Egoless Programming
1. Remember “You only live with the problems you have ‘accepted’ ”
53. Code review is...
and a great way to learn collaboratively
A formal assessment of code with the intention to check the changes ...