2 ms·
I picked up this book yesterday, and I'm now about 2/3 the way through (I skipped or skimmed about 1/4 of what I've got through - I'm reading for fun, and the r
by denton-scratch 5y ago
I picked up this book yesterday, and I'm now about 2/3 the way through (I skipped or skimmed about 1/4 of what I've got through - I'm reading for fun, and the returns seem to be diminishing).
I appreciate the author's frankness about the limitations he's working under: if there's no data available about some topic, he doesn't discuss that topic. In fact he's pretty rigourous about 'following the data'.
I think I would like just a little bit more speculation about e.g. developer motivations. And it's a shame there's not enough data to support an analysis of modern development paradigms such as TDD, pair-programming and so on. Of course that's not the author's fault; anyway, in a sense, the absence of data is itself interesting.
I've found the book interesting. I think there are too many 'data dumps', i.e. descriptions of datasets that don't cast much light on anything.
I think I'd find a review or abstract that distils the book useful and engaging.