<?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 Paul Lonsdale on Medium]]></title>
        <description><![CDATA[Stories by Paul Lonsdale on Medium]]></description>
        <link>https://medium.com/@PaulWritesCode?source=rss-d9552770204------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SrW85fZAK-fRkoaknUmwAQ.jpeg</url>
            <title>Stories by Paul Lonsdale on Medium</title>
            <link>https://medium.com/@PaulWritesCode?source=rss-d9552770204------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:30:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@PaulWritesCode/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[We’re using our phones all wrong]]></title>
            <link>https://medium.com/@PaulWritesCode/we-re-using-our-phones-all-wrong-e8af15371786?source=rss-d9552770204------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8af15371786</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Paul Lonsdale]]></dc:creator>
            <pubDate>Fri, 05 Jan 2018 20:19:13 GMT</pubDate>
            <atom:updated>2018-01-05T20:19:13.898Z</atom:updated>
            <content:encoded><![CDATA[<p>And it needs to stop <strong>now</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vsx2G8q5ZX1qg8KNqb2Klg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/Pvx24X1uiq4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">NeONBRAND</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>As the iPhone X (<em>read ten</em>) is released, it marks the 10th year anniversary of the iPhone, or smartphone as we know it. Steve Jobs, in his 2007 keynote revealing the iPhone, announced a device revolutionising the mobile phone.</p><blockquote>“Today, Apple is going to reinvent the phone.”</blockquote><p>Jobs would have severely underestimated the importance of this phrase. Look around you. How many people are on their phones? Chances are you’re reading this on your phone right now. This is precisely what I want to address.</p><p>Take a minute to think of the last time you used your phone for actual <em>phone</em> things; making calls, sending texts for a short conversation, maybe taking the odd picture or two. It’s probably recently. But then what happens? We get lost. Lost in a sea of information. Flooded by the endless streams of social media. Hours of our time get wasted, we forget to take in our surroundings. We lose out on human interaction.</p><p>Don’t get me wrong, I think the smartphone in its current format is great; we have the world at our fingertips, we can communicate anyone, anywhere. However, it’s the limits we <em>don’t </em>impose on ourselves which leads us to us these devices wrongly.</p><p>How many times a week do you charge your phone? Perhaps once a day is the average, probably leaving it to charge overnight while it can be left without the urge to want to use it. With that said, let’s take a quick look at the current averages for battery life on an iPhone 8 (as it’s the typical of a smartphone):</p><ul><li>Talk time: 14 hours</li><li>Internet use: 12 hours</li><li>Video playback: 13 hours</li><li>Audio playback: 40 hours</li></ul><p>So let’s pause again. Notice how many times we charge our phones a week. Once a day, or every two if we’re lucky. Now that says something. We’re attached to them. They’re our security blankets.</p><p>If we find ourselves in an uncomfortable situation, we try to escape into our phones. Not happy with the people we’re currently with? Again, let’s pull out our phones. Similarly, we are constantly seeking the dopamine a new notification subconsciously gives us. This is what we need to stop. We need to stop using our phones for gratification and get back to using them for what they are, <em>phones</em>.</p><p>You may have already noticed the <a href="http://www.wnyc.org/series/bored-and-brilliant/">Bored and Brilliant challenge</a>. If you haven’t, give it a go, it’s well worth it. Once you’ve tried it, join me in a challenge; let’s make our phones be our phones again. Let’s try to use them just as a phone, even if it’s for a day, then two, then a week, then maybe, just maybe, we can redefine our lives.</p><p>Let’s get back to having time to think, escaping from the always-on world, the never-ending scrolling. It’s not good for anyone. Reclaim your time; let’s get back to human interaction.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8af15371786" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Progress is great, rapid progress is not]]></title>
            <link>https://medium.com/@PaulWritesCode/progress-is-great-rapid-progress-is-not-cd34762c2701?source=rss-d9552770204------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd34762c2701</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[progress]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Paul Lonsdale]]></dc:creator>
            <pubDate>Mon, 28 Aug 2017 14:48:59 GMT</pubDate>
            <atom:updated>2017-08-28T15:05:23.471Z</atom:updated>
            <content:encoded><![CDATA[<p>Are you a tortoise or a hare?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TbOwBR31Wgk6a24NVdD1Vg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/KvHT4dltPEQ?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Gary Bendig</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Let’s take a minute to cast our memories all the way back to ‘The Tortoise and The Hare’. There’s a slow-moving tortoise and fast-moving hare, and, automatically, we would presume it is the fast-moving hare that wins the race. But (<em>spoiler alert</em>) this is not the case. In fact, it’s much the opposite. The tortoise wins the race.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*0S7fZrfsaqiMLT1AG58z6g.png" /></figure><p>The moral of the story is no matter how fast you think you are, or how quick you think you can accomplish something, it’s all about the process. The end result doesn’t help you grow as a person, but everything you take in along the way does and that’s why trying to move too fast means everything becomes a blur.</p><p>Returning to Aesop’s fable, let’s think about the process between the tortoise and the hare. The hare moves quickly, the tortoise does not. Imagine for a second that this is no longer a race. Let’s make it technical and assume that the tortoise and the hare have to work independently to produce a product to market. Now, depending on how good your imagination is, you may be visualising a tortoise and a hare sat with their laptops, the hare typing rapidly and tortoise typing slowly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gUQdsamUZz3C9Omv-Gh0qA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/X29UcYNM7Vc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Miriam Miles</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Defining the process</h4><p>Our new fable so far consists of a tortoise and a hare both having full technical knowledge of how to develop a product, of which they have been given a brief and now have to define the audience and build it accordingly.</p><p>A tortoise is slow (<em>I’m sorry if you’re a technical tortoise reading this, I don’t mean to judge</em>) whereas a hare is much faster. Again, it would be presumed that the hare would win this race as it would want to work at full speed to produce something ready to ship. But let’s just pause and realise it’s not who gets there first, or who is the fastest, it’s the product that is the most thought out that will be the most appealing.</p><p>For that reason alone, the slow tortoise is likely to be more methodical, thoughtful and build a more considered product. Again, another win for the tortoise.</p><p>It’s more likely that the product of the tortoise is better than that of the hare (<em>sorry hare, I judged tortoise a little earlier, now it’s your turn, I do apologise</em>). So this becomes the lesson of the technical tortoise and hare story: <strong>it’s not about how quick you get there or how much you produce, it’s the quality. </strong>Remember that old phrase ‘quality over quantity’, perhaps not as old as Aesop’s fable, but it is still extremely important.</p><h4>Take a break</h4><p>Just in case you skipped the heading, I mean this: <strong>take a break.</strong></p><p>Before you start judging me like I did the tortoise and the hare, let me explain. This is completely against the fable, but you should take a break. The process is all about taking a break. Do something. Stop. Do something unrelated to the process. Go back to the something.</p><p>It’s tempting, especially in the web industry which I work in, to be caught up in the new and shiny, to be expected to know everything and understand the latest and greatest. However, your number one priority is you. Rest when you need to. Relax when you’ve had enough. Most importantly, <em>walk away</em> when you hit a problem. It’s likely your subconscious mind will fix it for you when you return. Besides, a hare running so fast that it suddenly bursts into flames is no good to anyone; burnout is a real thing.</p><h4>Life isn’t a race</h4><p>You don’t want to grow to dislike what you’re doing. There is no rush. There is no race. There is no technical tortoise or hare. We’re all just humans (more on that in the future).</p><p>It’s about enjoying the process, doing what you enjoy and learning new processes. The way I see it is that each project is a chance to learn, whether it’s a small side project or huge commercial project, this is your chance to question everything you do to find out if you can improve yourself and your work.</p><p>Continue to grow. Continue to challenge yourself.</p><p>Continue to make progress, but not <em>rapid progress</em>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd34762c2701" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ruby on Rails with Visual Studio Code]]></title>
            <link>https://medium.com/@PaulWritesCode/ruby-on-rails-with-visual-studio-code-bc5681a2c098?source=rss-d9552770204------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc5681a2c098</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[rails]]></category>
            <category><![CDATA[visual-studio-code]]></category>
            <dc:creator><![CDATA[Paul Lonsdale]]></dc:creator>
            <pubDate>Sat, 26 Aug 2017 15:25:14 GMT</pubDate>
            <atom:updated>2019-12-18T20:46:11.052Z</atom:updated>
            <content:encoded><![CDATA[<p>A <a href="https://rails.readandwrite.io/ruby-on-rails-with-visual-studio-code/">follow up version of this post in now available on my blog Read and Write: Rails</a>. The original version is kept below for archival.</p><p>Here’s my set up for optimising Visual Studio Code for Ruby on Rails development. I’ve been using it for just over a week and I have to say, I’m really enjoying it!</p><p>After two or so years with Atom as my daily driver, it’s time to say goodbye. It’s not you, Atom, it’s me. I’ve changed. With that said, let’s stay friends, you enabled me to create many amazing projects and for that, I am grateful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*oRZJdK1AUiPVSyjXbIeHdA.png" /></figure><p>I originally looked at Visual Studio Code back in the early days, perhaps when I deciding to use Atom full-time. Atom won at the time. But Visual Studio Code has come a long way since then and after a recent discussion with a friend, I made the switch. I work mainly with Ruby on Rails, Sass, the typical front-end stack and ERB for Rails views.</p><p>Here’s my current setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wy8Y5MJXEqLJQoo2nSki0Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/0l1QuxkBDUw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Marcin Nowak</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Theme</h3><p>Before we get started, I use ‘Solarized Dark’. This is built in.</p><p>On a Mac, go to ‘<em>Code</em>’ &gt; ‘<em>Preferences</em>’ &gt; ‘<em>Color Theme</em>’ and choose ‘<em>Solarized Dark’</em>.</p><p>For Windows, replace ‘<em>Code</em>’ with ‘<em>File</em>’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7aJPlxn8gwhI7JjcBFr-tQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/fPkvU7RDmCo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Caspar Rubin</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Extensions</h3><p>Let’s list through the extensions I’m currently using with a brief explanation as to why I have it.</p><p><a href="https://marketplace.visualstudio.com/items?itemName=ms-vscode.atom-keybindings"><strong>Atom Keymap</strong></a><br>This extension makes migrating much easier; I would be lost without knowing the keyboard shortcuts.</p><p><a href="https://github.com/mrmlnc/vscode-csscomb"><strong>CSScomb</strong></a><br>I like my CSS refined and use CSScomb to create a <a href="http://csscomb.com/config">custom configuration</a>, which I then reference in my configuration (more on that later!).</p><p><a href="https://marketplace.visualstudio.com/items?itemName=mrmlnc.vscode-duplicate"><strong>Duplicate action</strong></a><strong><br></strong>I find duplicating files a lot easier than recreating them for those which are similar, such as uploaders, so this extension is extremely useful.</p><p><a href="https://marketplace.visualstudio.com/items?itemName=vincaslt.highlight-matching-tag"><strong>Highlight matching tag</strong></a><br>Sometimes I just need to find the opening tag for something, so this extension helps with that.</p><p><a href="https://github.com/rubyide/vscode-ruby"><strong>Ruby</strong></a><br>I don’t think I could have switched from Atom if it wasn’t for this. I use Rubocop for linting and this helps with that, along with code formatting and lots of other great things to make day-to-day development that much easier.</p><p><a href="https://marketplace.visualstudio.com/items?itemName=misogi.ruby-rubocop"><strong>Ruby Rubocop</strong></a><br>This is almost like revealing a secret, but rather than fix some linting errors, I automate the process and use this extension to help me do that.</p><p><a href="https://marketplace.visualstudio.com/items?itemName=mrmlnc.vscode-scss"><strong>SCSS IntelliSense</strong></a><br>It’s the little things that help make development easier and this is something that Atom didn’t quite do for me, so I use this to help suggest syntax while writing SCSS.</p><p><a href="https://marketplace.visualstudio.com/items?itemName=vortizhe.simple-ruby-erb"><strong>Simple Ruby ERB</strong></a><br>As I mentioned earlier, I use ERB for writing Rails views so this helps with that, it’s a small thing that makes a difference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v1yjlUhKpqtA2N_4fsO_AQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/wbXdGS_D17U?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ilya Pavlov</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Tasks</h3><p>I use a command line task to copy the <em>tasks.json</em> file in to every project, until global tasks become a thing. Currently, I use the tasks to install the gems for the extensions above, as I use rbenv. I also have additional tasks to help with Rails, such as console, server and Capistrano for deployment. In addition, I’ve configured tasks for rspec so I can have everything in one place (and use a keyboard shortcut to activate).</p><p>Additional tasks for htmlbeautifier and Rubocop gems also make things easier, so it can be maintained across the project.</p><p>I’ve included my tasks.json below, simply copy this in to your project root &gt; ‘<em>.vscode</em>’ &gt; ‘<em>tasks.json</em>’. The first task you should run is ‘<em>configure</em>’ to install the gems required for the extensions.</p><pre>{</pre><pre>// See https://go.microsoft.com/fwlink/?LinkId=733558</pre><pre>// for the documentation about the tasks.json format</pre><pre>&quot;version&quot;: &quot;2.0.0&quot;,</pre><pre>&quot;tasks&quot;: [</pre><pre>{</pre><pre>&quot;taskName&quot;: &quot;beautify&quot;,</pre><pre>&quot;type&quot;: &quot;shell&quot;,</pre><pre>&quot;command&quot;: &quot;htmlbeautifier ${relativeFile}&quot;,</pre><pre>&quot;problemMatcher&quot;: [],</pre><pre>&quot;presentation&quot;: {</pre><pre>&quot;reveal&quot;: &quot;never&quot;</pre><pre>}</pre><pre>},</pre><pre>{</pre><pre>&quot;taskName&quot;: &quot;rubocop&quot;,</pre><pre>&quot;type&quot;: &quot;shell&quot;,</pre><pre>&quot;command&quot;: &quot;rubocop --auto-correct ${relativeFile}&quot;,</pre><pre>&quot;problemMatcher&quot;: [],</pre><pre>&quot;presentation&quot;: {</pre><pre>&quot;reveal&quot;: &quot;never&quot;</pre><pre>}</pre><pre>},</pre><pre>{</pre><pre>&quot;taskName&quot;: &quot;rspec&quot;,</pre><pre>&quot;type&quot;: &quot;shell&quot;,</pre><pre>&quot;command&quot;: &quot;bundle exec rspec&quot;,</pre><pre>&quot;problemMatcher&quot;: [],</pre><pre>&quot;presentation&quot;: {</pre><pre>&quot;reveal&quot;: &quot;always&quot;</pre><pre>}</pre><pre>},</pre><pre>{</pre><pre>&quot;taskName&quot;: &quot;rspec file&quot;,</pre><pre>&quot;type&quot;: &quot;shell&quot;,</pre><pre>&quot;command&quot;: &quot;bundle exec rspec ${relativeFile}&quot;,</pre><pre>&quot;problemMatcher&quot;: [],</pre><pre>&quot;presentation&quot;: {</pre><pre>&quot;reveal&quot;: &quot;always&quot;</pre><pre>}</pre><pre>},</pre><pre>{</pre><pre>&quot;taskName&quot;: &quot;rails c&quot;,</pre><pre>&quot;type&quot;: &quot;shell&quot;,</pre><pre>&quot;command&quot;: &quot;bundle exec rails console&quot;,</pre><pre>&quot;problemMatcher&quot;: [],</pre><pre>&quot;presentation&quot;: {</pre><pre>&quot;reveal&quot;: &quot;always&quot;</pre><pre>}</pre><pre>},</pre><pre>{</pre><pre>&quot;taskName&quot;: &quot;rails s&quot;,</pre><pre>&quot;type&quot;: &quot;shell&quot;,</pre><pre>&quot;command&quot;: &quot;bundle exec rails server&quot;,</pre><pre>&quot;problemMatcher&quot;: [],</pre><pre>&quot;presentation&quot;: {</pre><pre>&quot;reveal&quot;: &quot;always&quot;</pre><pre>}</pre><pre>},</pre><pre>{</pre><pre>&quot;taskName&quot;: &quot;cap production deploy&quot;,</pre><pre>&quot;type&quot;: &quot;shell&quot;,</pre><pre>&quot;command&quot;: &quot;cap production deploy&quot;,</pre><pre>&quot;problemMatcher&quot;: [],</pre><pre>&quot;presentation&quot;: {</pre><pre>&quot;reveal&quot;: &quot;always&quot;</pre><pre>}</pre><pre>},</pre><pre>{</pre><pre>&quot;taskName&quot;: &quot;configure&quot;,</pre><pre>&quot;type&quot;: &quot;shell&quot;,</pre><pre>&quot;command&quot;: &quot;gem install ruby-debug-ide:0.6.0 debase:0.2.2.beta10 rcodetools rubocop fastri htmlbeautifier --no-ri --no-rdoc&quot;,</pre><pre>&quot;problemMatcher&quot;: [],</pre><pre>&quot;presentation&quot;: {</pre><pre>&quot;reveal&quot;: &quot;always&quot;</pre><pre>}</pre><pre>}</pre><pre>]</pre><pre>}</pre><h3>Further settings</h3><p>I’ve also included a copy of my <em>settings.json</em> so you can see how I exclude files within search and quick open that are not relevant to me.</p><p>Of course, I’ve disabled minimap, set the tab size to be two spaces, the ruler to be at 80 columns and files to autosave.</p><p>This is also where you should replace ‘<em>/path/to/csscomb.json</em>’ to where you have your CSScomb file saved.</p><pre>{</pre><pre>&quot;files.autoSave&quot;: &quot;onFocusChange&quot;,</pre><pre>&quot;workbench.colorTheme&quot;: &quot;Solarized Dark&quot;,</pre><pre>&quot;atomKeymap.promptV3Features&quot;: true,</pre><pre>&quot;editor.multiCursorModifier&quot;: &quot;ctrlCmd&quot;,</pre><pre>&quot;editor.formatOnPaste&quot;: true,</pre><pre>&quot;editor.tabSize&quot;: 2,</pre><pre>&quot;editor.rulers&quot;: [80],</pre><pre>&quot;csscomb.preset&quot;: &quot;/path/to/csscomb.json&quot;,</pre><pre>&quot;editor.minimap.enabled&quot;: false,</pre><pre>&quot;ruby.lint&quot;: {</pre><pre>&quot;rubocop&quot;: {</pre><pre>&quot;lint&quot;: true,</pre><pre>&quot;rails&quot;: true</pre><pre>}</pre><pre>},</pre><pre>&quot;workbench.activityBar.visible&quot;: true,</pre><pre>&quot;telemetry.enableCrashReporter&quot;: false,</pre><pre>&quot;files.trimTrailingWhitespace&quot;: true,</pre><pre>&quot;search.exclude&quot;: {</pre><pre>&quot;**/.git&quot;: true,</pre><pre>&quot;**/node_modules&quot;: true,</pre><pre>&quot;**/bower_components&quot;: true,</pre><pre>&quot;**/tmp&quot;: true,</pre><pre>&quot;**/coverage&quot;: true,</pre><pre>&quot;**/log&quot;: true,</pre><pre>&quot;**/public/uploads&quot;: true</pre><pre>},</pre><pre>&quot;files.exclude&quot;: {</pre><pre>&quot;**/.git&quot;: true,</pre><pre>&quot;**/.svn&quot;: true,</pre><pre>&quot;**/.hg&quot;: true,</pre><pre>&quot;**/CVS&quot;: true,</pre><pre>&quot;**/.DS_Store&quot;: true,</pre><pre>&quot;**/log&quot;: true</pre><pre>}</pre><pre>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5S22hdnaeQEAEi1eJptY5g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/s7nlaF3kefg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Closing thoughts</h3><p>I’ve been using this set up for just about a week and I’m continually tweaking it to be exactly what I want it to be. I hope this helps you in getting started with Visual Code Studio and Ruby on Rails.</p><p>Let me know what you think by commenting or tweet me, <a href="https://twitter.com/PaulWritesCode">@PaulWritesCode</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc5681a2c098" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>