Review
Before filling in this review, please read our Advice to Reviewers.
(If you have confidential comments about this chapter, please email them to one of the book editors.)
Title of chapter
Log It All (or "Why a Little Data Can be Harmful")
URL to the chapter
https://github.com/ds4se/chapters/blob/d238e0fe97bf300360a9fc1e718ca7f32f5e17f2/gmurphy/logitall.md
Message?
What is the chapter's clear and approachable take away message?
I think it is an interesting topic and I like the way the author explains the problem by the example. I understand the problem and I think their recommendation is helpful and It has a potential of coming up new research questions. values
Accessible?
Is the chapters written for a generalist audience (no excessive use of technical terminology) with a minimum of diagrams and references? How can it be made more accessible to generalist?
Overall, the authors did a good job to generalize the idea for non- technical people.
Size?
Is the chapter the right length? Should anything missing be added? Can anything superfluous be removed (e.g. by deleting some section that does not work so well or by using less jargon, less formulae, lees diagrams, less references).? What are the aspects of the chapter that authors SHOULD change?
I believe the size of the paper is good and there is not any futile information that should be deleted. I would like to add one issue to what authors mentioned:
The authors suggest capturing some data such as developer face as the task is performed. And then they mentioned some issues: Another important issue is the cost of capturing data. I believe there should be a cost/ benefit analysis on data gathering as well. the mandatory perspectives must be determined.
The authors also gave an example about how software developers learn commands available in an integrated development environment. I am not sure how did they capture the learning curve of the developers. It would be useful to clarify how knowing what were the windows active on the screen would help them to get the context in which the commands was executed.
Gotta Mantra?
We encouraged (but did not require) the chapter title to be a mantra or something cute/catchy, i.e., some slogan reflecting best practice for data science for SE? If you have suggestion for a better title, please put them here.
If they would like to keep “Log It All” title I suggest to add a ‘?’ at the end.
Best Points
What are the best points of the chapter that the authors should NOT change?
The introduction about an elephant example is very good.
Review Before filling in this review, please read our Advice to Reviewers. (If you have confidential comments about this chapter, please email them to one of the book editors.) Title of chapter Log It All (or "Why a Little Data Can be Harmful") URL to the chapter https://github.com/ds4se/chapters/blob/d238e0fe97bf300360a9fc1e718ca7f32f5e17f2/gmurphy/logitall.md Message? What is the chapter's clear and approachable take away message?
I think it is an interesting topic and I like the way the author explains the problem by the example. I understand the problem and I think their recommendation is helpful and It has a potential of coming up new research questions. values
Accessible? Is the chapters written for a generalist audience (no excessive use of technical terminology) with a minimum of diagrams and references? How can it be made more accessible to generalist?
Overall, the authors did a good job to generalize the idea for non- technical people.
Size? Is the chapter the right length? Should anything missing be added? Can anything superfluous be removed (e.g. by deleting some section that does not work so well or by using less jargon, less formulae, lees diagrams, less references).? What are the aspects of the chapter that authors SHOULD change?
I believe the size of the paper is good and there is not any futile information that should be deleted. I would like to add one issue to what authors mentioned: The authors suggest capturing some data such as developer face as the task is performed. And then they mentioned some issues: Another important issue is the cost of capturing data. I believe there should be a cost/ benefit analysis on data gathering as well. the mandatory perspectives must be determined.
The authors also gave an example about how software developers learn commands available in an integrated development environment. I am not sure how did they capture the learning curve of the developers. It would be useful to clarify how knowing what were the windows active on the screen would help them to get the context in which the commands was executed.
Gotta Mantra? We encouraged (but did not require) the chapter title to be a mantra or something cute/catchy, i.e., some slogan reflecting best practice for data science for SE? If you have suggestion for a better title, please put them here.
If they would like to keep “Log It All” title I suggest to add a ‘?’ at the end.
Best Points What are the best points of the chapter that the authors should NOT change?
The introduction about an elephant example is very good.