[jacksonh]

I've always found code review to be incredibly valuable. I remember a long time ago reading that NASA studied a bunch of different development methodologies and found code review to be the most effective at reducing defects. However, we already sit in front of our computers too much, and its hard to shift mindsets from coding to editing.

The iPad seemed like a good alternative to reviewing code on your computer. You can get away from your desk, and change your mindset.

[callahad]

There's an interesting paper from a few years back looking at software defect incidence in Windows Vista and trying to figure out what models did best at predicting error-prone modules.

Turns out, in that case, organizational structure had better precision and recall than any of five other models (code churn, cycolmatic complexity, test coverage, etc.)

"The Influence of Organizational Structure on Software Quality: An Empirical Case Study" -- http://research.microsoft.com/pubs/70535/tr-2008-11.pdf

[jacksonh]

This is awesome. Thanks. Love this kind of stuff. If you are interested there is a book "Making Software: What Really Works, and Why We Believe It" that takes a scientific approach to evaluating software practices.