<?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: narender2031</title>
    <description>The latest articles on DEV Community by narender2031 (@narender2031).</description>
    <link>https://dev.to/narender2031</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%2F208377%2Fde05dd14-d0c8-458f-ac09-50192757d4b5.png</url>
      <title>DEV Community: narender2031</title>
      <link>https://dev.to/narender2031</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/narender2031"/>
    <language>en</language>
    <item>
      <title>OS.Ninja</title>
      <dc:creator>narender2031</dc:creator>
      <pubDate>Mon, 19 Jan 2026 10:29:29 +0000</pubDate>
      <link>https://dev.to/narender2031/osninja-1a3b</link>
      <guid>https://dev.to/narender2031/osninja-1a3b</guid>
      <description>&lt;p&gt;For years I’ve relied on open source to learn, ship, and grow—but I’ve also felt how hard it is to truly enter a large codebase. Great projects exist, yet onboarding into them is still tribal knowledge and scattered docs.&lt;/p&gt;

&lt;p&gt;We built this to change that. The idea is simple: let AI read a repo like an experienced teammate and generate living, evolving learning paths—so contributors can move from “lost in files” to “first meaningful PR” much faster.&lt;/p&gt;

&lt;p&gt;This is just the beginning of how knowledge and code can work together. If you believe open source should be easier to learn from, give us a look (and a vote 🙏):&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.producthunt.com/products/os-ninja" rel="noopener noreferrer"&gt;https://www.producthunt.com/products/os-ninja&lt;/a&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>ai</category>
      <category>productivity</category>
      <category>opensource</category>
    </item>
    <item>
      <title>How to use sockets in react-native [No Expo]</title>
      <dc:creator>narender2031</dc:creator>
      <pubDate>Sun, 05 May 2024 06:42:01 +0000</pubDate>
      <link>https://dev.to/narender2031/how-to-use-sockets-in-react-native-no-expo-335a</link>
      <guid>https://dev.to/narender2031/how-to-use-sockets-in-react-native-no-expo-335a</guid>
      <description>&lt;p&gt;I am building an Application that need to use the sockets, i have gone through multiple docs and come up with the following packages. &lt;/p&gt;

&lt;p&gt;Can we use the following packages?&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;yarn add socket.io-client
yarn add @react-native-community/socket.io
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Please suggest me something that i can use &lt;/p&gt;

</description>
      <category>reactnative</category>
    </item>
    <item>
      <title>Hoisting in JavaScript</title>
      <dc:creator>narender2031</dc:creator>
      <pubDate>Mon, 12 Jul 2021 17:08:52 +0000</pubDate>
      <link>https://dev.to/narender2031/hoisting-in-javascript-48hi</link>
      <guid>https://dev.to/narender2031/hoisting-in-javascript-48hi</guid>
      <description>&lt;p&gt;When a JavaScript function executes it creates a global execution context. There are two-phase in the global execution context. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Creation&lt;/li&gt;
&lt;li&gt;Code execution &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In the Creation phase, javaScript allocates the memory to the variables and functions. For the variables, it allocates the placeholder value called &lt;strong&gt;undefined&lt;/strong&gt;. In the case of the function, it saves the function to the memory.&lt;/p&gt;

&lt;p&gt;So When you called the function before the define the function it works. But in the case of the Variables, it returns the undefined. &lt;/p&gt;

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