Field Guide to Writing Your First R Package
summary
A biologist’s approach turns private analysis scripts into shareable R packages using usethis and devtools, GitHub for hosting, and testthat for tests; the workflow centers on a simple map of components (R code, documentation, DESCRIPTION, NAMESPACE, tests) and iterative commands document() and load_all() to change one thing at a time. Practical tactics include poking existing GitHub repos, using science poke investigations, running iterative change-one-thing experiments, and seeking out bugs; packages get built successfully and released via soft messaging and Mastodon.
AI-written summary · about
chapters (3)
related talks
22mRMarkdown Driven Development
21mDon’t repeat yourself, talk to yourself! Reporting with R
17mOddly Satisfying - Find delight in the mundane
05mBecoming an R blogger
04mWhy’d you load that package for?
22mCultivating Your Own R Ecosystem as a Solo Contributor
18mHow non-programmers can make sparks fly when using testthat during package development
15mDemystifying the art of creating custom libraries for your organization
