<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mokshita V P on Medium]]></title>
        <description><![CDATA[Stories by Mokshita V P on Medium]]></description>
        <link>https://medium.com/@mokshitavp?source=rss-00ea420bef08------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HNzEtw24aeKtLwln</url>
            <title>Stories by Mokshita V P on Medium</title>
            <link>https://medium.com/@mokshitavp?source=rss-00ea420bef08------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:51:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mokshitavp/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[How Bats Gave Me a Project Idea (and Why I’m Building It on Just My Laptop)]]></title>
            <link>https://medium.com/@mokshitavp/how-bats-gave-me-a-project-idea-and-why-im-building-it-on-just-my-laptop-b276f1dad18d?source=rss-00ea420bef08------2</link>
            <guid isPermaLink="false">https://medium.com/p/b276f1dad18d</guid>
            <category><![CDATA[python-web-developer]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[python-programming]]></category>
            <category><![CDATA[python3]]></category>
            <dc:creator><![CDATA[Mokshita V P]]></dc:creator>
            <pubDate>Mon, 20 Jul 2026 06:50:41 GMT</pubDate>
            <atom:updated>2026-07-20T06:50:41.740Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*owNLE_24OpX3BrAb" /><figcaption>Photo by <a href="https://unsplash.com/@fridalannerstrom?utm_source=medium&amp;utm_medium=referral">Frida Lannerström</a> on <a href="https://unsplash.com?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It started with a random late-night rabbit hole. I don’t even remember what I was originally looking up, but I ended up on a Scientific American article about how bats echolocate: [<a href="https://www.scientificamerican.com/article/how-do-bats-echolocate-an/">How Do Bats Echolocate, and How Are They Able to Fly in Total Darkness?</a>]. The piece breaks down how bats send out sound pulses and read the returning echoes to build a picture of the world around them, distance, size, even texture, all from sound bouncing back at them.</p><p>I read the whole thing twice. Something about an animal building a 3D mental map purely from timing differences in returning sound waves felt almost too clean, too elegant, to just be biology. It felt like an algorithm.</p><p>That sent me to a second article, this one from National Geographic: [<a href="https://www.nationalgeographic.com/animals/article/echolocation-is-nature-built-in-sonar-here-is-how-it-works">Echolocation Is Nature’s Built-In Sonar</a>]. It covers similar ground but goes wider, talking about dolphins and whales too, and it’s the piece that made the connection click for me: this is just sonar. Submarines do the exact same thing with hydrophones. Bats had it first by about fifty million years, but the physics is identical. Emit a pulse, listen for the echo, measure the delay, calculate the distance.</p><p>Once I saw it that way, I couldn’t unsee it. A speaker is a mouth. A microphone is an ear. Every laptop already has both.</p><h4><strong>Then I Found Out People Already Beat Me to It</strong></h4><p>Naturally my next move was to see if anyone had already tried this on consumer hardware, because if a bat can do it with a face made of skin and cartilage, surely someone has done it with a Laptop.</p><p>Turns out yes. Plenty of people.</p><p>I found the [<a href="https://github.com/Neumi/open_echo/issues">open_echo</a>] project on GitHub, an open source sonar/echo-sounder build, and started reading through the issues thread. Watching real contributors argue about signal noise, transducer choice, and calibration made the whole idea feel less like a fantasy and more like an actual weekend project with actual solvable problems.</p><p>Then I stumbled on an old blog post from 2012 by Bob Lansdorp: [<a href="https://boblansdorp.blogspot.com/2012/10/microphone-and-speaker-based-sonar.html">Microphone and Speaker Based Sonar</a>]. This one is the closest thing to a blueprint I’ve found. He’s doing exactly what I had in my head: playing a signal out of a regular speaker and picking up the reflection on a regular mic, no special hardware, just cross-correlation math doing the heavy lifting.</p><p>And then, because apparently this idea has been floating around for over a decade, I found a Hackaday writeup from 2013: [<a href="https://hackaday.com/2013/12/23/sonar-with-python-and-conference-call-hardware/">Sonar With Python and Conference Call Hardware</a>]. Someone built this using a conference speakerphone and Python, years before I ever thought about it.</p><p>At first this was a little deflating. That familiar feeling of “oh, I thought I had a cool original idea” hitting me the moment I open a search bar. But the more I read, the more I realized that’s actually the reassuring part. If multiple people independently built versions of this over more than a decade, using totally different hardware and totally different eras of tooling, the core concept is clearly solid. It’s not a fluke or a gimmick. It’s a real, repeatable technique. I wasn’t chasing something impossible, I was just late to a party that’s apparently been going for a while.</p><h4><strong>The Hardware Reality Check</strong></h4><p>Here’s where my plan hit a small wall. A lot of the builds I was reading about, including Bob Lansdorp’s and the Hackaday one, used external microphones and speakers, sometimes decent ones, sometimes purpose-built conference call hardware with better frequency response than what ships in a standard laptop.</p><p>I don’t have any of that. No external mic, no dedicated speaker rig, no transducers sitting in a drawer somewhere. What I have is the laptop I’m typing this on right now.</p><p>So instead of treating that as a blocker, I’m treating it as the actual constraint that defines the project: build the whole thing using nothing but the built-in speaker and built-in mic. No shopping list, no waiting for parts to arrive, no external gear at all. Just whatever’s already sitting inside the machine.</p><p>It changes the scope a bit. Laptop speakers and mics roll off well before the frequencies dedicated sonar hardware can hit, so the first real step isn’t distance detection at all, it’s figuring out what my specific laptop can actually emit and pick back up cleanly near the edge of human hearing. Everything else, the chirp design, the cross-correlation, the live radar-style readout, depends on getting that baseline first.</p><p>There’s something fitting about that limitation too. Bats didn’t get to special-order better ears. They worked with the biology they had and turned it into one of the most precise navigation systems in nature. I’m working with whatever’s built into a laptop, which feels like a reasonable place to start.</p><h4><strong>What’s Next</strong></h4><p>Right now I’m at the very beginning: reading, understanding the physics, and mapping out how the emit-and-listen loop actually needs to work before I touch a line of code. The plan is to document each phase as I go, starting with a hardware validation test to see what frequency range my mic and speaker can realistically handle, then moving into the actual distance detection once I know what I’m working with.</p><p>If a bat can build a working model of a cave using nothing but its own voice, I’d like to think a laptop can figure out how far away my wall is.</p><p><em>Thanks for reading! If you enjoyed this or have ideas for enhancements, let me know in the comments. If you’re interested in what I do next, make sure to follow so you don’t miss out! Drop a comment or connect with me on Medium and LinkedIn.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b276f1dad18d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reducing Decision Fatigue with Code: Inside My AI-Powered Fashion App]]></title>
            <link>https://medium.com/@mokshitavp/reducing-decision-fatigue-with-code-inside-my-ai-powered-fashion-app-f5b4496880b5?source=rss-00ea420bef08------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5b4496880b5</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Mokshita V P]]></dc:creator>
            <pubDate>Sun, 26 Apr 2026 10:12:40 GMT</pubDate>
            <atom:updated>2026-04-26T10:12:40.988Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ww0t7ojIPWKOp8EVdtN3DA.jpeg" /></figure><p>It’s been a while since I last wrote here.</p><p>For the past few months, I’ve been working on something that started with a very simple frustration: I had a full wardrobe and still spent way too long deciding what to wear.</p><p>At first, I thought I just needed better clothes. But after repeating the same cycle over and over, it became clear that wasn’t the problem.</p><p>The real issue was not knowing what I already had, what actually worked together, and what was just taking up space.</p><p>So instead of buying more clothes or reorganizing my cupboard again, I decided to build something.</p><p>What started as a small idea turned into a full-stack web app that helps you:</p><ul><li>organize your wardrobe</li><li>get outfit suggestions</li><li>evaluate clothes before buying them</li><li>and identify items that aren’t worth keeping</li></ul><p>In this article, I’ll walk through how I built it, what worked, what didn’t, and what I’d do differently.</p><h3>The Problem Most Fashion Apps Ignore</h3><p>Most fashion apps focus on helping you discover new clothes.</p><p>But that’s not where people struggle.</p><p>The real problem is decision fatigue.</p><p>Even with a good wardrobe, it’s surprisingly hard to:</p><ul><li>remember everything you own</li><li>combine items confidently</li><li>and avoid repeating the same outfits</li></ul><p>On top of that, most recommendations feel generic. They don’t learn from you, and they don’t reflect your actual wardrobe.</p><p>I wanted to build something that did the opposite:</p><ul><li>focus on what you already own</li><li>improve over time using feedback</li><li>and give suggestions that actually make sense</li></ul><h3>What the App Actually Does</h3><p>Instead of building isolated features, I focused on creating a system where everything connects.</p><p>Here’s what it does in simple terms:</p><p>You first upload a full size picture of yourself, and then a few details like height and weight.</p><p>You then upload your clothes and build a digital wardrobe.</p><p>From there, the app suggests outfits based on things like color compatibility and personal attributes. You can rate those suggestions so the system learns what works for you.</p><p>It also helps with decisions beyond outfits:</p><ul><li><strong>Shopping assistant</strong> → checks if a new item actually fits your wardrobe</li><li><strong>Discard assistant</strong> → flags items that don’t add much value</li></ul><p>The goal isn’t just recommendations, it’s better decisions.</p><h3>How I Approached Building It</h3><p>One of the best decisions I made early on was <strong>not jumping straight into AI/ML</strong>.</p><p>Instead, I started with simple, rule-based logic.</p><p>That made everything easier to:</p><ul><li>debug</li><li>improve</li><li>and explain</li></ul><p>The stack I used:</p><ul><li>React (with Vite) for the frontend</li><li>FastAPI for the backend</li><li>SQLite for development</li><li>Celery + Redis for background jobs</li><li>JWT-based authentication</li></ul><p>Nothing fancy individually, but together, it created a flexible system.</p><h3>How Recommendations Work (Without Overcomplicating It)</h3><p>Instead of black-box models, I used a weighted scoring system.</p><p>Each outfit is scored based on:</p><ul><li>how well the colors go together</li><li>how well it fits the user’s body type</li><li>how well it matches undertones</li></ul><p>Each factor contributes to a final score, which is used to rank recommendations.</p><p>This approach has a big advantage: it’s explainable.</p><p>Instead of just showing an outfit, the system can also explain <em>why</em> it works.</p><p>I used similar logic for:</p><ul><li>suggesting what to buy</li><li>suggesting what to remove</li></ul><h3>The Hard Parts No One Talks About</h3><p>This is where most of my time actually went.</p><h3>1. Image Processing Slowed Everything Down</h3><p>Analyzing images isn’t cheap.</p><p>At one point, a few users uploading images at the same time would slow down the entire system.</p><p>The fix:</p><ul><li>move heavy work to background jobs</li><li>limit how many tasks run at once</li><li>add status tracking so users aren’t stuck waiting</li></ul><h3>2. Authentication Got Complicated Fast</h3><p>JWT sounds simple, until you need real-world behavior like:</p><ul><li>logging out from one device</li><li>logging out from all devices</li><li>preventing token reuse</li></ul><p>To handle this, I had to:</p><ul><li>store refresh tokens in the database</li><li>track them using unique IDs</li><li>rotate them on every refresh</li></ul><p>This turned auth into one of the more complex parts of the system.</p><h3>3. Multi-user Systems Are Easy to Get Wrong</h3><p>If you’re not careful, users can end up accessing each other’s data.</p><p>To avoid that, I made sure:</p><ul><li>every request checks ownership</li><li>all data is strictly user-scoped</li><li>image access is protected</li></ul><p>This is one of those things that’s invisible when done right, but critical.</p><h3>4. Setup Was Becoming a Headache</h3><p>As the project grew, running it locally became harder.</p><p>So I:</p><ul><li>containerized everything using Docker</li><li>added support for GitHub Codespaces</li><li>cleaned up environment configs</li></ul><p>That made the project much easier to run and share.</p><h3>What I Learned From This</h3><p>A few things stood out after building this:</p><ul><li>Simple systems are easier to improve than complex ones</li><li>Feedback is what makes recommendations actually useful</li><li>Security should be built in early, not added later</li><li>Developer experience matters more than you think</li></ul><p>But the biggest lesson was this:</p><p>You don’t need a huge idea to build something valuable.</p><p>You just need a real problem.</p><h3>What’s Next</h3><p>There’s still a lot I want to improve:</p><ul><li>add analytics to measure how good suggestions actually are</li><li>improve the mobile experience</li><li>deploy with a proper production setup</li><li>create a public demo</li></ul><h3>Final Thoughts</h3><p>This started as a small frustration and turned into a system that actually helps solve it.</p><p>Not by adding more choices, but by making better use of what’s already there.</p><p>And honestly, that applies to more than just wardrobes.<br>here’s my github repo incase u wanna try it out yourself or maybe look at the code:</p><p><a href="https://github.com/Mokshitavp1/fashion_assistant">https://github.com/Mokshitavp1/fashion_assistant</a></p><p>let me know in the comments if u have any more questions or advices. and follow for more!!</p><p><em>This article is an adapted and expanded version of a piece originally published on FreeCodeCamp.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5b4496880b5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Built a Sudoku Solver in C as a First-Year Engineering Student]]></title>
            <link>https://medium.com/@mokshitavp/how-i-built-a-sudoku-solver-in-c-as-a-first-year-engineering-student-28a497ef79c3?source=rss-00ea420bef08------2</link>
            <guid isPermaLink="false">https://medium.com/p/28a497ef79c3</guid>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[c-programming-language]]></category>
            <category><![CDATA[c-programming]]></category>
            <category><![CDATA[first-year-students]]></category>
            <dc:creator><![CDATA[Mokshita V P]]></dc:creator>
            <pubDate>Sat, 02 Aug 2025 09:39:17 GMT</pubDate>
            <atom:updated>2025-08-02T09:39:17.861Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cWO3cqlsagwgKdpV" /><figcaption>Photo by <a href="https://unsplash.com/@altumcode?utm_source=medium&amp;utm_medium=referral">AltumCode</a> on <a href="https://unsplash.com?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Hey everyone!</strong></p><p>I’ve officially completed my first year!!</p><p>One of our final projects was to build a Sudoku solver using C programming, and I’m proud to say I got a full score for it! 🎉</p><p>So here’s a quick report of what the project was about, how I approached it, and what I learned. If you’re interested, I’d be happy to share a detailed step-by-step breakdown of the code in my next article!</p><p><strong>Initial Idea and Why It Failed:</strong></p><p>At first, I tried solving the Sudoku puzzle using a 3D array along with lots of nested if-statements inside loops. I also tried to eliminate numbers from rows and columns like we normally do when solving Sudoku by hand, by checking what numbers are already present and narrowing down the possibilities.</p><p><strong>Why the elimination approach failed:</strong></p><ul><li>It was very hard to keep track of which numbers were possible for each cell.</li><li>It wasn’t flexible, once I made a wrong assumption, the rest of the logic didn’t know how to “undo” it.</li></ul><p><strong>Why the overall idea was complicated:</strong></p><ul><li>The code became full of deeply nested if-statements, making it messy and hard to read.</li><li>Debugging was difficult, if something went wrong, I couldn’t easily trace it back.</li></ul><p>Because of all this, I decided to scrap the approach entirely and instead switch to something simpler and more reliable: backtracking with recursion.</p><p><strong>Method Used: Backtracking</strong></p><p>The method I used is called backtracking. In simple terms, backtracking works like this:</p><p><em>You try something and If it works, go forward and If it doesn’t work, go back and try something else.</em></p><p>It’s basically trial and error but in a very organized way.</p><p>In Sudoku solving, it works like this:</p><p>1. Find an empty square on the Sudoku board.</p><p>2. Try placing a number (1 to 9) into it.</p><p>3. After placing a number:</p><p>· If the move is valid (no rules are broken), continue to the next empty square.</p><p>· If later you get stuck (no number fits):</p><p>-&gt; Erase the last number (set it back to 0).</p><p>-&gt; Go back to the previous square and try a different number.</p><p>4. Keep repeating this process until the entire Sudoku is correctly filled.</p><p><strong>Challenges Faced:</strong></p><p>1. Forgetting to Erase the Number:</p><p>· Sometimes I placed a number but when it later turned out wrong, I forgot to undo it.</p><p>· This made the grid remain wrong, which caused all future steps to also be wrong.</p><p>· I fixed it by making sure to add: grid[row][col] = 0; when backtracking.</p><p>2. Forgetting to Write the Stopping Condition (Base Case):</p><p>· At first, the recursion kept going forever because I didn’t write a proper base case.</p><p>· This caused an infinite loop.</p><p>· I corrected it by adding: if (!emptyFound) return 1; to stop when the board is fully solved.</p><p>3. Accidentally Changing the Whole Puzzle:</p><p>· I sometimes made changes that accidentally affected the entire puzzle (global changes), even when I meant them to be only local.</p><p>· I became more careful with how I modified the board and understood better how variables behave during recursion.</p><p><strong>What I Could Have Done Better:</strong></p><p>1. Split the Code into Smaller Functions</p><ul><li>I crammed almost everything inside the solve() function.</li><li>If I had separated the tasks into smaller functions like:</li><li>A function to check if a number is valid,</li><li>A function to find the next empty cell,</li><li>A function to solve the puzzle,</li><li>Then the code would have been much cleaner, easier to read, and easier to debug.</li></ul><p>2. Improved Input Validation</p><ul><li>I only checked if the numbers entered were between 0 and 9.</li><li>I could have also checked:</li><li>If the initial Sudoku grid itself was already breaking rules (like same number twice in a row/column/box).</li><li>It would prevent wasting time trying to solve an invalid Sudoku.</li></ul><p><strong>What I Learned:</strong></p><p>• Backtracking and Recursion: I learned structured ways to approach problems, not just guessing.</p><p>• Code Organization Matters: Cleaner, modular code is easier to debug and improve.</p><p>• Debugging Skills: Patience is key; logical thinking helps identify issues.</p><p>• Mistakes Are Part of Learning: Failed methods taught me the value of clarity in logic.</p><ul><li>Don’t Be Afraid to Start Over: A new approach can be more effective than fixing a broken idea.</li></ul><p><em>Thanks for reading! If you enjoyed this or have ideas for enhancements, let me know in the comments. I’ll be adding more tutorials and updates on Python projects like this. If you’re interested, make sure to follow so you don’t miss out!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28a497ef79c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Built an Invoice & Billing Generator App in Python: Full Beginner’s Code Walkthrough]]></title>
            <link>https://python.plainenglish.io/how-i-built-an-invoice-billing-generator-app-in-python-full-beginners-code-walkthrough-7a59c12e714c?source=rss-00ea420bef08------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a59c12e714c</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[beginner]]></category>
            <category><![CDATA[beginners-guide]]></category>
            <category><![CDATA[python-programming]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Mokshita V P]]></dc:creator>
            <pubDate>Thu, 31 Jul 2025 16:23:27 GMT</pubDate>
            <atom:updated>2025-07-31T16:25:54.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*EgLkGCvGxfGI05n3daHrVA.jpeg" /></figure><p>Hey everyone!</p><p>If you read my <a href="https://medium.com/python-in-plain-english/building-my-first-invoice-billing-generator-app-a-beginners-journey-941edb9c1cae">last article</a>, you already know how I challenged myself, fresh into my first year as an AI/ML student, to build a real, useful software project: an <strong>Invoice &amp; Billing Generator desktop app</strong>.</p><p>That article was all about my journey, the brainstorming, obstacles, and personal lessons I took away as a beginner. Now, as promised, I’m sharing the <em>actual code</em>, breaking down each part, and letting you follow along, step by step.</p><p>Whether you’re looking for a practical Python project, want to understand GUIs and PDF handling, or just enjoy beginner stories, this guide is for you!</p><p><strong>Tools and Libraries Used</strong></p><ul><li><strong>Python:</strong> My primary programming language.</li><li><strong>Tkinter:</strong> For building the user interface (GUI).</li><li><strong>FPDF2:</strong> To generate chosen invoices as PDFs.</li><li><strong>os, subprocess, platform:</strong> Manage files and folders across Windows, macOS, and Linux.</li><li><strong>datetime:</strong> For displaying the current date.</li><li><strong>PyInstaller:</strong> (Optional) To turn the finished script into a Windows executable.</li></ul><p><strong>Project Overview</strong></p><p>This app lets you:</p><ul><li>Enter client and service details.</li><li>Instantly see auto-calculated amounts and GST totals.</li><li>Validate inputs with clear feedback.</li><li>Generate professional PDF invoices.</li><li>(On any OS) Instantly open the folder where your invoices are saved</li></ul><p>So without further ado, here’s my complete code with detailed explanations!</p><p><strong>Setting up the main window</strong></p><pre>from tkinter import *<br>from tkinter import messagebox<br>from fpdf import FPDF<br>import os<br>import subprocess<br>import platform<br>from datetime import datetime</pre><p>· tkinter is used for GUI building</p><p>· message box is for pop up messages which I used to pop up error/success messages</p><p>· fpdf is used to generate pdf invoices</p><p>· I used os to Check if folders or files exist. As I wanted to store all the invoices in a particular folder.</p><p>· Subprocess is used to open the folder where the invoices are stored</p><p>· Platform is used to detect the current os. So that the correct command can be used to open the folder</p><p>· Os, subprocess, and platform work together to store all the invoices in one folder and create a new folder if it doesn’t exist.</p><p>· Datetime is used to get and display the current date and time.</p><pre>root = Tk()<br>root.title(&quot;Invoice &amp; Billing Generator&quot;)<br>root.geometry(&quot;800x500&quot;)</pre><p>· It creates a root window, this is the main window in which all the buttons and input fields exist</p><p>· It’s title and geometry(size) is set .</p><pre># Variables<br>name_var = StringVar()<br>email_var = StringVar()<br>address_var = StringVar()<br>desc_var = StringVar()<br>quantity_var = StringVar()<br>rate_var = StringVar()<br>amount_var = StringVar()<br>gst_var = StringVar()<br>total_var = StringVar()</pre><p>· All of these are input fields for user to enter</p><pre># Invoice number<br>if not os.path.exists(&quot;invoices&quot;):<br>os.makedirs(&quot;invoices&quot;)</pre><p>· Makes sure that the folder named ”invoices” exists , to store all the invoices.</p><pre>def get_invoice_number():<br>return f&quot;INV{len(os.listdir(&#39;invoices&#39;)) + 1:04d}&quot;</pre><p>· This counts the invoices previously generated and stored and generates a new invoice number .</p><pre>invoice_number_var = StringVar(value=get_invoice_number())<br>date_var = StringVar(value=datetime.now().strftime(&#39;%d-%m-%Y&#39;))</pre><p>· Displays the current invoice number and date.</p><pre># Utility functions<br>def shake(widget):<br>x, y = root.winfo_x(), root.winfo_y()<br>for _ in range(3):<br>root.geometry(f&#39;+{x + 10}+{y}&#39;)<br>root.update()<br>root.after(50)<br>root.geometry(f&#39;+{x - 10}+{y}&#39;)<br>root.update()<br>root.after(50)<br>root.geometry(f&#39;+{x}+{y}&#39;)</pre><p>· Shakes the whole widget/root window if any input field is left empty.</p><pre>def highlight(widget):<br>try: widget.config(highlightthickness=2, highlightbackground=&quot;red&quot;)<br>except: pass<br>def unhighlight(widget):<br>try: widget.config(highlightthickness=0)<br>except: pass</pre><p>· This part of the code, uses a red border around the empty input fields to highlight them if any input field is empty ( this is simply because I wanted to have some fun and wanted to do something else other than the widget shake only)</p><pre>def calculate_amount(*args):<br>try:<br>qty = float(quantity_var.get())<br>rate = float(rate_var.get())<br>amount = qty * rate<br>amount_entry.config(state=&#39;normal&#39;)<br>amount_var.set(f&quot;{amount:.2f}&quot;)<br>amount_entry.config(state=&#39;readonly&#39;)<br>except ValueError:<br>amount_entry.config(state=&#39;normal&#39;)<br>amount_var.set(&quot;&quot;)<br>amount_entry.config(state=&#39;readonly&#39;)</pre><p>· Calculates and updates the amount field when the values change</p><pre>def calculate_total_with_gst(*args):<br>try:<br>amount = float(amount_var.get())<br>gst = float(gst_var.get())<br>total = amount + (amount * gst / 100)<br>total_entry.config(state=&#39;normal&#39;)<br>total_var.set(f&quot;{total:.2f}&quot;)<br>total_entry.config(state=&#39;readonly&#39;)<br>except ValueError:<br>total_entry.config(state=&#39;normal&#39;)<br>total_var.set(&quot;&quot;)<br>total_entry.config(state=&#39;readonly&#39;)</pre><pre><br>def live_update(*args):<br>calculate_amount()<br>calculate_total_with_gst()</pre><p>· This function acts as a bridge, gets called whenever the user changes any values and then recalculates the amount and total.</p><pre>def update_address_var(*args):<br>address_var.set(TextAddress.get(&quot;1.0&quot;, &quot;end-1c&quot;))</pre><p>· This method ensures that the address that the user entered in the multiline “Address” box on the form is always stored in the address variable in the code, allowing access in other areas of the program (such as form validation or PDF generation).</p><pre>def generate_invoice():<br>update_address_var()<br>fields = [<br>(entry_name, name_var),<br>(entry_email, email_var),<br>(TextAddress, address_var),<br>(entry_desc, desc_var),<br>(entry_quantity, quantity_var),<br>(entry_rate, rate_var),<br>(amount_entry, amount_var),<br>(entry_gst, gst_var),<br>(total_entry, total_var),<br>]<br>valid = True<br>for widget, var in fields:<br>unhighlight(widget)<br>if var.get().strip() == &quot;&quot;:<br>highlight(widget)<br>shake(widget)<br>valid = False<br>if not valid:<br>messagebox.showerror(&quot;Error&quot;, &quot;Please fill all required fields!&quot;)<br>return<br>invoice_number = get_invoice_number()<br>filename = f&quot;invoices/{invoice_number}.pdf&quot;<br>pdf = FPDF()<br>pdf.add_page()<br>pdf.set_font(&quot;Arial&quot;, size=12)<br>pdf.cell(200, 10, txt=&quot;Invoice &amp; Billing Generator&quot;, ln=True, align=&quot;C&quot;)<br>pdf.cell(200, 10, txt=f&quot;Invoice No: {invoice_number}&quot;, ln=True, align=&quot;R&quot;)<br>pdf.cell(200, 10, txt=f&quot;Date: {date_var.get()}&quot;, ln=True, align=&quot;R&quot;)<br>pdf.ln(10)<br>pdf.cell(200, 10, txt=&quot;Client Details:&quot;, ln=True)<br>pdf.cell(200, 10, txt=f&quot;Name: {name_var.get()}&quot;, ln=True)<br>pdf.cell(200, 10, txt=f&quot;Email: {email_var.get()}&quot;, ln=True)<br>pdf.multi_cell(200, 10, txt=f&quot;Address: {address_var.get()}&quot;)<br>pdf.ln(5)<br>pdf.cell(200, 10, txt=&quot;Service Details:&quot;, ln=True)<br>pdf.cell(200, 10, txt=f&quot;Description: {desc_var.get()}&quot;, ln=True)<br>pdf.cell(200, 10, txt=f&quot;Quantity: {quantity_var.get()}&quot;, ln=True)<br>pdf.cell(200, 10, txt=f&quot;Rate: Rs. {rate_var.get()}&quot;, ln=True)<br>pdf.cell(200, 10, txt=f&quot;Amount: Rs. {amount_var.get()}&quot;, ln=True)<br>pdf.cell(200, 10, txt=f&quot;GST: {gst_var.get()}%&quot;, ln=True)<br>pdf.cell(200, 10, txt=f&quot;Total: Rs. {total_var.get()}&quot;, ln=True)<br>pdf.output(filename)<br>messagebox.showinfo(&quot;Success&quot;, f&quot;Invoice saved as {filename}&quot;)<br>clear_form()<br>invoice_number_var.set(get_invoice_number())</pre><p>· This pulls all the input values.</p><p>· Checks the input fields and if any field is empty, the widget shakes and highlightes the missing fields.</p><p>· Else if it’s valid:</p><p>— It generates a new PDF with all info structured in proper sections</p><p>— Saves the PDF in invoices folder.</p><p>— Alerts user.</p><p>— Resets the form for next entry.</p><pre>def open_invoice_folder():<br>folder_path = os.path.abspath(&quot;invoices&quot;)<br>if not os.path.exists(folder_path):<br>os.makedirs(folder_path)<br>if platform.system() == &quot;Windows&quot;:<br>os.startfile(folder_path)<br>elif platform.system() == &quot;Darwin&quot;:<br>subprocess.Popen([&quot;open&quot;, folder_path])<br>else:<br>subprocess.Popen([&quot;xdg-open&quot;, folder_path])</pre><p><em>·</em> Detects the current os to open invoices directory in the user’s file explorer (I wanted it to work on any os especially since I plan on adding more features to it as I learn)</p><pre>def clear_form():<br>for var in [name_var, email_var, address_var, desc_var, quantity_var, rate_var, amount_var, gst_var, total_var]:<br>var.set(&quot;&quot;)TextAddress.delete(&quot;1.0&quot;, END)<br>for widget in [entry_name, entry_email, TextAddress, entry_desc, entry_quantity, entry_rate, amount_entry, entry_gst, total_entry]:<br>unhighlight(widget)<br></pre><ul><li>It empties all fields and removes highlights.</li></ul><pre>def exit_app():<br>root.destroy()</pre><ul><li>Closes the application.</li></ul><pre># Live calculation binding<br>quantity_var.trace_add(&#39;write&#39;, live_update)<br>rate_var.trace_add(&#39;write&#39;, live_update)<br>gst_var.trace_add(&#39;write&#39;, live_update)</pre><ul><li>Whenever Quantity, Rate, or GST is changed, amounts are automatically recalculated. (because I didn’t want to clear the whole form and start over again if i wanted to change the values)</li></ul><pre># Top header<br>top_frame = Frame(root)<br>top_frame.pack(pady=5)<br>Label(top_frame, textvariable=invoice_number_var, font=(&quot;Arial&quot;, 10, &quot;bold&quot;)).grid(row=0, column=0, padx=10)<br>Label(top_frame, textvariable=date_var, font=(&quot;Arial&quot;, 10)).grid(row=0, column=1, padx=10)</pre><ul><li>Top Header Shows the invoice number and date.</li></ul><pre># Main frames<br>main_frame = Frame(root)<br>main_frame.pack()<br># Client Info Frame<br>client_frame = LabelFrame(main_frame, text=&quot;Client Info&quot;, padx=10, pady=10)<br>client_frame.grid(row=0, column=0, padx=10)<br>Label(client_frame, text=&quot;Client Name:&quot;).grid(row=0, column=0, sticky=W)<br>entry_name = Entry(client_frame, textvariable=name_var, width=30)<br>entry_name.grid(row=0, column=1)<br>Label(client_frame, text=&quot;Email:&quot;).grid(row=1, column=0, sticky=W)<br>entry_email = Entry(client_frame, textvariable=email_var, width=30)<br>entry_email.grid(row=1, column=1)<br>Label(client_frame, text=&quot;Address:&quot;).grid(row=2, column=0, sticky=NW)<br>TextAddress = Text(client_frame, height=3, width=30)<br>TextAddress.grid(row=2, column=1)<br>TextAddress.bind(&quot;&lt;KeyRelease&gt;&quot;, update_address_var)<br># Service Info Frame<br>service_frame = LabelFrame(main_frame, text=&quot;Service Details&quot;, padx=10, pady=10)<br>service_frame.grid(row=0, column=1, padx=10)<br>Label(service_frame, text=&quot;Service Description:&quot;).grid(row=0, column=0, sticky=W)<br>entry_desc = Entry(service_frame, textvariable=desc_var, width=30)<br>entry_desc.grid(row=0, column=1)<br>Label(service_frame, text=&quot;Quantity:&quot;).grid(row=1, column=0, sticky=W)<br>entry_quantity = Entry(service_frame, textvariable=quantity_var)<br>entry_quantity.grid(row=1, column=1)<br>Label(service_frame, text=&quot;Rate (₹):&quot;).grid(row=2, column=0, sticky=W)<br>entry_rate = Entry(service_frame, textvariable=rate_var)<br>entry_rate.grid(row=2, column=1)<br>Label(service_frame, text=&quot;Amount (₹):&quot;).grid(row=3, column=0, sticky=W)<br>amount_entry = Entry(service_frame, textvariable=amount_var, state=&#39;readonly&#39;)<br>amount_entry.grid(row=3, column=1)<br>Label(service_frame, text=&quot;GST (%):&quot;).grid(row=4, column=0, sticky=W)<br>entry_gst = Entry(service_frame, textvariable=gst_var)<br>entry_gst.grid(row=4, column=1)<br>Label(service_frame, text=&quot;Total (₹):&quot;).grid(row=5, column=0, sticky=W)<br>total_entry = Entry(service_frame, textvariable=total_var, state=&#39;readonly&#39;)<br>total_entry.grid(row=5, column=1)</pre><ul><li>This code consists of two main frames:<br> — Client Info (left): Name, Email, Address.<br> — Service Details (right): Description, Quantity, Rate, Amount (auto), GST, Total (auto).</li><li>The whole code is creating input fields and positioning them on the window.</li><li>Label is the text written beside the input field to let the user know what needs to be written there</li><li>Entry creates the input fields.</li><li>Grid is its position on the widget</li></ul><pre># Buttons<br>button_frame = Frame(root)<br>button_frame.pack(pady=10)<br>Button(button_frame, text=&quot;Generate Invoice&quot;, bg=&quot;blue&quot;, fg=&quot;white&quot;, command=generate_invoice).grid(row=0, column=0, padx=10)<br>Button(button_frame, text=&quot;Clear Form&quot;, command=clear_form).grid(row=0, column=1, padx=10)<br>Button(button_frame, text=&quot;Exit&quot;, command=exit_app).grid(row=0, column=2, padx=10)<br>Button(button_frame, text=&quot;Open Invoice Folder&quot;, command=open_invoice_folder).grid(row=0, column=3, padx=10)</pre><ul><li>Buttons are used for generating the invoice, clearing the form, exiting, and opening invoices folder.</li><li>These buttons link the primary user actions (create invoice, reset, quit, and view invoices) to interactive controls that are clearly labeled, which makes the application practical and easy to use.</li><li>I especially added the “open invoice folder “ button because even though I knew a new folder is created , It was annoying to search for it again and again ,since I was deleting the whole folder n editing the code and testing.</li></ul><pre># Enter key navigation<br>def bind_enter_key_sequence():<br>entry_name.bind(&quot;&lt;Return&gt;&quot;, lambda e: entry_email.focus_set())<br>entry_email.bind(&quot;&lt;Return&gt;&quot;, lambda e: TextAddress.focus_set())<br>TextAddress.bind(&quot;&lt;Return&gt;&quot;, lambda e: entry_desc.focus_set())<br>entry_desc.bind(&quot;&lt;Return&gt;&quot;, lambda e: entry_quantity.focus_set())<br>entry_quantity.bind(&quot;&lt;Return&gt;&quot;, lambda e: entry_rate.focus_set())<br>entry_rate.bind(&quot;&lt;Return&gt;&quot;, lambda e: entry_gst.focus_set())<br>entry_gst.bind(&quot;&lt;Return&gt;&quot;, lambda e: entry_name.focus_set())<br>bind_enter_key_sequence()</pre><ul><li>Allows user to move to the next field with clicked on Enter key(I added this as it felt kinda frustrating to move the cursor to the next input field)</li></ul><pre># Start app<br>root.mainloop()</pre><p><em>·</em> Starts the Tkinter event loop, displaying the window.</p><p><strong>Project Summary</strong></p><p>· Automatic invoice numbering and date stamping</p><p>· Live updating of total and GST</p><p>· Instant visual feedback for missing fields</p><p>· Platform-independent folder management</p><p>· Professional-looking, valid PDF output every time</p><p>· Keyboard navigation for speed</p><p>· Clean, user-friendly interface</p><p><strong>User Flow:</strong><br> Enter client and service details → See auto-calculated totals → Generate a PDF invoice → Open the invoice folder — all in just a few clicks!</p><p><em>Thanks for reading! If you enjoyed this tutorial or have ideas for enhancements, let me know in the comments. I’ll be adding more tutorials and updates on Python projects like this. If you’re interested, make sure to follow so you don’t miss out!</em></p><h3>Thank you for being a part of the community</h3><p><em>Before you go:</em></p><ul><li>Be sure to <strong>clap</strong> and <strong>follow</strong> the writer ️👏️<strong>️</strong></li><li>Follow us: <a href="https://x.com/inPlainEngHQ"><strong>X</strong></a> | <a href="https://www.linkedin.com/company/inplainenglish/"><strong>LinkedIn</strong></a> | <a href="https://www.youtube.com/@InPlainEnglish"><strong>YouTube</strong></a> | <a href="https://newsletter.plainenglish.io/"><strong>Newsletter</strong></a> | <a href="https://open.spotify.com/show/7qxylRWKhvZwMz2WuEoua0"><strong>Podcast</strong></a> | <a href="https://twitch.tv/inplainenglish"><strong>Twitch</strong></a></li><li><a href="https://differ.blog/"><strong>Start your own free AI-powered blog on Differ</strong></a> 🚀</li><li><a href="https://discord.gg/in-plain-english-709094664682340443"><strong>Join our content creators community on Discord</strong></a> 🧑🏻‍💻</li><li>For more content, visit <a href="https://plainenglish.io/"><strong>plainenglish.io</strong></a> + <a href="https://stackademic.com/"><strong>stackademic.com</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a59c12e714c" width="1" height="1" alt=""><hr><p><a href="https://python.plainenglish.io/how-i-built-an-invoice-billing-generator-app-in-python-full-beginners-code-walkthrough-7a59c12e714c">How I Built an Invoice &amp; Billing Generator App in Python: Full Beginner’s Code Walkthrough</a> was originally published in <a href="https://python.plainenglish.io">Python in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building My First Invoice & Billing Generator App: A Beginner’s Journey]]></title>
            <link>https://python.plainenglish.io/building-my-first-invoice-billing-generator-app-a-beginners-journey-941edb9c1cae?source=rss-00ea420bef08------2</link>
            <guid isPermaLink="false">https://medium.com/p/941edb9c1cae</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[beginner]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Mokshita V P]]></dc:creator>
            <pubDate>Thu, 24 Jul 2025 19:51:51 GMT</pubDate>
            <atom:updated>2025-07-24T19:51:51.563Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*uvXx5D6SdkfT76JcBy2esg.jpeg" /></figure><p>Hey everyone!</p><p>I’m a first-year AI/ML student, and this year I challenged myself to build my <strong>first real software project</strong> — an <strong>Invoice &amp; Billing Generator desktop app</strong>. What started as a small idea to practice Python ended up teaching me so much about <strong>coding, GUIs, file handling, and real-world problem-solving</strong>. And most importantly, patience</p><p>Here’s my full journey — from idea to a working .exe app, plus what I learned along the way.</p><h3>Why I Chose This Project</h3><p>I wanted something <strong>practical and useful</strong>. Invoices are something freelancers, small businesses, or even students doing internships can use regularly. Also:</p><ul><li>It covers <strong>programming basics</strong>: GUI design, user input, file operations, and PDF generation</li><li>I can <strong>expand it in the future</strong> with more features, and I can possibly add AI too!</li><li>My professor suggested picking a long-term project to keep improving as I learn more coding skills</li><li>I plan on connecting it to an actual database in the future .</li></ul><h3>Tools I Used</h3><ul><li><strong>Python</strong> — my main programming language</li><li><strong>Tkinter</strong> — for the GUI</li><li><strong>fpdf2</strong> — to generate PDF invoices</li><li><strong>PyInstaller</strong> — to convert my script into a Windows .exe</li></ul><h3>Step 1: Setting Up My Development Environment</h3><p>Before starting to write any code, I made sure to set up everything properly:</p><p>✔️ Installed Python, VS Code, Tkinter, and fpdf2</p><p>✔️ Configured PyInstaller for later packaging</p><p>✔️ Tested by running basic .py files to check dependencies</p><p>This setup step made the project feel <em>real</em> and boosted my motivation.</p><h3>Step 2: Sketching The User Interface</h3><p>I watched a YouTube tutorial on <strong>Tkinter Layout Basics</strong> to understand .pack(), .grid(), and .place() positioning. Then I sketched a simple wireframe:</p><ul><li>Client details (Name, Email)</li><li>Service description</li><li>Rate and quantity</li><li>A button to generate the invoice</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bMv7kzvXPz7yPddFb-Apdg.jpeg" /></figure><p>The UI is <strong>minimal for now because, as a first-year student, I have yet to know what else is needed. As of writing this, I have more ideas on what else to add, like company’s address.</strong></p><h3>Key takeaway:</h3><p>Creating a rough wireframe <em>before coding</em> reduced confusion and improved my coding flow.</p><h3>Step 3: Building the Input Form</h3><p>Once my UI layout was ready on paper, I coded the basic form in Tkinter and tested it with dummy data. Pressing <strong>Generate Invoice</strong> triggered the PDF creation process using fpdf2.</p><p>Seeing the first PDF generate felt amazing. It wasn’t pretty at first, but it <strong>worked</strong> — and that felt like a big win.</p><h3>Step 4: Organizing Output Files</h3><p>Initially, all invoices were saving in some folder but i didn’t know where, So I:</p><ul><li>Imported Python’s <strong>os module</strong></li><li>Checked if an invoices folder existed; if not, created it</li><li>Saved each PDF in that folder with a filename</li></ul><p>But then i couldn’t find where that folder was, so i created a button which, when clicked would open the folder.</p><h3>What I Learned:</h3><p>Good file organization matters <em>a lot</em>, even in small projects. At</p><h3>Step 5: Adding Smart Features</h3><p>By the end of a few weeks, my app had:</p><p>✔️ <strong>Smooth input navigation</strong> — pressing Enter moved to the next field</p><p>✔️ <strong>Auto-calculation &amp; validation</strong> — calculations updated automatically; empty fields shook to grab attention</p><p>✔️ <strong>Unique invoice IDs</strong> — each invoice had an incremented ID</p><p>✔️ <strong>Past invoice viewer</strong> — a button to list all previously generated invoices</p><p>✔️ <strong>.exe packaging</strong> — the app was now portable and installable on any Windows system</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*EgLkGCvGxfGI05n3daHrVA.jpeg" /></figure><p>Seeing it all come together felt surreal — what started as an idea on paper was now a <strong>fully functional, usable app</strong>.</p><h3>What’s Next</h3><p>This is just <strong>version 1</strong>. In the coming months, I plan to add:</p><ul><li>more input fields</li><li>i’ve realized that one company might provide more than one service</li></ul><p>I aim to keep evolving it as I learn more AI and software development skills.</p><h3>Final Thoughts</h3><p>Starting this project taught me:</p><ul><li>How powerful <strong>small daily progress</strong> is</li><li>That real-world projects teach far more than tutorial codes</li><li>Debugging and layout spacing aren’t as scary after a few attempts</li><li><strong>Learning by building</strong> is the best way to grow as a beginner programmer</li></ul><p>If you’re thinking about your first project, here’s my advice:</p><p>-&gt; <strong>Start scrappy</strong></p><p>-&gt; <strong>Stay consistent</strong></p><p>-&gt; <strong>Make it yours</strong></p><p>You’ll be surprised how much you grow by the end.</p><p><em>Thanks for reading my journey! If you’re building your own Invoice Generator or similar beginner projects, I’d love to hear about them. Drop a comment or connect with me on Medium and LinkedIn.</em></p><h3>Next Post Teaser</h3><p>In my upcoming post, I’ll share a <strong>step-by-step guide</strong> with code snippets on how I used fpdf2 and Tkinter to build this app from scratch. Stay tuned!</p><h3>Thank you for being a part of the community</h3><p><em>Before you go:</em></p><ul><li>Be sure to <strong>clap</strong> and <strong>follow</strong> the writer ️👏️<strong>️</strong></li><li>Follow us: <a href="https://x.com/inPlainEngHQ"><strong>X</strong></a> | <a href="https://www.linkedin.com/company/inplainenglish/"><strong>LinkedIn</strong></a> | <a href="https://www.youtube.com/@InPlainEnglish"><strong>YouTube</strong></a> | <a href="https://newsletter.plainenglish.io/"><strong>Newsletter</strong></a> | <a href="https://open.spotify.com/show/7qxylRWKhvZwMz2WuEoua0"><strong>Podcast</strong></a> | <a href="https://twitch.tv/inplainenglish"><strong>Twitch</strong></a></li><li><a href="https://differ.blog/"><strong>Start your own free AI-powered blog on Differ</strong></a> 🚀</li><li><a href="https://discord.gg/in-plain-english-709094664682340443"><strong>Join our content creators community on Discord</strong></a> 🧑🏻‍💻</li><li>For more content, visit <a href="https://plainenglish.io/"><strong>plainenglish.io</strong></a> + <a href="https://stackademic.com/"><strong>stackademic.com</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=941edb9c1cae" width="1" height="1" alt=""><hr><p><a href="https://python.plainenglish.io/building-my-first-invoice-billing-generator-app-a-beginners-journey-941edb9c1cae">Building My First Invoice &amp; Billing Generator App: A Beginner’s Journey</a> was originally published in <a href="https://python.plainenglish.io">Python in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Wrapping Up the Build — Tying It All Together]]></title>
            <link>https://medium.com/@mokshitavp/wrapping-up-the-build-tying-it-all-together-eb01581a9b7a?source=rss-00ea420bef08------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb01581a9b7a</guid>
            <category><![CDATA[python-programming]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[tkinter-gui]]></category>
            <category><![CDATA[student-developer]]></category>
            <category><![CDATA[projects]]></category>
            <dc:creator><![CDATA[Mokshita V P]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 17:07:49 GMT</pubDate>
            <atom:updated>2025-06-25T17:07:49.482Z</atom:updated>
            <content:encoded><![CDATA[<h3>🧩 Wrapping Up the Build — Tying It All Together</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*DYSPKV8BVPDPkwPPc7n94g.png" /><figcaption><strong>Midway snapshot — wiring up enter-key navigation and final buttons before the main loop kicks in</strong></figcaption></figure><p>It’s wild to think this all started with a basic sketch and an empty Python file.</p><p>Over the past few weeks, I’ve been steadily building this invoice generator project — a tool that seemed simple at first but turned out to be full of opportunities to learn. From figuring out layout spacing to debugging why the form wouldn’t respond, every little piece added something to the experience.</p><p>And now… it’s finally complete. Well, <strong>version 1</strong>, at least.</p><h3>✨ What I’ve Managed to Do So Far:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*QTxXwxCpL5hafclY2g0guA.png" /><figcaption><strong>A look at the final interface with smart validation and calculation</strong></figcaption></figure><p>Without going into all the specifics, here’s a rough idea of what the app does now:</p><ul><li>The form’s a lot smarter than when I started. Inputs respond naturally — pressing enter moves to the next box.</li><li>Calculations update automatically when the data changes, and basic validation ensures no field gets missed (with a little shake to get your attention 👀).</li><li>Every invoice gets a unique ID that increments automatically.</li><li>You get a little message when it’s successfully done — kind of satisfying, tbh.</li><li>Oh, and there’s a button to view all the past invoices instantly.</li><li>And yes — it’s a .exe file now too. Portable, clean, and functional.</li></ul><h3>What’s Next?</h3><p>Right now, the core stuff is done. But I already have a list of future add-ons I want to explore over time:</p><ul><li>Smarter entry predictions</li><li>Analytics and insights</li><li>Maybe even a voice assistant?</li></ul><p>This isn’t one of those “done and never touched again” things. I’m hoping to keep revisiting it — adding bits, fixing things, and slowly evolving it into something I’m really proud of.</p><h3>Final Thoughts</h3><p>I started this with one goal in mind — to build something real, from the ground up.<br> Every step of the way taught me something, whether it was figuring out how layout works or realizing how much smoother things feel when the small details (like auto-filling or field validation) just <em>work</em>.</p><p>This isn’t just a one-time project either — I want to keep improving it over time, slowly making it smarter and cleaner as I learn more.</p><p>If you’ve followed along with these updates, thank you. And if you’re thinking of starting your own project but unsure where to begin, I’ll just say this: start scrappy, stay consistent, and don’t be afraid to make it yours.</p><p>More updates soon (maybe with a fancy dashboard 👀),</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb01581a9b7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stepping Into the Core — Organizing the Output]]></title>
            <link>https://medium.com/@mokshitavp/stepping-into-the-core-organizing-the-output-b2e9fbb66065?source=rss-00ea420bef08------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2e9fbb66065</guid>
            <category><![CDATA[beginnerapp]]></category>
            <category><![CDATA[beginner-python-project]]></category>
            <category><![CDATA[studentdev]]></category>
            <category><![CDATA[tkinter]]></category>
            <category><![CDATA[guiinpython]]></category>
            <dc:creator><![CDATA[Mokshita V P]]></dc:creator>
            <pubDate>Tue, 10 Jun 2025 05:02:44 GMT</pubDate>
            <atom:updated>2025-06-10T05:02:44.295Z</atom:updated>
            <content:encoded><![CDATA[<h3>Stepping Into the Core — Organizing the Output</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rhe1pe7cFOuFKF6Neh38kw.jpeg" /></figure><p>It’s been a few days into the project, and things are <em>finally</em> starting to feel like they’re coming together!</p><p>After getting the basic GUI up and running and being able to generate a PDF invoice from the form data (which was a great feeling btw), I noticed a small but annoying problem — all my invoices were just piling up in the main folder. Not only messy, but it also made me wonder: what happens when I have 20+ invoices? Or even 100?</p><p>So, today’s goal was to <strong>create a proper folder structure</strong> and make sure that every invoice gets stored inside a dedicated invoices folder. Nothing fancy yet, just something clean and simple.</p><h3>What I Did</h3><ul><li>I used Python’s os module to check if an invoices folder exists.</li><li>If it doesn’t, the app now <em>automatically creates it</em> the moment I hit “Generate Invoice.”</li><li>Then it saves the PDF into that folder, using a filename like invoice_&lt;clientname&gt;_&lt;timestamp&gt;.pdf.</li></ul><p>This small change made such a big difference. Now, everything’s much more organized, and it even feels like a “real” app, not just a bunch of files dumped into one place.</p><h3>What I Learned</h3><ul><li>How to use os.path.exists() and os.makedirs() to handle folder creation in Python</li><li>How to change the save path for files generated by the app</li><li>That good file organization <em>really</em> matters when building something even slightly serious 😅</li></ul><h3>What’s Next</h3><p>I want to be able to <strong>view all past invoices</strong> in a list or some kind of dashboard inside the app. I think that’ll make the whole flow more user-friendly.</p><p>I also haven’t added delete/edit options yet. Those are coming later once the core features are stable.</p><p>That’s all for this update!<br> If you’re following along or building your own version, let me know how it’s going for you too!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2e9fbb66065" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kicking Off the Build: Setting Up & Sketching the UI]]></title>
            <link>https://medium.com/@mokshitavp/kicking-off-the-build-setting-up-sketching-the-ui-e6aeedaf8576?source=rss-00ea420bef08------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6aeedaf8576</guid>
            <category><![CDATA[tkinter-gui]]></category>
            <category><![CDATA[invoice-app]]></category>
            <category><![CDATA[student-project]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[my-coding-journey]]></category>
            <dc:creator><![CDATA[Mokshita V P]]></dc:creator>
            <pubDate>Sat, 31 May 2025 11:46:58 GMT</pubDate>
            <atom:updated>2025-05-31T11:46:58.960Z</atom:updated>
            <content:encoded><![CDATA[<p>Taking the first real steps toward building a functional, clean invoice generator.</p><h3>Setting Up My Dev Environment</h3><p>Before writing a single line of code, I wanted to get everything set up properly. Here’s what I installed and configured:</p><ul><li><strong>Python</strong>: My main language for this project.</li><li><strong>VS Code</strong>: Clean, extensible, and beginner-friendly. I made sure everything was working properly, including running basic .py files.</li><li><strong>Tkinter</strong>: I’ll be using this for building the GUI.</li><li><strong>fpdf2</strong>: This will help with generating the final invoice in PDF format.</li><li><strong>PyInstaller</strong>: I’ll use this later to convert the script into a .exe file for offline use.</li></ul><p>Having all the tools ready made me feel like the project was becoming real.</p><h3>Sketching the UI</h3><p>I watched this video on <a href="https://youtu.be/YXPyB4XeYLA">Tkinter Layout Basics</a>, which helped me understand how to place widgets properly using .pack(), .grid(), and .place().</p><p>Based on that, I quickly sketched a rough wireframe for the app:</p><ul><li>Client details (name, email)</li><li>Service description</li><li>Rate and quantity</li><li>A button to generate the invoice</li></ul><p>The goal is to keep things <strong>simple and clean</strong> — no clutter, just what’s needed for a small freelancer or student to send a professional-looking bill.</p><p><em>(If you’re curious, here’s a sneak peek of what I’m thinking visually — I’ll share better screenshots once it’s built.)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uQygRNmIE10taRCWmfUIRA.png" /></figure><h3>What I Learned Today</h3><ul><li>Installing tools takes longer than you expect when you’re being careful.</li><li>A visual wireframe helps reduce confusion while coding.</li><li>Tkinter is beginner-friendly but still flexible enough for decent-looking UIs.</li><li>Starting small actually builds momentum.</li></ul><p>This was a calm but productive start. Tomorrow, I’ll begin building the basic input form in Tkinter and test it with dummy data.</p><p>Let’s see how it turns out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6aeedaf8576" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Starting My First Software Project: Invoice & Billing Generator]]></title>
            <link>https://medium.com/@mokshitavp/starting-my-first-software-project-invoice-billing-generator-d215b0324f8f?source=rss-00ea420bef08------2</link>
            <guid isPermaLink="false">https://medium.com/p/d215b0324f8f</guid>
            <category><![CDATA[beginner-developers]]></category>
            <category><![CDATA[ai-ml-student-projects]]></category>
            <category><![CDATA[python-programming]]></category>
            <category><![CDATA[tkinter]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Mokshita V P]]></dc:creator>
            <pubDate>Wed, 28 May 2025 15:49:01 GMT</pubDate>
            <atom:updated>2025-05-28T15:49:01.825Z</atom:updated>
            <content:encoded><![CDATA[<p>My journey building an invoice generator app from scratch — learning Python, GUI, and AI tools along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F_Zc9l46FLlGDKzqu9NuHg.avif" /></figure><h3>Hey everyone!</h3><p>I’m a first-year AI/ML student, and I’m about to start my first real software project — an <strong>Invoice &amp; Billing Generator</strong> desktop app.</p><p>I want to build something useful for freelancers or small businesses, and also challenge myself to improve my coding skills. This will be a long-term project that I plan to keep adding to as I learn more AI and software development.</p><h3>Why this project?</h3><p>I chose this because:</p><ul><li>It’s practical — invoices are something people actually need.</li><li>It involves important programming basics like making a GUI, handling user input, working with files, and generating PDFs.</li><li>It fits well with my goal of eventually adding AI features like auto-complete, smart categorization, or voice commands.</li></ul><p>Also, I was encouraged early on to pick a project I can grow over time, so this felt like a perfect fit.</p><h3>What I’ll be using</h3><ul><li><strong>Python</strong> — my main programming language</li><li><strong>Tkinter</strong> — for creating the desktop app’s interface</li><li><strong>fpdf2</strong> — to generate PDF invoices</li><li><strong>PyInstaller</strong> — to package my app into a Windows executable (.exe)</li><li><strong>ChatGPT</strong> — as a helper to explain concepts or suggest solutions when I get stuck</li></ul><h3>How I plan to work on it</h3><p>I’ve broken the project into smaller goals so I can make steady progress each day. I’ll try to figure things out on my own first, then turn to AI tools or other resources only when I’m stuck or need extra help.</p><p>I want to make sure I’m really learning and not just copying code. I’ll also be keeping a diary of what I learn every day to keep track of my progress.</p><h3>What’s next?</h3><p>I’ll start coding the basic app soon, with a simple form to enter client info and services. Then I’ll work on generating PDF invoices and saving records.</p><p>I’m excited (and a little nervous), but mostly ready to get started and learn as I go!</p><h3>Follow along!</h3><p>I’ll be blogging my progress regularly — sharing what I’ve learned, what problems I faced, and how I solved them. If you’re interested in software projects or AI-assisted coding, stay tuned!</p><h4>Upcoming Milestones:<br>- [ ] Design the client and service input form<br>- [ ] Generate a basic PDF invoice<br>- [ ] Save invoice history<br>- [ ] Package app into a .exe<br>- [ ] Add optional AI features</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d215b0324f8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>