<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rick</title>
    <description>The latest articles on DEV Community by Rick (@ricknoln).</description>
    <link>https://dev.to/ricknoln</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F371064%2F0fe47dad-ac8a-4588-ac73-ee354f720586.jpg</url>
      <title>DEV Community: Rick</title>
      <link>https://dev.to/ricknoln</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ricknoln"/>
    <language>en</language>
    <item>
      <title>Rob Pike interview: “Go has indeed become the language of cloud infrastructure“</title>
      <dc:creator>Rick</dc:creator>
      <pubDate>Wed, 06 May 2020 09:40:57 +0000</pubDate>
      <link>https://dev.to/ricknoln/rob-pike-interview-go-has-indeed-become-the-language-of-cloud-infrastructure-3ek1</link>
      <guid>https://dev.to/ricknoln/rob-pike-interview-go-has-indeed-become-the-language-of-cloud-infrastructure-3ek1</guid>
      <description>&lt;p&gt;We spoke to Rob Pike, the co-author of the Go programming language, about a career spanning four decades, the evolution of Go over the last ten years, and into the future.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://evrone.com/rob-pike-interview"&gt;Read the interview&lt;/a&gt;&lt;/p&gt;

</description>
      <category>go</category>
      <category>backend</category>
    </item>
    <item>
      <title>Introducing postcss-px-to-viewport: open-source software to create scalable interfaces on any display</title>
      <dc:creator>Rick</dc:creator>
      <pubDate>Wed, 29 Apr 2020 08:30:27 +0000</pubDate>
      <link>https://dev.to/ricknoln/introducing-postcss-px-to-viewport-open-source-software-to-create-scalable-interfaces-on-any-display-4o15</link>
      <guid>https://dev.to/ricknoln/introducing-postcss-px-to-viewport-open-source-software-to-create-scalable-interfaces-on-any-display-4o15</guid>
      <description>&lt;p&gt;Most mobile and cross-platform web developers have encountered the problem at some point: you need your web app to scale neatly to the device screen size, regardless of which of the many thousands of devices there are out there, but your units only have one design layout width, mainly mobile. &lt;/p&gt;

&lt;p&gt;Grappling with this problem in one of our projects our leading frontend developer Dmitriy Karpunin came up with the idea of using a post-processor to convert CSS values from one set of units to another, and that’s how postcss-px-to-viewport, a plug-in for PostCSS that converts px values to viewport units (vw, vh, etc.), was born.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://evrone.com/postcss-px-viewport"&gt;Learn more about a new tool for creating scalable interfaces on any display&lt;/a&gt;&lt;/p&gt;

</description>
      <category>css</category>
      <category>frontend</category>
      <category>postcss</category>
    </item>
    <item>
      <title>Dotenv-linter: looking after the environment for you</title>
      <dc:creator>Rick</dc:creator>
      <pubDate>Tue, 21 Apr 2020 13:43:47 +0000</pubDate>
      <link>https://dev.to/ricknoln/dotenv-linter-looking-after-the-environment-for-you-5gk2</link>
      <guid>https://dev.to/ricknoln/dotenv-linter-looking-after-the-environment-for-you-5gk2</guid>
      <description>&lt;p&gt;When developing applications, we always try to stick to the Manifesto of Twelve Factors. This approach helps you to avoid a number of the problems associated with the ongoing support of applications throughout their lifecycle. &lt;/p&gt;

&lt;p&gt;One of the principles of the manifesto is that all settings should be stored in environment variables, allowing you to alter them for different environments (development, automated testing, staging/QA, production) without changing the code.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://evrone.com/dotenv-linter"&gt;Learn more about a new tool to lint .env files&lt;/a&gt;&lt;/p&gt;

</description>
      <category>linter</category>
      <category>rust</category>
      <category>env</category>
      <category>dotenv</category>
    </item>
  </channel>
</rss>
