Eng1080 said:
My comment above about leaving a few mistakes in a plan set to see if a reviewer picks up on it is meant for somebody I've never worked with before, not somebody I already trust.
Yeah, I assumed that to be the case when I read your original comment.
Eng1080 said:
That seems a little harsh, but I get it.
Alright... softer then.
Like everyone's opinion on everything, mine is based on my unique experiences in peer review work which are these:
1) When I do peer review, it's usually a "favor" for the most part. Peer review is rarely a lucrative business opportunity. As with quizzing folks in job interviews, I feel that this sets up the rules of the road as far as the power dynamic and etiquette goes. If I'm doing someone a favor, I expect them to show me a certain amount of respect simply by virtue of my being an adult and a licensed professional.
2) Hiding mistakes on me in a
Where's Waldo fashion is subtly questioning both my professionalism and my competence. It's tough not to find that offensive in the context of favor doing. If I agree to paint your garage in exchange for a beer and a slice of pizza, I don't want to find out that you've been deliberately botching the wallboard taping to make it hard for me and thereby "test my skills". I can buy my own pizza.
3) I'm a pretty seasoned veteran when it comes to the whole SE thing. Even so, I find that most peer review clients have a handful of "hot button issues" that I can't anticipate unless they specifically tell me that they have bees in their bonnets when it comes to those things. As an example, I have a client that has had some bad experiences with fillet welding the radii of HSS to stuff. One one assignment, they mentioned their surprise that I didn't flag that as a "no go" in an exterior application. So now that's on the list of stuff that I check
for that client. My point is that every engineer has a shit list in their head of stuff to look out for. And, even with an excellent reviewer, their shit list is likely to be different from yours unless you've reviewed the shit list together at the outset.
4) In the kinds of peer review situations that I get into, I feel that the proper etiquette is this:
a) Vet me for the peer review work the usually way. Check out my resume, ask for some work samples, check a reference. Cross your fingers.
b) Take a chance on a smaller assignment and engage me for peer review without insulting me.
c) If you don't like my work, don't hire me again. Vote with your feet. Or refuse to pay me. It's small $$$ so I don't much care either way.
I feel as though this is how one normally does business with other grown ups in modern North America.
5) I'm sure that there are some crap peer reviewers out there. And I sympathize with your frustration if that has been a substantial part of your experience with peer review in the past. I suspect that much of that underperformance has something to do with this:
KootK said:
2) The biggest difficulty that I've had with peer review work in the past is that it always falls to the bottom of the priority heap. Nobody needs an MBA to know that peer review is a shit business model.
Well intentioned, competent reviewers may still struggle to do a good job of peer review because, to put it bluntly, it simply is not important work for them. I myself was surprised how difficult it is to do peer review work ethically for exactly this reason.
I once volunteered to do a pro-bono structural design for a new, Humane Society animal shelter (I like dogs). I underperformed on that assignment too, keeping folks waiting too long for the information that I owed them. Same thing. Pro-bono = less important than the work that pays the bills. I'm much more careful with what I take on these days.