diff --git a/communicate.Rmd b/communicate.Rmd index 27483e8..0a9dca2 100644 --- a/communicate.Rmd +++ b/communicate.Rmd @@ -2,14 +2,18 @@ # Introduction -The successful completion of a data science project you will have built up a good understand of what is going on with the data. It doesn't matter how brilliant your understand is unless you can communicate it with others. You will need to share your work in a way that your audience can understand. Your audience might be fellow scientists who will want to reproduce the work, non-scientists who will want to understand your findings in plain terms, or yourself (in the future) who will be thankful if you make your work easy to re-learn and recreate. __Part 5__ discusses communication, and how you can use RMarkdown to generate reproducible artefacts that combine prose and code. +Parts 1 through 4 have shown you how to understand what is going on in your data, but it won't matter how well you understand your data if you cannot communicate what you find with others. To be effective, you will need to share your work in a way that your audience can comprehend. Your audience might be + +* fellow scientists who will want to reproduce the work +* non-scientists who will want to understand your findings in plain terms +* or yourself (in the future) who will be thankful if you make your work easy to re-learn and recreate + +__Part 5__ discusses communication, and how you can use R Markdown to save and share your work in an incredibly efficient way. ```{r echo = FALSE, out.width = "75%"} knitr::include_graphics("diagrams/data-science-communicate.png") ``` -Reproducible, literate code is the data science equivalent of the Scientific Report (i.e, Intro, Methods and materials, Results, Discussion). - Recommendations for learning more about communication: For writing: [Style: Lessons in Clarity and Grace](http://amzn.com/0321898680),