<?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: Priyadharshini</title>
    <description>The latest articles on DEV Community by Priyadharshini (@dharshini_0101).</description>
    <link>https://dev.to/dharshini_0101</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%2F3688449%2F403e6d4a-f583-4064-81b3-ea5093c1f5eb.png</url>
      <title>DEV Community: Priyadharshini</title>
      <link>https://dev.to/dharshini_0101</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dharshini_0101"/>
    <language>en</language>
    <item>
      <title>Why Contributing to Open Source Can Help Your Career</title>
      <dc:creator>Priyadharshini</dc:creator>
      <pubDate>Sat, 31 Jan 2026 09:56:52 +0000</pubDate>
      <link>https://dev.to/dharshini_0101/why-contributing-to-open-source-can-help-your-career-2m56</link>
      <guid>https://dev.to/dharshini_0101/why-contributing-to-open-source-can-help-your-career-2m56</guid>
      <description>&lt;p&gt;Open source isn’t just about coding—it’s about community, learning, and growth.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Connect with developers worldwide – Exchange ideas and grow your network.&lt;/li&gt;
&lt;li&gt;Explore diverse codebases – Gain hands-on experience with real-world projects.&lt;/li&gt;
&lt;li&gt;Improve coding quality &amp;amp; strategy – Learn to approach problems efficiently.&lt;/li&gt;
&lt;li&gt;Boost communication skills – Collaborate and discuss solutions effectively.&lt;/li&gt;
&lt;li&gt;Small wins = confidence boost – Every merged PR is progress.&lt;/li&gt;
&lt;li&gt;Portfolio &amp;amp; profile enhancement – Showcasing contributions strengthens your professional profile.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;How to get started:&lt;br&gt;
1) Pick a domain you’re comfortable with.&lt;br&gt;
2) Learn GitHub workflow – how to work with repos, branches, PRs, and issues.&lt;br&gt;
3) Find beginner-friendly issues: goodfirstissues.com, goodfirstissue.dev&lt;br&gt;
4) Start small – fix minor bugs or documentation, comment on issues, then raise PRs.&lt;br&gt;
5) Engage with the community and follow contributing guidelines.&lt;/p&gt;

&lt;p&gt;Each contribution helps you grow, learn, and make an impact in real-world projects&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How Changing My Thinking Transformed My Interview Problem‑Solving</title>
      <dc:creator>Priyadharshini</dc:creator>
      <pubDate>Wed, 28 Jan 2026 18:25:45 +0000</pubDate>
      <link>https://dev.to/dharshini_0101/how-thinking-changed-my-interview-problem-solving-1ign</link>
      <guid>https://dev.to/dharshini_0101/how-thinking-changed-my-interview-problem-solving-1ign</guid>
      <description>&lt;p&gt;For the longest time in coding interviews, my first instinct was:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;“I’ve already seen this problem before. How did I solve it?”&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;During prep, we solve hundreds of problems mostly by recognizing patterns and applying known solutions. But in real interviews, it’s unrealistic to remember every exact solution. What I eventually realized was this reflex was actually hurting me.&lt;/p&gt;

&lt;p&gt;The questions looked familiar, but the constraints were different each time.&lt;/p&gt;

&lt;p&gt;And when my first coding attempt didn’t work? Fixing or rewriting it became messy and slow.&lt;/p&gt;

&lt;p&gt;So I tried something different: I slowed down.&lt;/p&gt;

&lt;p&gt;Here’s what changed:&lt;/p&gt;

&lt;p&gt;I stopped trying to recall exact past solutions&lt;/p&gt;

&lt;p&gt;I focused on why a pattern works, not just how to apply it&lt;/p&gt;

&lt;p&gt;I read the problem once then again until constraints were crystal clear&lt;/p&gt;

&lt;p&gt;I sketched a rough solution on paper before writing a single line of code&lt;/p&gt;

&lt;p&gt;At first, sure it felt slower.&lt;/p&gt;

&lt;p&gt;But clarity came first.&lt;br&gt;
And with clarity came speed, confidence, and cleaner code.&lt;/p&gt;

&lt;p&gt;Treat every problem as new. Don’t react reflexively approach it with a clear strategy and the right use of pattern. That’s real problem‑solving, not pattern matching. &lt;/p&gt;

&lt;p&gt;This way of thinking isn’t just for coding interviews it can help in any competition or challenge, wherever clarity and strategy matter.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Happy new year everyone😃🥳</title>
      <dc:creator>Priyadharshini</dc:creator>
      <pubDate>Thu, 01 Jan 2026 12:01:26 +0000</pubDate>
      <link>https://dev.to/dharshini_0101/happy-new-year-everyone-438p</link>
      <guid>https://dev.to/dharshini_0101/happy-new-year-everyone-438p</guid>
      <description></description>
    </item>
  </channel>
</rss>
