Member-only story
10 steps for better code reviews | You owe it to your team
The code is bits and bytes. It tells you exactly how your team thinks. Do you want to know your teams better? Do better code reviews.
This helps you be a better engineering manager, it also makes YOU a better engineer. The best part is that if you follow these 10 steps as a checklist, you can get started in 30 minutes or less, with any sized repo!
Writing good code that is manageable through change, requires years of experience. As an engineering leader, teaching good practices in tactical moments is the best way to grow your team and learn their strengths and weaknesses.
No engineer will learn SOLID principles just by reading a book and without applying them to real-world scenarios. Engineering managers need to help them through this journey.
Before you throw these 10 books at the team on how to write clean code, design clean architecture, follow DDD, and so on…
You need to continuously assess your team towards becoming better software engineers. Once you get going with these, the review process won’t take more than 1 hour per week (as you start looking at PRs over time).
