<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pico on rostrum.blog</title>
    <link>https://www.rostrum.blog/tags/pico/</link>
    <description>Recent content in Pico on rostrum.blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 18 Apr 2021 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.rostrum.blog/tags/pico/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Make the simplest R package with {pico}</title>
      <link>https://www.rostrum.blog/2021/04/18/pico-pkg/</link>
      <pubDate>Sun, 18 Apr 2021 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2021/04/18/pico-pkg/</guid>
      <description>tl;dr I made {pico}, an R package for creating tiny R packages with the absolute minimum structure and content. The goal: to demystify package making.
 Function in a haystack I saw a @WeAreRLadies tweet from last week’s curator, @ShreyaLouis. The gist was ‘how can you be more organised when recalling and reusing your own R code?’
See the thread for ideas, but I had the same thought as Fabio: create a personal package of your frequently-used functions so you can invoke them whenever you want.</description>
    </item>
    
  </channel>
</rss>