3 ms·
Code review definitely is about communication. That’s arguably it’s biggest benefit. The author could test something himself, but code review facilitates a conv
by jrs95 8y ago
Code review definitely is about communication. That’s arguably it’s biggest benefit. The author could test something himself, but code review facilitates a conversation and keeps people on the same page.
- tonyarkles 8y agoMy experience is that people often can't test what they've been doing by themselves. They've got blind spots and assumptions that they can't see. They have a mental model for how a feature is supposed to work, and they test that mental model, but they don't test outside of that model.
- watwut 8y agoYes, this. Programmers are supposed to test their own code. And write tests. You are not supposed to have bugs for what you thought to test. Tester is for independent check you forgot about or did not knew about. Tester is so that you don't stop testing your code due to too much confidence. Without testing, programmers tend to not have feedback on bugs, tend to think they don't have them and then tend to produce more bugs in the long term. Not because they are lazy or bad, but because they are normal humans.