Projects, code, and other infrequently posted thoughts
Maintaining R packages on CRAN sometimes means you have to find creative ways to ensure that your code runs on different platforms and on multiple versions of R---even ones that haven't been released yet.
You don't have to be a web developer to have smooth flow and consistent style across your personal website or blog and your R package websites.
Building a beautiful website for your R package is a great way to improve its documentation, usability, and visibility. 'pkgdown' makes it easy to build your site, particularly if you follow these conventions.
The latest 'httptest' 📦 release provides tools for automatically redacting sensitive information from your test fixtures so that you never accidentally publish your auth tokens. It also includes a number of smaller fixes and enhancements based on user suggestions.
Here's the story of the time I wrote a R package for an undocumented web API in under an hour, with documentation and full test coverage. With the right tools, creating an API client can be quick and painless.
When you're writing an R package, you're writing software, and your decision to depend on another library should be made carefully. Here are some ways to use R itself to get more information about the cost of adding a dependency to your package.
When becoming an engineering leader means you don't have time to write code anymore, scratch your itch by automating some of your management duties.
Testing code that communicates with remote APIs can be challenging, but it doesn't have to be. The 'httptest' package for R makes testing HTTP code simple. Here are some examples of scenarios that are easily testable using httptest.
It's easy to automate the publishing of your R Markdown site to GitHub Pages. Free yourself to focus on content, and let Travis handle the rest.