<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Steve Simpson on Medium]]></title>
        <description><![CDATA[Stories by Steve Simpson on Medium]]></description>
        <link>https://medium.com/@data_steve?source=rss-cbc5620c9577------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ggFahmwTiiCmB3sF-8yjSg.jpeg</url>
            <title>Stories by Steve Simpson on Medium</title>
            <link>https://medium.com/@data_steve?source=rss-cbc5620c9577------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 17 May 2026 19:16:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@data_steve/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Porting Medium to Jekyll Github.io with R]]></title>
            <link>https://medium.com/@data_steve/porting-medium-to-jekyll-on-github-3ac5f12c1836?source=rss-cbc5620c9577------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ac5f12c1836</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[r]]></category>
            <category><![CDATA[jekyll]]></category>
            <dc:creator><![CDATA[Steve Simpson]]></dc:creator>
            <pubDate>Tue, 22 Mar 2016 16:00:24 GMT</pubDate>
            <atom:updated>2016-03-23T04:46:11.747Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m porting my Medium page <a href="http://medium.com/@data_steve">medium.com/@data_steve</a> to host on Github using Jekyll at <a href="http://data-steve.github.io">data-steve.github.io</a>. I decided to do it with code and make a package out of it in case others might want to.</p><h4>Reasons</h4><p>R-bloggers does like Medium, since Medium will only share an excerpt of the post with a link to the rest. R-bloggers wants the whole post. Fair enough.</p><p>Its extra work, but I like the idea of being able to work within my own development environment. And instead of having to learn a bunch of keyboard shortcuts, I can write code and execute commands and push updates via Jekyll.</p><h4>Example</h4><p>Since I’m bothering to post this on Medium, I thought I’d get some use out of it. I’ll show how I did it as a post on my new blog.</p><p>Here’s a code chunk to round out my porting example</p><pre># test code<br>nothing_special &lt;- function(a){<br>    return(a)<br>}</pre><p>Here’s a screenshot of a random bit of the code from the R package I’m writing to show how the images are handled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/484/1*RDkVpxPfCqDY8YrRVUtSxA.png" /></figure><p>See you over at <a href="http://data-steve.github.io">data-steve.github.io</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ac5f12c1836" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Slack sends Code Snippets to Hotel California]]></title>
            <link>https://medium.com/@data_steve/slack-sends-code-snippets-to-hotel-california-efe78ad194c8?source=rss-cbc5620c9577------2</link>
            <guid isPermaLink="false">https://medium.com/p/efe78ad194c8</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Steve Simpson]]></dc:creator>
            <pubDate>Mon, 26 Oct 2015 13:06:10 GMT</pubDate>
            <atom:updated>2015-10-26T13:06:10.983Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>… We are programmed to receive.<br>You can check out any time you like,<br>But you can never leave. …</blockquote><p>That’s what it feels like sometimes when trying to share code snippets on Slack. Sure, it’s easy to drop some code on there; but getting it out?</p><h4><strong>Caveat Coder</strong></h4><p>That inviting little question, “Create a Snippet?”… You know the one that automagically appears when you go to paste in a code chunk into the chatbox?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*H8RPm7DZvqgcf4mI4mn8qw.png" /></figure><p>It’s a trap. You’ll be 3 steps into waiting for your browser to view the code before you get that snippet back out.</p><h4>Options</h4><p>I think it’s easier to wrap your code in block-code markdown using a pair of triple-backticks ```, like so :</p><pre>```<br>fantastic_function(sth)<br>```</pre><p>There’s still sometimes problems with selecting the code back out of a markdown block (no matter how you stab at it with your steely … touchpad), in that those trailing backticks can sometimes find their way into your code. But it’s still faster than the snippet functionality (at present) and more prettified than just dropping the code chunk in as raw text.</p><h4>Get In Line Here</h4><p>Slack’s a great productivity tool, which I use all day, everyday at work; and I’ve already sent them a comment regarding this. Their customer service was super prompt, assuring me they’ll thinking about this.</p><p>I’m taking this nod towards code snippets as the start of good things. But I’m still exploring other options than current functionality for sharing code. If you have any ideas, send ’em my way at @data_steve</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efe78ad194c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>