<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Almost Random</title>
    <link>http://malte-grosser.com/post/</link>
    <description>Recent content in Posts on Almost Random</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2017-2023 Malte Grosser</copyright>
    <lastBuildDate>Sun, 01 Jan 2017 00:00:00 +0100</lastBuildDate>
    
	<atom:link href="http://malte-grosser.com/post/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Introducing the snakecase package</title>
      <link>http://malte-grosser.com/post/introducing-the-snakecase-package/</link>
      <pubDate>Tue, 06 Mar 2018 00:00:00 +0000</pubDate>
      
      <guid>http://malte-grosser.com/post/introducing-the-snakecase-package/</guid>
      <description>There are many style guides out there which recommend specific naming conventions for programming languages. At 2017’s useR conference Rasmus Bååth showed quite impressively the variety of cases which even exist within base R in his talk “The current state of naming conventions in R”.
However, consistent style is not only about naming new objects.
ImportWhen you do a data analysis, most of the data already exists and you import it from disk, an API or a database.</description>
    </item>
    
  </channel>
</rss>