Izzi Bikun, a developer at Kroger, discusses best practices for code reviews including using learning and knowledge instead of comments, timeboxing new developers, only experienced developers reviewing alone or paired, writing tickets instead of comments, removing dead code, including tickets in commits, using tests as documentation, renaming variables, extracting code to methods, testing business logic, and trying code in a simulated environment rather than just writing tests.

1. Izzi Bikun,
Developer, Kroger
@Izzib76

2. Use Learning and
Knowledgeable instead.

3. Let them try things out. Timebox if
you’re not sure.

4. Knowledgeable
developers should only
drive when by
themselves or paired
with another developer
with similar
knowledge.

5. COMMENTS
ARE USELESS

6. Let’s explain what we’re about to do.

7. COMMENTS
ARE USELESS

8. • Write a ticket instead of leaving a commentToDo
• Remove it. This is what source control is forDead Code
• Include ticket numbers in git commits
• Use unit tests as documentationBug Fix
•Rename variables
•Extract code into well named methods
•Use unit tests as documentation
Business Logic

9. It can be 100% faked

10. More than just writing
unit tests. Spin up your
code and try to use it.

11. Izzi Bikun
@izzib76