Welcome to Magnifier in Hand, where I will be posting about being an SDET and their interactions with the software process.
You' re probably wondering, who is this guy? What qualifies him to be talking here?
Well, let me take the time to answer both of those questions. Currently, I'm a SDET on the PSIT group in MSIT. Prior to this role, I was a Developer for 4 years at Microsoft. I changed positions about 4 months ago and I'm currently exploring this new field and hoping to share my findings. If you want more information about my previous experience, here is a link to my old blog .
Alright, so let's get things rolling. My team has been implementing the practice full team code review. Therefore this is the first topic that I want to discuss (topics about code review will be discussed from now till the end of March). While a lot of my co-workers have asked me for examples of what to look for in code reviews, I'm going to start with the other most frequently asked question which is the following; How can I be helpful in the code review process if my coding skills are not as good as the developers?
The answer is the following: anyone can be helpful in a code review as long as he or she person has basic proficiency with the language at hand. I have made the following diagram to help assess your skill level and determine how helpful you will be in the process.
On my next blog post I'm going to cover what steps can be taken to increase your value as a reviewer and move up in this diagram.