Exceptions prove rules not make them.
It's the same as viewing comments as a faulure to write readable code, or comming up with an accurate name.
Your description made sense to you at the time, and havng been doing this for a while you try not to shoot yourelf in the foot and make the description make sense to you and others later.
These aren't really rules, more like guidelines, following in some baked in standard and making your code less comprehensible is moronic, usually imposed by an MBA manager with delusions of competence.
Another one from my lengthy past. This guy had this idea (reducing cyclomatic complexity?) where there should only be one return point in a function and it should be the last intruction.
To do that he used flag variables, and infinite loop and then break after they were set....
So you'd see stuff like find one item
flag = false
While True
...
...
If x then
globalvariable = 10
flag = false
break;
endwhile
return flag
Course everybody unfamiliar with this "standard", is stumbling all over the code with a WTF expression on their face.
I wish I'd been there when he was, I'd have ripped him a new one.
