RMarkdown Driven Development
summary
Workflow converts a single exploratory R Markdown into a tested, reusable package by removing hard‑coded values and moving inputs into RMarkdown parameters, replacing brittle paths with {here}, and deleting dead code; then it groups setup and heavy computation at the top, extracts repeated code into functions with roxygen2 docs, and saves processed artifacts to speed future knits. Project tools like usethis/devtools create an R/ and man/ layout, tests run with {testthat}, and pkgdown builds a website; automation fits via RStudio Connect.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:29This implicit analysis tool already contains core development and design components
- 3:51Parameters can protect the integrity of your analysis and your credentials
- 5:42Don't let your script become a junk drawer
- 7:41Enhance the navigability of your file in RStudio with chunk names and special comments
- 12:07Projects modularize components and make it easy to access individual project assets
- 13:39Pre-processing data decreases external system dependencies and knitting time
- 14:48There are many tools to help make a project, but consistency is the key!
- 16:34There is a near one-to-one mapping between the components of a project and a package
- 19:26Different stopping points optimize for recreation versus extension of your work
- 20:24No matter what path you chose, your RMarkdown analysis is closer to a sustainable and empathetic data product than you may think!
related talks
11mField Guide to Writing Your First R Package
24mHow to Write Reproducible Manuscripts
20mInstant Impact: Developing {docorator} to Simplify R Adoption for Teams
05mIntegrating R & Google Drive or Collaborative Research
18mBuilding Accessible Lessons with R and Friends
17mOddly Satisfying - Find delight in the mundane
19mIt's a Great Time to be an R Package Developer!
31mREADME Driven Development