Introducing the Recipe series

The Recipe series: an overview

My goal in this series is to explore the ‘why’ and the ‘how’ of doing quantitative language research. The content of this series will, in large part, overlap with resources available on doing Data Science, generally (see (Wickham and Grolemund 2017)), or in field-specific areas and domains (Beckerman, Childs, and Petchey 2017; Hodeghatta and Nayak 2016; Perlin 2017). However, this series will focus exclusively on issues and methods concerning language data and linguistic analyses through practical data sources and realistic examples.

I will assume little computing, programming, or statistical knowledge, but I hope to provide useful information for even the more experienced researchers and practicioners. Doing quantitative language research does not require programming skills, as there are many tools and graphical user interfaces (GUI) available to do basic to even quite complex language analyses without these skills, but programming, for most practicing data scientists, is a more efficient and effective strategy for approaching data analysis. This series will make use of the R programming language and the powerful Integrated Development Environment (IDE) RStudio.

Through R and RStudio I will cover organizational topics like software installation, accessing files, and project management all the way through reporting results and creating reproducible research. Along the way I will cover the fundamental concepts and methods for statistical language analysis including data acquisition, preparation, transformation, and visualization as well as data modeling for hypothesis testing and exploratory and predictive analysis.

As a primary goal this series represents an effort to document and share the knowledge and skills I have acquired over the years with those that have an interest in quantitative language and/or programming with R. There is, however, a second, more selfish goal: I aim to learn a lot in the process through consolidating and conveying my knowledge as well as recieving comments, feedback, and corrections from the community. To this end, please don’t hesitate to contact me with ideas for posts or suggestions or alternative approaches to existing posts.

OK. With that in mind, let’s get staRted!

References