<?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: Christian Otieno</title>
    <description>The latest articles on DEV Community by Christian Otieno (@christianotieno).</description>
    <link>https://dev.to/christianotieno</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%2F260820%2Ffb7f4ddb-beaf-4896-b59b-afbebed2d42e.jpeg</url>
      <title>DEV Community: Christian Otieno</title>
      <link>https://dev.to/christianotieno</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/christianotieno"/>
    <language>en</language>
    <item>
      <title>Hoisting</title>
      <dc:creator>Christian Otieno</dc:creator>
      <pubDate>Thu, 19 Mar 2020 20:58:21 +0000</pubDate>
      <link>https://dev.to/christianotieno/hoisting-d7g</link>
      <guid>https://dev.to/christianotieno/hoisting-d7g</guid>
      <description>&lt;p&gt;One of the advantages of JavaScript putting function declarations into memory before it executes any code segment is that it allows you to use a function before you declare it in your code.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>hoisting</category>
    </item>
    <item>
      <title>Double Pipe Equals</title>
      <dc:creator>Christian Otieno</dc:creator>
      <pubDate>Fri, 28 Feb 2020 22:07:24 +0000</pubDate>
      <link>https://dev.to/christianotieno/double-pipe-equals-2mk3</link>
      <guid>https://dev.to/christianotieno/double-pipe-equals-2mk3</guid>
      <description>&lt;p&gt;If the left-hand side of the comparison is true, there's no need to check the right-hand side. Well, the principle works well in my programming world. I am not so sure of its practicality on the real world though.&lt;/p&gt;

</description>
      <category>doublepipeequals</category>
      <category>operators</category>
    </item>
    <item>
      <title>DRY</title>
      <dc:creator>Christian Otieno</dc:creator>
      <pubDate>Fri, 29 Nov 2019 16:12:59 +0000</pubDate>
      <link>https://dev.to/christianotieno/dry-c5o</link>
      <guid>https://dev.to/christianotieno/dry-c5o</guid>
      <description>&lt;p&gt;Don't Repeat Yourself: DRY is a principle of software development which states that "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system." By not writing the same information over and over again, our code is more maintainable, more extensible, and less buggy.&lt;/p&gt;

</description>
      <category>dontrepeatyourself</category>
    </item>
    <item>
      <title>Behaviour Driven Development</title>
      <dc:creator>Christian Otieno</dc:creator>
      <pubDate>Thu, 28 Nov 2019 21:01:23 +0000</pubDate>
      <link>https://dev.to/christianotieno/behaviour-driven-development-2mm9</link>
      <guid>https://dev.to/christianotieno/behaviour-driven-development-2mm9</guid>
      <description>&lt;p&gt;Behaviour Driven Development (BDD) is similar to Test Driven Development but focuses on writing specifications for a project in the form of descriptive stories that can be the basis for automated acceptance tests.&lt;/p&gt;

</description>
      <category>tdd</category>
      <category>rails</category>
      <category>opensource</category>
      <category>todayilearned</category>
    </item>
    <item>
      <title>Rails.</title>
      <dc:creator>Christian Otieno</dc:creator>
      <pubDate>Thu, 28 Nov 2019 17:42:51 +0000</pubDate>
      <link>https://dev.to/christianotieno/rails-2lf2</link>
      <guid>https://dev.to/christianotieno/rails-2lf2</guid>
      <description>&lt;p&gt;Rails uses, as you’ll often hear, “convention over configuration”. That means that the creators of Rails have made a lot of decisions for you about how things should be structured and how the code should run. You can change them, but it’s best if you just go with the flow and work within their rules (especially as a noob).&lt;/p&gt;

</description>
      <category>ruby</category>
      <category>rails</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
