CHAPTER: Introduction & Epilogue

[ljwolf]

Introduction:

• acknowledgement/caveat emptor that the code will change in the future.
• motivation for writing & concerns at the time of the book
  • why a book on this stuff
  • why does this book avoid other stuff
  • why a book this way

Epilogue:

• where to go for next steps and open areas of research.
• the book offers more than just guidance about packages
• style that we presented it provides ways to move forward that we do not directly document.

[sjsrey]

https://hackmd.io/QQ3qcoQhTBmPDbDLKvigag

[darribas]

xref #155 for the prologue/introduction and #205 for reference. I think this supersedes, so will close those but we can always return.

[darribas]

Update: we've added the space to add the epilogue in the book with #260

[darribas]

Thoughts to discuss from giving SJR & LJW sections a read (some edits and my bit added in acd9cc4):

• We use "data scientific" as a way to describe elements "from data science". Is this standard? Or, more importantly, are we OK? Probably so, but I wanted to note it as I don't think I've seen it anywhere else in the book.
• We have repeated the structure of "what this book is/what is not" and "what this book contains/what it doesn't". Maybe this is also fine, it just sounds a bit repetitive. Again, just flagging it.
• On why a book this way, we say "The book is written to develop everything shown from scratch". This is not really the case with datasets, which we prepare ahead of the book. Should we mention it?
• That section too reads a bit unfinished at this point (e.g., single sentences, less narrative), should we give it a further pass?
• I'm not sold on the title "the book with the perspective of the future". To discuss further.

[darribas]

After @ljwolf's pass merged in #270, this is good to go, so moving to with-publisher