Why Software Builds Fail · Slashdot Mirror

Posted by Soulskill on Wednesday June 25, 2014 @06:05AM from the failure-to-bribe-the-hamster dept.

itwbennett writes: A group of researchers from Google, the Hong Kong University of Science and Technology and the University of Nebraska undertook a study of over 26 million builds by 18,000 Google engineers from November 2012 through July 2013 to better understand what causes software builds to fail and, by extension, to improve developer productivity. And, while Google isn't representative of every developer everywhere, there are a few findings that stand out: Build frequency and developer (in)experience don't affect failure rates, most build errors are dependency-related, and C++ generates more build errors than Java (but they're easier to fix).

1 of 279 comments (clear)

Min score:

Reason:

Sort:

Re:Because I'm lazy by mlts · 2014-06-25 06:36 · Score: 3, Interesting

When in CS, I had a prof that had one rule that for release (not beta/alpha/dev) code, if the code had even a single warning, it was unshippable unless there was an extremely good reason (which would be part of the README) of why it happened. Yes, this was a PITA, but he was trying to teach something that seems to have been lost.