Does "In the Zone" programming actually provide quality and no-bug benefits comparable to pair programming? I suppose you could suggest that you would follow i

Does "In the Zone" programming actually provide quality and no-bug benefits comparable to pair programming? I suppose you could suggest that you would follow it up with a code review, but when you sum all the reviewing process to the coding process, does an organization end up spending more time coding/reviewing/fixing this portion of the codebase after either technique?