"Advanced R" by Hadley Wickham is widely considered the best resource to improve your knowledge at R. However, going through it and answering every exercise takes a long time. This guide is designed to give you the most essential parts of Advanced R so that you can get going right away. It still will take a long time, but not as long.
--
1.) Quickly skim these chapters (without doing the exercises) to make sure you're familiar with the concepts:
Git is the key tool we use to allow multiple people to work on the same code base. Git takes care of merging everyone's contributions smoothly. Hence, learning how to use Git is critical to contributing to open source.
Exercise 1: Go through the Try Git Guide
Exercise 2: Learn How to file a github issue.
| #!/bin/bash | |
| # | |
| # generate a Markdown version of a word document. Goes in separate folder, since | |
| # images are extracted and converted as well (separate folder avoids naming clashes). | |
| # | |
| # REQUIREMENTS: pandoc | |
| # | |
| # | |
| # with pandoc | |
| # --extract-media=[media folder] |
"Programs should be written for people to read, and only incidentally for machines to execute." -- Structure and Interpretation of Computer Programs
"How would you define good code? [...] After lots of interviews we started wondering if we could come out with a definition of good code following a pseudo-scientific method. [...] The population is defined by all the software developers. The sample consists of 65 developers chosen by convenience. [...] The questionnaire consists in a single question: “What do you feel makes code good? How would you define good code?”. [...] Of those, the most common answer by far was that the code has to be Readable (78.46%), almost 8 of each 10 developers believe that good code should be easy to read and understand." -- "What is Good Code: A Scientific Definition"
A lot of important government documents are created and saved in Microsoft Word (*.docx). But Microsoft Word is a proprietary format, and it's not really useful for presenting documents on the web. So, I wanted to find a way to convert a .docx file into markdown.
On a mac you can use homebrew by running the command brew install pandoc.