@liw
Couldn't agree more.
Bugs are found through automated things like CI and test suites. Review is for things that automated tools can't find, such as design flaws, code style issues, and advice.
Couldn't agree more.
Bugs are found through automated things like CI and test suites. Review is for things that automated tools can't find, such as design flaws, code style issues, and advice.
@mdione
Well, yes. 100% code coverage is a utopian desire that is probably not achievable in most real world code, and so yes review may still find bugs and that's good, and you should flag bugs if you see them in review.
It shouldn't be the goal of review though; review should not be about that, you should not focus on finding code bugs but instead you should focus on things the computer can't find.
@liw
Well, yes. 100% code coverage is a utopian desire that is probably not achievable in most real world code, and so yes review may still find bugs and that's good, and you should flag bugs if you see them in review.
It shouldn't be the goal of review though; review should not be about that, you should not focus on finding code bugs but instead you should focus on things the computer can't find.
@liw
- replies
- 1
- announces
- 0
- likes
- 0