
Member of @rweekly_org team. Opinions are my own. #rstats #shiny #rweekly #dogowner Blog: https://xitter.gq/t.co/bQKEEf1Et4 https://xitter.gq/t.co/BxS12rNZHw
- Tweets961
- Following110
- Followers154
- Likes2.2K

ALT There are many benefits to turning your R scripts or functions into a package, like making your code easier to re-use, easier to share with others, easier to document, and easier to test. But the process of writing a package can feel intimidating, especially if you haven't done it before. But it doesn't need to! In this interactive workshop, we'll discuss:* What things you need to make a package and how to create them* How to write functions (in a package-friendly way) and add them to a package* How to write documentation and examples for functions* Best practices for package development* How to share your package with other people* Useful resourcesBy the end of this workshop, you will have made an R package! The session aims to be introductory, so you don't need any previous experience of building R packages (or even writing functions!) but some basic knowledge of R will be useful. If you're already a seasoned R package developer, you're also welcome to attend and hopefully you'll sti

ALT Screenshot of webR REPL application running in a web browser. The interface is split into two panels: on the left is a code editor containing the R command 'plot(1:10)', and on the right is the resulting scatter plot visualization showing 10 points plotted from coordinates (1,1) to (10,10). The plot has 'Index' labeled on the x-axis and values from 0 to 10 on the y-axis. The browser interface shows typical web app controls including Run, Save, and Share buttons at the top

ALT Screenshot of GitHub repository documentation for "R Package CRAN Submission Action". The page shows the project title, followed by a description explaining that this GitHub Action automates checking and submitting R packages to CRAN, performing necessary checks and creating tracking issues. Below is a "Usage" section with YAML code example showing how to implement the action in a workflow file. The code demonstrates configuration for triggering on pre-releases, setting up permissions for reading contents and writing issues, and defining action parameters including directory paths and error handling options. The bottom text states that this workflow will trigger on pre-releases and submit the package to CRAN.

ALT Inspired by my work on Obsidian Web Clipper I created Defuddle, an open source library to replace Mozilla's Readability in my projects. Defuddle extracts the main content from web pages. It's a bit more forgiving and tunable to my preferences. Notably, Defuddle uses a website's mobile styles to find unnecessary elements that can be removed from the page.














