Cracking the code review (Part 3): Be proactive | Hacker News Reader