<?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: shivain gupta</title>
    <description>The latest articles on DEV Community by shivain gupta (@shivain_gupta_e9052a6a259).</description>
    <link>https://dev.to/shivain_gupta_e9052a6a259</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%2F4162125%2F49d3c36f-fbd4-4cab-a529-9f56e81f0c18.jpg</url>
      <title>DEV Community: shivain gupta</title>
      <link>https://dev.to/shivain_gupta_e9052a6a259</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shivain_gupta_e9052a6a259"/>
    <language>en</language>
    <item>
      <title>My Hacktoberfest 2026 Plan: How I'm Picking Issues Without Burning Out</title>
      <dc:creator>shivain gupta</dc:creator>
      <pubDate>Sun, 11 Oct 2026 19:31:14 +0000</pubDate>
      <link>https://dev.to/shivain_gupta_e9052a6a259/my-hacktoberfest-2026-plan-how-im-picking-issues-without-burning-out-53ki</link>
      <guid>https://dev.to/shivain_gupta_e9052a6a259/my-hacktoberfest-2026-plan-how-im-picking-issues-without-burning-out-53ki</guid>
      <description>&lt;p&gt;Hacktoberfest is here again, and this year I'm trying to be more intentional instead of grabbing the first "good first issue" I see.&lt;/p&gt;

&lt;h2&gt;
  
  
  My rules for picking issues
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Pick projects I actually use.&lt;/strong&gt; I understand the context faster and care more about the result.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check maintainer activity.&lt;/strong&gt; If the last merged PR is months old, I skip it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Start small.&lt;/strong&gt; Docs fixes, tests, and small bug fixes build trust before bigger changes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Comment before coding.&lt;/strong&gt; A quick "Can I take this?" saves everyone from duplicate work.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  My workflow
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Fork, then clone&lt;/li&gt;
&lt;li&gt;Create a branch named after the issue&lt;/li&gt;
&lt;li&gt;Make the smallest change that solves the problem&lt;/li&gt;
&lt;li&gt;Run the tests locally&lt;/li&gt;
&lt;li&gt;Write a clear PR description: what changed, why, and how to verify it&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I'm hoping to learn
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Reading unfamiliar codebases faster&lt;/li&gt;
&lt;li&gt;Writing better commit messages and PR descriptions&lt;/li&gt;
&lt;li&gt;Handling review feedback gracefully&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Tips if you're just starting
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Don't wait until you feel "ready." Nobody does.&lt;/li&gt;
&lt;li&gt;A merged typo fix still counts as a real contribution.&lt;/li&gt;
&lt;li&gt;Be patient with maintainers. Most are volunteers.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What's your strategy for finding issues this month? Drop your favorite repos or tips in the comments, and I'll check them out.&lt;/p&gt;

&lt;p&gt;Happy hacking! 🎃&lt;/p&gt;

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