<?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: NickeaBennett</title>
    <description>The latest articles on DEV Community by NickeaBennett (@nickeabennett).</description>
    <link>https://dev.to/nickeabennett</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F823217%2F9bf70bf5-ef41-4e01-b6db-185ab7071b35.png</url>
      <title>DEV Community: NickeaBennett</title>
      <link>https://dev.to/nickeabennett</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nickeabennett"/>
    <language>en</language>
    <item>
      <title>What is Active Record</title>
      <dc:creator>NickeaBennett</dc:creator>
      <pubDate>Sat, 13 Aug 2022 14:06:00 +0000</pubDate>
      <link>https://dev.to/nickeabennett/what-is-active-record-2fl4</link>
      <guid>https://dev.to/nickeabennett/what-is-active-record-2fl4</guid>
      <description>&lt;p&gt;To non-programmers this might sound like a recording label. However, in computer programming what is Active record? active record is a ruby gem that handles the database stuff without worrying to much about writing SQL.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Object/Relational Mapping (ORM)&lt;/strong&gt;&lt;br&gt;
ORM stands for Object-Relational-Mapping. Essentially, Active Record takes data stored in a relational database, which needs to be modified or retrieved by writing SQL statements. Developers can interact with that data using Ruby object.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Example without Active Record&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;class User
  attr_accessor :name

  @@all = []

  def initialize(name)
      @name = name
      @@all &amp;lt;&amp;lt; self
  end

  def self.all
      @@all
  end
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Example with Active Record&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;class User &amp;lt; ActiveRecord::Base

end
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



</description>
      <category>ruby</category>
    </item>
    <item>
      <title>Using NPM VS Yarn in React</title>
      <dc:creator>NickeaBennett</dc:creator>
      <pubDate>Mon, 04 Jul 2022 16:00:45 +0000</pubDate>
      <link>https://dev.to/nickeabennett/using-npm-vs-yarn-in-react-2o1b</link>
      <guid>https://dev.to/nickeabennett/using-npm-vs-yarn-in-react-2o1b</guid>
      <description>&lt;p&gt;While most junior Software Engineers tend to gravitate to NPM (Node Package manager) like myself. Most experienced React Engineers gravitate to yarn. Yea! boring right?&lt;/p&gt;

&lt;p&gt;Both have similarities and differences but at the end of the day both get the job done. &lt;/p&gt;

&lt;p&gt;NPM tends to be on the slow side of things when installing dependencies. However, yarn seems to be a bit slower when starting an application.&lt;/p&gt;

&lt;p&gt;The reason behind the slowness of yarn is due to it's validation checks. In all honesty, I really don't mind. I feel a bit safer and confident using yarn over NPM now that I have given it a shot. &lt;/p&gt;

&lt;p&gt;Lets briefly compare yarn and npm.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Command                      npm    yarn
Install dependencies:   npm install yarn
Install package: npm install [package]  yarn add [package]
Update:             npm update  yarn upgrade

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To learn more about yarn you can visit the official site here: &lt;a href="https://classic.yarnpkg.com/en/docs/getting-started"&gt;https://classic.yarnpkg.com/en/docs/getting-started&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can also visit Digital Ocean's cheat sheet here: &lt;a href="https://www.digitalocean.com/community/tutorials/nodejs-npm-yarn-cheatsheet"&gt;https://www.digitalocean.com/community/tutorials/nodejs-npm-yarn-cheatsheet&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I hope whichever path you choose will lead you to a speedy development process....minus the bugs. &lt;/p&gt;

</description>
      <category>javascript</category>
      <category>react</category>
    </item>
  </channel>
</rss>
