I half expected the document to present statistical evidence about how programmers tend to behave, and use that to generate advice for compiler writers. The ar

I half expected the document to present statistical evidence about how programmers tend to behave, and use that to generate advice for compiler writers. The article is a nice read (and doesn't present that kind of statistical evidence), but I'm still wondering, has anyone done a significant study of how programmers work? I would be really fascinated to read an analysis of, say, data taken from full-time software engineers at a given company where all of their actions are recorded (key-strokes, compiler runs, error messages, etc.). Similar to how online competitive gamers have their actions recorded to the microsecond to identify weak points. It would even be interesting to know, e.g., what is the net average number of lines of code created/deleted per day?