<?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: SaikatCodes</title>
    <description>The latest articles on DEV Community by SaikatCodes (@saikatcodes).</description>
    <link>https://dev.to/saikatcodes</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%2F4182580%2Fe6ed6741-0b64-447c-a13f-dcde265f54b6.png</url>
      <title>DEV Community: SaikatCodes</title>
      <link>https://dev.to/saikatcodes</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/saikatcodes"/>
    <language>en</language>
    <item>
      <title>How a Python Practice Question Became My First GitHub Project</title>
      <dc:creator>SaikatCodes</dc:creator>
      <pubDate>Tue, 13 Oct 2026 15:56:07 +0000</pubDate>
      <link>https://dev.to/saikatcodes/how-a-python-practice-question-became-my-first-github-project-5gp4</link>
      <guid>https://dev.to/saikatcodes/how-a-python-practice-question-became-my-first-github-project-5gp4</guid>
      <description>&lt;p&gt;What started as a Python problem-solving exercise gradually became my first publicly documented software project: Transaction Auditor.&lt;/p&gt;

&lt;p&gt;I was practicing Python functions, loops, lists, sets, and file handling when I began working on a problem involving financial transaction records.&lt;/p&gt;

&lt;p&gt;Initially, the goal was simple: read transaction data and calculate useful statistics.&lt;/p&gt;

&lt;p&gt;But as I developed the solution, I discovered that building a reliable program required much more than getting the calculations right.&lt;/p&gt;

&lt;p&gt;**&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;**&lt;/p&gt;

&lt;p&gt;Transaction Auditor is a file-based Python program that reads transaction records, validates them, performs financial calculations, and generates an audit report.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Its features include:&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Detecting duplicate transaction IDs&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Rejecting transactions with non-positive amounts&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Calculating successful and failed transaction statistics&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Generating customer-wise financial summaries&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Identifying the highest successful transaction&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Finding the customer with the highest successful transaction total&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Saving the results in a text report&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;**&lt;/p&gt;

&lt;h2&gt;
  
  
  The Biggest Challenge: Duplicate Transactions
&lt;/h2&gt;

&lt;p&gt;**&lt;/p&gt;

&lt;p&gt;One of the most interesting challenges was handling repeated transaction IDs.&lt;/p&gt;

&lt;p&gt;My initial approach used nested loops to compare transactions. It worked for several test cases, but testing multiple records with the same ID revealed a problem: a rejected transaction could appear more than once in the duplicate report.&lt;/p&gt;

&lt;p&gt;This taught me an important lesson:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Detecting matching pairs isn't always the same as identifying unique rejected transaction occurrences.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Testing edge cases helped me understand why the distinction matters.&lt;/p&gt;

&lt;p&gt;**&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Learned
&lt;/h2&gt;

&lt;p&gt;**&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;This project strengthened my understanding of:&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Python functions and program structure&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Lists and sets&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Nested loops and conditional logic&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;File reading and writing&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Data validation&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Debugging and edge-case testing&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Connecting multiple functions into one working program&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I also learned how to organize a project, document it using Markdown, and publish it on GitHub.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;What Comes Next?&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Transaction Auditor is currently a learning and portfolio project, not a production-ready financial system.&lt;/p&gt;

&lt;p&gt;Future improvements could include CSV support, stronger input validation, interactive transaction entry, and automated transaction imports.&lt;/p&gt;

&lt;p&gt;For now, I'm focusing on strengthening my Python fundamentals and building more practical projects.&lt;/p&gt;

&lt;p&gt;Explore the Project&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GitHub Repository&lt;/strong&gt;: &lt;a href="https://github.com/Saikat703/Transaction-Auditor" rel="noopener noreferrer"&gt;Transaction Auditor&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'd appreciate constructive feedback, especially on improving the program's structure, reliability, and testing.&lt;/p&gt;

&lt;p&gt;Thanks for reading!&lt;/p&gt;

</description>
      <category>python</category>
      <category>beginners</category>
      <category>showdev</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
