<?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: rubalk</title>
    <description>The latest articles on DEV Community by rubalk (@rubalk).</description>
    <link>https://dev.to/rubalk</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%2F719096%2Fa64a725c-8928-42b3-879e-64bca066f69c.png</url>
      <title>DEV Community: rubalk</title>
      <link>https://dev.to/rubalk</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rubalk"/>
    <language>en</language>
    <item>
      <title>Are you an awesome developer???</title>
      <dc:creator>rubalk</dc:creator>
      <pubDate>Tue, 26 Oct 2021 13:47:37 +0000</pubDate>
      <link>https://dev.to/rubalk/are-you-an-awesome-developer-4f1m</link>
      <guid>https://dev.to/rubalk/are-you-an-awesome-developer-4f1m</guid>
      <description>&lt;p&gt;According to Evans Data Corporation Data's Global Developer Population and Demographic Study, there are 26.9 million software developers worldwide, each working on different platforms and programming languages. Every other developer has a different way of writing their code, but one thing that connects us all is our &lt;strong&gt;Witty and Sagacious Brains.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In this article, we will go through the some of the daily interactive areas of a developer and situations that a developer must have encountered at least once in their entire professional journey.&lt;br&gt;
So, go through each of the questions below and try evaluating yourself against them. The answer to each of the questions are binary, either &lt;em&gt;yes or no&lt;/em&gt;, &lt;em&gt;true or false&lt;/em&gt;, &lt;em&gt;0 or 1&lt;/em&gt; or whatever you say :)&lt;br&gt;
Follow your instincts, whatever comes first in your mind while reading the questions is the answer to the question.&lt;/p&gt;

&lt;p&gt;At the end of the article, you will have an answer to how awesome of a developer you are.&lt;/p&gt;

&lt;p&gt;Be honest to yourself and don't rush for the results....&lt;/p&gt;

&lt;p&gt;Here you go!!!&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Can you solve each of the following basic logical problems without searching online and taking help?&lt;br&gt;
a. Evaluate if the given number is a Palindrome Number or not.&lt;br&gt;
b. Evaluate if a number is Prime numbers or not.&lt;br&gt;
c. List numbers in Fibonacci series in a given range.&lt;br&gt;
d. Print a pattern with * in the form of a triangle.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;There is Project A that you worked on previously and now you are working on a new one Project B. A feature is supposed to be developed in Project B which is exactly similar to a feature in Project A. You know the exact solution for the feature but the solution you derived was not an ideal solution. It had few drawbacks and loopholes, and you are aware of them, but it works like charm and chances of getting user getting into those issues is very rare. Will you change the design and derive a better solution?&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Have you tried deriving your own logic for the following generic problems?&lt;br&gt;
a. Palindrome String&lt;br&gt;
b. Counting occurrence of a particular character in a given string&lt;br&gt;
c. Removing duplicates from array&lt;br&gt;
d. Sorting an array&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Every developer must have solved some of the problem statements several times for different purposes in their entire journey. This may be for different project or while learning a new language or just for the sake of practice. For example, calculating the largest number in an array. So, do you derive a different logic every time, a more optimized and newer solution?&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;You don't get agitated when you get a bug in production ready feature?&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;While reading any problem statement do you tend to derive the solution in your mind? As you are moving ahead and reading the problem statement the solution is being constructed in your mind and at the end when you are finish reading you have a ready solution in your mind on which you can start working immediately. Did this ever happen to you?&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Do you try to minimize the iterations in your loops by breaking them conditionally? Does saving a single iteration in the loop makes you satisfied and happy?&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That's all folks!!!&lt;/p&gt;

&lt;p&gt;I know, the questions were not very complicated, but they must have opened abundant windows of questions for you.&lt;/p&gt;

&lt;p&gt;So, here are the results...&lt;/p&gt;

&lt;p&gt;If your answer to each of the question is a &lt;strong&gt;truthy&lt;/strong&gt;&lt;em&gt;(yes, true, 1)&lt;/em&gt; - &lt;br&gt;
Congratulations!!! You are an Awesome Developer!!! Keep up the good work!!! Inspire and guide others to be as awesome as you are.&lt;/p&gt;

&lt;p&gt;If all your answers don't result in truthy then don't get disheartened. There is still a long way to go. Try identifying the opportunities to grow and whenever you find yourself in any of the situations mentioned above, always go for a truthy :)&lt;/p&gt;

&lt;p&gt;Honestly, there is no scale to measure an awesome developer, it totally depends on how wisely you take decisions while developing. The situations mentioned above are some of the common situations we face on daily basis. There is just a thin line of choosing a healthy and optimized solution over a workaround solution. You already know the answers to each of the question, but still, we don't abide by that. Choosing an ideal solution will always move you one step closer to be an awesome developer and in no time, you will be an &lt;br&gt;
&lt;strong&gt;AWESOME DEVELOPER&lt;/strong&gt;&lt;br&gt;
or the better I say &lt;br&gt;
&lt;strong&gt;LEGEND&lt;/strong&gt;  &lt;em&gt;wait for it&lt;/em&gt;  &lt;strong&gt;DARY DEVELOPER&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;Do share in the comment section below if you are an Awesome Developer.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>programming</category>
      <category>career</category>
      <category>performance</category>
    </item>
  </channel>
</rss>
