Do code reviews quickly! As I mentioned in a previous tip: https://lnkd.in/gpf42uw, reading code is a skill, and as you improve, you get faster. In addition to getting faster at reading code, starting a review quickly also has crucial benefits. In the middle of something? So are your coworkers! Getting good at rapid context switching is a significant skill in and of itself. If you are good at reading code, a review should not take you entirely out of your previous context. Please jump on reviews quickly, use your code reading skills to review it efficiently, and then jump right back into what you were doing. Doing so lets you practice context switching, and helps speed up your colleague’s work. It also creates an expectation for your colleague to do the same for you! Waiting for a review is one of the most frustrating aspects of being a software engineer, while an instant review is one of the most satisfying. Give your peers quick feedback; they will appreciate you for it. #bendevtip
Reading code is a skill. Writing code is a skill. They are not the same, and reading is arguably harder! A great time to practice reading code is through reviews, as it’s your chance to verify things are written according to your team’s style guidelines and function as expected. This context helps you read, as skimming through some random code samples you have no vested interest in won’t be nearly as effective at fully understanding what you are reading. The faster you can read code, the better, too! Speedy reviews are always appreciated, but balance speed with thoroughness. Striking that balance well is an invaluable skill for a software engineer, and the more you do it, the better you’ll get at it! Don’t shy away from code reviews; embrace the fear of missing issues. When you discover you missed something, learn from the miss. Make it a point not to miss that same issue again. Keep doing this, and you will develop a strong sense of what to look for in reviews, problems you naturally are good at finding and issues you need extra focus to find. Always be asking yourself when creating review comments, though: “does this matter?”. #bendevtip
