<?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: Arpit Mathur.</title>
    <description>The latest articles on DEV Community by Arpit Mathur. (@arpit_m).</description>
    <link>https://dev.to/arpit_m</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%2F452017%2F2d85ba02-13c8-4597-aacd-85d7052b583d.jpg</url>
      <title>DEV Community: Arpit Mathur.</title>
      <link>https://dev.to/arpit_m</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/arpit_m"/>
    <language>en</language>
    <item>
      <title>Showcase Projects vs Passion Projects</title>
      <dc:creator>Arpit Mathur.</dc:creator>
      <pubDate>Thu, 14 Jan 2021 22:10:02 +0000</pubDate>
      <link>https://dev.to/arpit_m/showcase-projects-vs-passion-projects-2cnd</link>
      <guid>https://dev.to/arpit_m/showcase-projects-vs-passion-projects-2cnd</guid>
      <description>&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Ffr1sg1h92puti9kkpf60.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Ffr1sg1h92puti9kkpf60.jpg" alt="Work desk"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;One of the most common pieces of advice you'll get as a newbie developer is to work on some projects to master your skills when looking for a job. The conventional wisdom is that 3 is a good number to show on your resume, which I generally agree with (we'll talk about which three the next time)&lt;/p&gt;

&lt;p&gt;That said, people confuse 2 types of projects: &lt;strong&gt;showcase projects&lt;/strong&gt; and &lt;strong&gt;passion projects&lt;/strong&gt;. Let's see how they differ:&lt;/p&gt;

&lt;h3&gt;
  
  
  Showcase projects
&lt;/h3&gt;

&lt;p&gt;Showcase projects are projects that you want to show a recruiter or an engineering lead. These projects should be familiar products (a bug organizer, a blog, etc). Showcase projects should not be around an idea unfamiliar to the reviewer, so the conversation you have around it is about the code and your technical skills, not the merit of the idea. It's also ok to adopt the design from a well-known project out there instead of trying to come up with a design yourself, especially if you aren't a designer.&lt;/p&gt;

&lt;h3&gt;
  
  
  Passion Projects
&lt;/h3&gt;

&lt;p&gt;Passion projects are projects you are personally very excited about even though their implementation may not be very complicated or the user interaction may be very unusual. A simple listing of local keto restaurants may be a great passion project but doesn't highlight your technical skills. &lt;/p&gt;

&lt;h2&gt;
  
  
  Mixing it up
&lt;/h2&gt;

&lt;p&gt;This division may feel a bit arbitrary, and if your passion project has technical merit, then definitely show it. But remember your primary goal in a technical interview is to discuss the technical underpinnings of your project. You will get more credit for a complex system implemented well than a novel idea with a simple execution 🙂 &lt;/p&gt;

&lt;p&gt;============================&lt;br&gt;
🙏 Thanks for reading this post. &lt;/p&gt;

&lt;p&gt;Btw, If you are interested in learning Javascript and are bored with books and long videos, try out my latest project:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://devbots.ai/jax.html" rel="noopener noreferrer"&gt;🤖 Jax: Your JavaScript chatbot coach&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://devbots.ai/jax.html" rel="noopener noreferrer"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdevbots.ai%2Fimg%2FBadge.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;=============================&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>ruby</category>
      <category>resume</category>
      <category>career</category>
    </item>
    <item>
      <title>Communicating when working remote</title>
      <dc:creator>Arpit Mathur.</dc:creator>
      <pubDate>Tue, 12 Jan 2021 18:27:25 +0000</pubDate>
      <link>https://dev.to/arpit_m/communicating-when-working-remote-4671</link>
      <guid>https://dev.to/arpit_m/communicating-when-working-remote-4671</guid>
      <description>&lt;p&gt;I was recently rewatching one of my favorite talks, &lt;a href="https://www.youtube.com/watch?v=P1T-1FqUBVY"&gt;Jonathan Rosenberg's Rules to Success&lt;/a&gt; and it just struck me how many of his points are even more important today than ever, especially on communication, which is really important when working from home. I shared my notes on that with my team at work but figured it would also be useful to others here.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Overcommunicate always all the time. You cant communcate enough&lt;/li&gt;
&lt;li&gt;Openly share everything with your collegues. Trust your people and give them this info. Trust breeds loyalty.&lt;/li&gt;
&lt;li&gt;Repetition does not spoil the prayer&lt;/li&gt;
&lt;li&gt;Each word matters. Be crisp and direct and choose each word wisely&lt;/li&gt;
&lt;li&gt;Great leaders are great teachers and great teachers are great storytellers. Narrative matters.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;On Talking:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;As leaders, you learn more by listening than talking. Listening makes you humble and smart. When you listen you learn how things work, when you talk, you echo how you think things work.&lt;/li&gt;
&lt;li&gt;If you must talk, ask questions. People learn more about you from your questions&lt;/li&gt;
&lt;li&gt;If you actually know the answer in a business situation, talk, but back up with data.&lt;/li&gt;
&lt;li&gt;Try to respond instantly. If you don't respond instantly, everything stalls.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Thoughts are always welcome 😀&lt;/p&gt;

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