Goldilocks and the Three Code Reviews
@vaidehijoshi
π» π» π»
ππ½
π©π½βπ»
Β π
π
π
π€
π
πͺ
π
π©π½βπ»
Β π
π
π
π
π©π½βπ»
Β π
π
π
π
π
π
π
π
π
π
π
π
π
LGTM
LGTM
LGTM
LGTM
LGTM
π¨
π₯
π¨
π₯
π₯
π¨
π¨
π¨
π©π½βπ
π
oh no.
we really got this code review thing down!
lol j/k NOPE
we really got this code review thing down!
π€¦π½ββοΈ
Β π
There must be a better way of doing code reviews!
...Right?
Code Complete
catching problems at the βlowest-valueβ stage
π©π½βπ»
Β π
βquality gatesβ
π€
π
π©π½βπ»
π
π₯
Β π
collective ownership in construction
inspections
π©π½βπ»
Β π
defect-detection
not correction
short reviews
π©π½βπ»
Β π
Code Complete, 2nd Edition,
Steve McConnell
walk throughs
π©π½βπ»
Β π
working meetings
Peer Reviews in Software: A Practical Guide,
Karl E. Wiegers
Who is doing the review?
Energy
How much time are they spending on it?
big commits, large PR's, no context
unequal reviewsΒ
second-class citizens
π
π
π
What exactly are they saying or doing while reviewing?
Substance
And how?
tons of comments, little conversation
focusing on style/ syntax
ego over empathy
π
π
π
π©π½βπ»
π€·π½ββοΈ
ππ½
1. Β commit hooks
small wins
1. Β commit hooks
2. PR templates
small wins
1. Β commit hooks
2. PR templates
3. screenshots/gifs
small wins
1. Β commit hooks
2. PR templates
3. screenshots/gifs
4. linters
small wins
1. Β commit hooks
2. PR templates
3. screenshots/gifs
5. encapsulation
4. linters
small wins
1. Β commit hooks
2. PR templates
3. screenshots/gifs
5. encapsulation
4. linters
6. specific reviewers
small wins
1. Β review everyone: push for a culture that values vulnerability
2. develop empathy: call out the good stuff, too!
big wins
itπerπateπ
3.Β
iterate
iterate
start the conversation
π€
I love code reviews in theory.
In practice, they are only as good as the group thatβs responsible for conducting them in the right manner.
bettercode.reviews
β¨
thank you!
@vaidehijoshi
http://bit.ly/better-code-reviews
Better Code Reviews
By Vaidehi Joshi
Better Code Reviews
- 4,299