./trevorcarnahan/Reducing Time to Insight.md

[timm]

After review, relabel to 'reviewTwo'. After second review, relabel to 'EditorsComment'.

[pgbovine]

Title of chapter

Reducing Time to Insight

URL to the chapter

https://github.com/ds4se/chapters/blob/master/trevorcarnahan/Reducing%20Time%20to%20Insight.md

Message?

Making it faster to get insights from data should be a top priority in any organization that wants to be innovative.

Accessible?

I think this chapter is very accessible.

My only suggestion for improvement is to break the "What to do" section into several smaller sets of bullet points. Right now 8 paragraph-long bullet points feels a bit overwhelming. Perhaps 2-3 groups would be better.

Also, there are a lot of references that are Web links; those might not be effective in a paper version of this book. (Just something to be aware of.)

Size?

Seems like the right length!

Gotta Mantra?

The current title is pretty straightforward and good. I can't think of anything snappier; maybe something incorporating the quote "There is immeasurable distance between late and too late." into the title would make it snappier? But I don't know how best to word it.

Best Points

I like how the author talks directly to the reader using "you", etc.; definitely keep that one-on-one conversational tone. Also good concrete examples such as Web search.

[tzimmermsr]

Review by @siravegas (moved from #112):

Review template

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

Reducing Time to Insight

URL to the chapter

https://github.com/ds4se/chapters/blob/master/trevorcarnahan/Reducing%20Time%20to%20Insight.md

Message?

What is the chapter's clear and approachable take away message?

Producing insights faster to improve results faster. Avoiding being too late.

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?

It is written for a generalist audience. It is already accessible.

Size?

Is the chapter the right length?

Yes.

Should anything missing be added?

No.

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).?

No.

What are the aspects of the chapter that authors SHOULD change?

1. Perhaps the "what to do" section could be organised in a way that the different items can be related to each other. As they are now they are a bit confusing. A possibility could be organising them according to the phases identified in the figure.

2. First paragraph of the chapter: "I'll assert are you are...".

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.

No need to change the title. Perhaps the author could consider adding something like: "Avoiding being too late" or something like that. Something that includes "too late" in the title.

Best Points

What are the best points of the chapter that the authors should NOT change?

In general, how the chapter has been written. I liked it all. The message is clear, and it is easy to understand.

[tzimmermsr]

Great chapter @trevorcarnahan ! Please prepare a final version of your paper by January 13 taking the reviewers' feedback into account, in particular improving the organization of the What to Do section to make it less overwhelming.

[trevorcarnahan]

Thanks for the review @pgbovine and @tzimmermsr. I've broken the 'What to do' section up a bit to make it more approachable.

• We all seem happy enough with the title, I'll defer to the esteemed editors if it needs to be snappier.
• I'll defer to the editors on the web references also.

Latest is in:
9905f29

[tzimmermsr]

Thanks @trevorcarnahan .

How about "Reduce Time to Insight" instead of "Reducing..." for the title? (That said, I'm fine also with keeping the title unchanged.)

The MK production team will figure out the web references.

Thanks,
Tom