I’m with you. The presumption to “educate,” the author is annoying and tedious. Unless the author asks for an opinion assume they know what they’re doing. Same

I’m with you. The presumption to “educate,” the author is annoying and tedious. Unless the author asks for an opinion assume they know what they’re doing. Same goes for review “comments,” that interrogate the author. “Why did you choose to use a for loop here?” is such a waste of time. I agree, stay within stylistic guidelines and lacking any try to use the same style as the file being edited. And just focus on the code itself: does it meet the specifications, is it clear that it does what it’s supposed to, are all the T’s crossed and I’s dotted? Good, go. Brevity is it’s own form of clarity when used well. Update ... and remember to leave your ego at the door! Talk about the code like an object of study.