I agree with you. My point, if it wans't clrear, is that I think correct naming is a prerequisite to finding design flaws in review ! Hence we have the same ultimate goal :-)
I don't find that to be the case. I'm usually looking for bigger things like:
1. making multiple trips to a relational database when a single statement joining tables can make it one trip;
2. not handling exceptions that can cause data loss or data corruption.
(I'm not trying to be exhaustive. The examples above are common ones I've seen regularly and they make me cringe.)
I don't need to know the variable names used in these cases. The very act of not using a relational database properly or not handling exceptions is easy to spot.
