<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>reprex on Maëlle Salmon&#39;s personal website</title>
    <link>https://masalmon.eu/tags/reprex/</link>
    <description>Recent content in reprex on Maëlle Salmon&#39;s personal website</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Licence: &lt;a href=&#34;https://creativecommons.org/licenses/by-sa/2.0/&#34;&gt;CC BY-SA&lt;/a&gt;</copyright>
    <lastBuildDate>Tue, 13 Jul 2021 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://masalmon.eu/tags/reprex/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>How to become a better R code detective?</title>
      <link>https://masalmon.eu/2021/07/13/code-detective/</link>
      <pubDate>Tue, 13 Jul 2021 00:00:00 +0000</pubDate>
      
      <guid>https://masalmon.eu/2021/07/13/code-detective/</guid>
      <description>Huge thanks to Hannah Frick for her useful feedback on this post! Vielen Dank!
This post was featured on the R Weekly podcast by Eric Nantz.
When trying to fix a bug or add a feature to an R package, how do you go from viewing the code as a big messy ball of wool, to a logical diagram that you can bend to your will? In this post, I will share some resources and tips on getting better at debugging and reading code, written by someone else (or yourself but long enough ago to feel foreign!</description>
    </item>
    
  </channel>
</rss>