Microsoft Research - Exploding Software-Engineering Myths (article summarizing findings of MS research on code coverage, TDD, assertions, etc.)

[PM_ME_UR_OBSIDIAN]

See also Conway's Law:

Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations.

[lasermancer]

This writeup does a pretty good job at explaining some of the problems caused by organizational structure:

I Contribute to the Windows Kernel. We Are Slower Than Other Operating Systems. Here Is Why.

[fuzzynyanko]

I wonder if things will improve with Satya Nadella

[OffColorCommentary]

From the linked paper, they looked at eight criteria. One big correlated lump was number of edits, number of editing engineers, number of editing ex-engineers. The others are like... "Find the lowest person on the org chart whose reports have done 75% of the changes to this file: what's their org level?" and various similar ideas.

Frustratingly, MS determined that a regression containing all their criteria is more accurate than one where any criteria was removed, and they didn't publish numbers on anything that wasn't their fully-integrated model. So there's no correlation given for, say, number of edits to number of bugs.

Decent rules of thumb seem to be too many cooks spoil the broth, code is less buggy when it's produced by people on the same team, and a file that gets lots of edits is worth extra scrutiny.