point out, that even if you work solo, and, in a team, even before let's say "committing/submitting" your code... you can and should do a code review of your own code in your process. I know some people will say it is biased and some people just cannot see their own mistake. That is probably true for some people and to some extend, but in reality, there are a lot of people being able to do that and benefit from it. Of course someone might not get the benefit of peer feedback about how to do it better from an external source (including from "equal skill" developers). I still believe that skilled developers can improve their technique doing that. And for banal/common mistakes, they should be easier to spot on when looked separately from the main development process and since it is your code, it should be faster to go on. This should encourage you to develop good habits too when coding (if you are responsible for the code, you're the one that will scream about that lack of escaping/filtering/naming/etc. and you should develop habit to avoid those as much as possible). After finishing a development block, someone can and should just look at his whole output just like when we proof a text. For me it is common sense and it might be for your too, but you might be surprised, even among lot of "professional", the amount of people who submit code without testing, reviewing, etc. That being