Comment by SkiFire13

> I've been thinking about this in art. Is it the end result that matters, or the process of creating it?

What is the "end result" you're talking about here?

Programs are complex beasts, you cannot just quickly look at them and get an idea of what's they are actually doing. You might look at the behavior of the program in some limited circumstances, but that will make you blind to all the other situations where bugs will likely hide! In the end a code review is looking at what the "end result" is, and it requires quite a lot of effort!

So without knowing what the end result is, how can you justify the effort for such code review? And that's where the process comes in, as an indicator of what to expect.