NP-Hardass wrote: > >> or do they typically restrict review to a certain class of users? > > > >Hm, why would that end up happening? I'm not saying it can't, just > >that I don't understand why it would. What do you have in mind? > > Well, it was just proposed earlier in the thread that it could be > used for non-devs (primarily/only), hence two classes of users, > those subjected to review and those not.
Ah I understand. Personally I think review is just as important for devs as for non-devs. The big win with a review tool/flow is that it becomes *at all possible* for non-devs to contribute efficiently to the project, and if the review tool is good then giving review is also efficient. Some will always be more equal than others, but.. > An alternative is a situation where all users, developer and non > developer alike require review I feel that this is the only way to achieve the best quality. > with the review requirements different between the two I don't feel that this is as useful for quality. Devs produce crap too. It's important that the review flow is well-understood and efficient. It's important that everyone working is *motivated* to participate in review. I've had plenty of experience with smart people who simply do not want to participate in a review flow and that's all it takes for the review flow to fail. //Peter
