<?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 Abhijith Purohit on Medium]]></title>
        <description><![CDATA[Stories by Abhijith Purohit on Medium]]></description>
        <link>https://medium.com/@abhijithpurohit?source=rss-2def82b6e88d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DAzvLjFG8CA84CDa_pFT4w@2x.jpeg</url>
            <title>Stories by Abhijith Purohit on Medium</title>
            <link>https://medium.com/@abhijithpurohit?source=rss-2def82b6e88d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:20:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abhijithpurohit/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[I Thought Indie Hacking Was About Building. I Was Wrong.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://abhijithpurohit.medium.com/i-thought-indie-hacking-was-about-building-i-was-wrong-33a21ab96456?source=rss-2def82b6e88d------2"><img src="https://cdn-images-1.medium.com/max/1672/1*3A1cQtN92RwjTG2WroKCNw.png" width="1672"></a></p><p class="medium-feed-snippet">I didn&#x2019;t really start by telling myself, &#x201C;I&#x2019;m going to become an indie hacker.&#x201D;</p><p class="medium-feed-link"><a href="https://abhijithpurohit.medium.com/i-thought-indie-hacking-was-about-building-i-was-wrong-33a21ab96456?source=rss-2def82b6e88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://abhijithpurohit.medium.com/i-thought-indie-hacking-was-about-building-i-was-wrong-33a21ab96456?source=rss-2def82b6e88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/33a21ab96456</guid>
            <category><![CDATA[indiedev]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[founder-stories]]></category>
            <category><![CDATA[solopreneur]]></category>
            <dc:creator><![CDATA[Abhijith Purohit]]></dc:creator>
            <pubDate>Wed, 30 Sep 2026 16:10:03 GMT</pubDate>
            <atom:updated>2026-09-30T16:10:03.841Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Vibe Coding in 2026: I Ship Faster, but I Review More Than Ever]]></title>
            <link>https://abhijithpurohit.medium.com/vibe-coding-in-2026-i-ship-faster-but-i-review-more-than-ever-1002275d0385?source=rss-2def82b6e88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1002275d0385</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <dc:creator><![CDATA[Abhijith Purohit]]></dc:creator>
            <pubDate>Sat, 01 Aug 2026 06:06:32 GMT</pubDate>
            <atom:updated>2026-08-03T11:07:42.997Z</atom:updated>
            <content:encoded><![CDATA[<h4>How AI coding tools changed the way I build software, test ideas, and think about being a developer</h4><p>A few years ago, starting a software project meant opening an empty editor and preparing for a long night.</p><p>I created the folders.</p><p>I installed the libraries.</p><p>I connected the database.</p><p>I built the first screen.</p><p>Then I spent two hours fixing a setup problem before writing anything related to the actual product.</p><p>That was simply how coding worked.</p><p>Today, I often begin with a paragraph.</p><p>I explain what I want to build, how the current system works, what should not change, and how I expect the feature to behave.</p><p>An AI coding tool reads the project, suggests a plan, changes several files, runs commands, and explains what it did.</p><p>Sometimes the result is surprisingly good.</p><p>Sometimes it breaks something that was working perfectly and confidently tells me that the task is complete.</p><p>Welcome to vibe coding.</p><blockquote><strong><em>I write less code by hand now, but I spend more time explaining decisions.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33zesLswbY7vrt8vNKhhcg.png" /><figcaption>Depiction of Vibe coding and traditional Coding</figcaption></figure><h3>What Is Vibe Coding?</h3><p>Vibe coding is a way of building software by describing what you want in normal language and allowing an AI coding tool to generate much of the code.</p><p>Instead of writing every function yourself, you guide the tool through a conversation.</p><p>You might start with:</p><blockquote><em>Create a page where users can upload a document.</em></blockquote><p>Then continue with:</p><blockquote><em>Show the upload progress.</em></blockquote><blockquote><em>Do not accept files larger than 20 MB.</em></blockquote><blockquote><em>Handle failed uploads without clearing the page.</em></blockquote><p>The software slowly takes shape through instructions, tests, corrections, and repeated attempts.</p><p>It sounds simple, but good vibe coding is not only about writing clever prompts.</p><p>The real work is deciding what the product should do, checking what the tool created, and finding what it misunderstood.</p><h3>How I Learned to Build Software</h3><p>I learned software development in the traditional way.</p><p>I have worked with C, C++, Python, APIs, databases, desktop applications, embedded systems, and web products.</p><p>For most of my career, there was no tool that could inspect an entire project and complete a feature after reading a few sentences.</p><p>When a program crashed, I used a debugger.</p><p>When an application became slow, I checked the logs, memory usage, execution time, and data flow.</p><p>When a function failed, I followed the code until I understood why.</p><p>It was slower, but it forced me to understand what the machine was doing.</p><p>That knowledge still matters.</p><p>AI coding tools can generate a large amount of code very quickly.</p><p>They can also generate a large amount of bad code very quickly.</p><blockquote><strong><em>The ability to produce code is becoming cheaper. The ability to judge code is becoming more valuable.</em></strong></blockquote><h3>Building AskQuest Showed Me What Changed</h3><p>One of the products I have been working on is AskQuest.</p><p>The idea started simply.</p><p>I wanted to open a long webpage and turn it into something easier to understand.</p><p>The output could be:</p><ul><li>A short summary</li><li>Key points</li><li>A deeper explanation</li><li>A beginner-friendly version</li><li>Text that could be read aloud</li></ul><p>The main idea was easy to explain.</p><p>Building it involved many smaller decisions.</p><p>How should the browser extension find the real article?</p><p>How should it separate useful text from menus, ads, buttons, and unrelated links?</p><p>What should happen when a page contains very little readable content?</p><p>How should the system handle a very long document?</p><p>How can the summary remain connected to the original source?</p><p>What should the interface show when a request fails?</p><p>An AI coding tool can quickly create a browser extension, API request, database model, or React component.</p><p>What it cannot do is understand all my product decisions without enough context.</p><h3>My First Instructions Were Too Simple</h3><p>At first, I gave short instructions.</p><blockquote><em>Add a summary feature.</em></blockquote><p>The result technically worked.</p><p>But it was not the feature I had imagined.</p><p>The output was too long.</p><p>The error handling was weak.</p><p>The interface did not match the rest of the product.</p><p>Important situations were completely ignored.</p><p>The tool had followed my sentence.</p><p>It had not understood my intention.</p><p>That changed the way I work.</p><p>Now, before asking an AI coding tool to write code, I explain:</p><ol><li>The user problem</li><li>The current behaviour</li><li>The expected result</li><li>The cases that could fail</li><li>The parts that must not change</li></ol><p>The quality improves when the thinking happens before the code generation.</p><h3>The Fastest Part of Coding Is No Longer Typing</h3><p>Writing code was never the only difficult part of software development.</p><p>You still have to understand the user.</p><p>You still have to decide what to build.</p><p>You still have to choose how different parts of the system communicate.</p><p>You still have to think about security, performance, failures, maintenance, and future changes.</p><p>AI coding tools have made typing code much faster.</p><p>They can create forms, API endpoints, database tables, test files, and user interfaces in minutes.</p><p>But faster code creates another problem.</p><p>It becomes very easy to create too much of it.</p><p>I might ask for a small feature and receive:</p><ul><li>Four new services</li><li>Several helper files</li><li>Another dependency</li><li>Hundreds of lines that were not needed</li></ul><p>The tool never gets tired.</p><p>It does not mind building a complex system for a simple problem.</p><p>A developer still has to look at the result and say:</p><blockquote><em>No. This is far more complicated than it needs to be.</em></blockquote><p>That judgement is part of software development now.</p><h3>Why Vibe Coding Is Great for Starting</h3><p>I enjoy vibe coding most when an idea is still rough.</p><p>Suppose I am thinking about an app that turns spoken thoughts into notes, action items, project plans, and content ideas.</p><p>In the past, I might have spent several days setting up the project before learning whether the main flow was useful.</p><p>Now I can describe the idea, generate a basic interface, connect a temporary backend, and test the experience much sooner.</p><p>I can try different versions.</p><p>I can remove weak ideas before becoming attached to them.</p><p>I can discover that a feature looks useful in my head but feels pointless when I actually use it.</p><p>This is where AI-assisted software development is genuinely helpful.</p><p>It reduces the cost of trying.</p><blockquote><strong><em>Vibe coding helps me answer, “Could this idea work?” It does not automatically answer, “Will this system remain reliable?”</em></strong></blockquote><h3>Vibe Coding Changes When Real Users Arrive</h3><p>A personal prototype can survive a few strange bugs.</p><p>A real product cannot.</p><p>Once users depend on the software, the work changes.</p><p>You have to check authentication.</p><p>You have to protect private data.</p><p>You have to validate user input.</p><p>You have to think about failed payments, permissions, database migrations, backups, abuse, and recovery.</p><p>The software does not become safe just because the generated code looks clean.</p><p>AI makes software development more accessible.</p><p>It does not automatically give everyone the experience needed to recognise weak, unsafe, or fragile code.</p><p>My personal rule is simple:</p><blockquote><strong><em>I can start on vibes. I cannot ship on vibes.</em></strong></blockquote><p>Before releasing something, I still need to understand the important parts of the system.</p><p>I review the changes.</p><p>I test the difficult cases.</p><p>I check what happens when the network fails.</p><p>I check what happens when the input is wrong.</p><p>I check whether the tool replaced working code simply because it preferred a different approach.</p><p>The AI coding tool can help with all of this.</p><p>But it cannot take responsibility for the final result.</p><p>That responsibility remains with me.</p><h3>AI Coding Tools Are Becoming Coding Agents</h3><p>The first AI coding assistants mainly completed lines inside an editor.</p><p>You wrote part of a function, and the tool suggested what came next.</p><p>That already feels old.</p><p>Modern AI coding tools are becoming coding agents.</p><p>They can:</p><ul><li>Inspect an existing codebase</li><li>Edit multiple files</li><li>Run terminal commands</li><li>Write and execute tests</li><li>Review their own changes</li><li>Prepare pull requests</li><li>Work on several tasks at the same time</li></ul><p>Companies such as OpenAI, Anthropic, Google, GitHub, Microsoft, Cursor, and others are competing to control more of the software development workflow.</p><p>The competition is no longer only about who provides the best autocomplete.</p><p>It is about who can manage the complete journey from an idea to working code.</p><p>The editor.</p><p>The terminal.</p><p>The issue tracker.</p><p>The tests.</p><p>The review process.</p><p>The deployment.</p><p>The winning AI coding tool may not be the one that writes the most code.</p><p>It may be the one that understands the project, follows its rules, remembers previous decisions, and knows when it should stop and ask for help.</p><h3>The Developer’s Job Is Moving Up One Level</h3><p>Traditional coding often started with this question:</p><blockquote><em>How do I write this?</em></blockquote><p>AI-assisted software development starts with different questions:</p><blockquote><em>What exactly should happen?</em></blockquote><blockquote><em>What should never happen?</em></blockquote><blockquote><em>What information does the coding agent need?</em></blockquote><blockquote><em>How can I prove that the result is correct?</em></blockquote><blockquote><em>What could break after the next update?</em></blockquote><p>This changes what makes someone effective at building software.</p><p>Programming knowledge still matters.</p><p>It helps you notice:</p><ul><li>Weak security</li><li>Unnecessary complexity</li><li>Slow code</li><li>Missing checks</li><li>Incorrect assumptions</li><li>Confident nonsense</li></ul><p>But other skills are becoming more important.</p><p>Clear thinking.</p><p>Product judgement.</p><p>Writing useful requirements.</p><p>Breaking large tasks into smaller parts.</p><p>Testing unusual cases.</p><p>Knowing when a solution is good enough.</p><p>Knowing when to delete code.</p><p>AI can generate five versions of a feature.</p><p>It cannot always tell which one belongs in the product.</p><p>It can add everything you request.</p><p>It cannot always tell you that the product would be better without half of it.</p><p>It can create working code.</p><p>It cannot decide whether the software is worth building.</p><h3>Traditional Coding Is Not Disappearing</h3><p>Traditional coding and vibe coding are often presented as two opposing sides.</p><p>I do not see them that way.</p><p>The older skills are becoming the safety layer beneath the new workflow.</p><p>Knowing how software works helps me give better instructions.</p><p>It helps me review generated changes.</p><p>It helps me notice when a coding agent has fixed the visible problem while damaging something deeper.</p><p>At the same time, AI coding tools help me explore ideas that I might have ignored because the setup cost was too high.</p><p>An idea no longer needs to wait until I have an empty week.</p><p>I can test its basic shape in an evening.</p><p>I can find the weak parts sooner.</p><p>I can throw away a bad idea without feeling that I wasted a month.</p><h3>What Changed in My Coding Workflow</h3><p>My old workflow looked something like this:</p><ol><li>Understand the feature</li><li>Design the system</li><li>Write the code</li><li>Debug the code</li><li>Test the result</li><li>Release it</li></ol><p>My current workflow looks more like this:</p><ol><li>Understand the user problem</li><li>Explain the existing system</li><li>Define the expected behaviour</li><li>Ask the coding agent for a plan</li><li>Review the plan</li><li>Let it make the first changes</li><li>Test the result</li><li>Inspect the important code</li><li>Remove unnecessary complexity</li><li>Release only after verification</li></ol><p>I am not doing less thinking.</p><p>I am moving the thinking to a different part of the process.</p><h3>My Main Takeaways From Vibe Coding</h3><p>After using AI coding tools regularly, these are the lessons that matter most to me.</p><h3>1. Clear instructions beat clever prompts</h3><p>The coding agent needs context, limits, examples, and expected behaviour. A fancy prompt cannot replace a clear understanding of the problem.</p><h3>2. Small tasks work better than giant requests</h3><p>Asking an agent to rebuild an entire application in one attempt usually creates confusion. Smaller tasks are easier to review and test.</p><h3>3. Working code is not always good code</h3><p>A feature can appear to work while still being insecure, slow, difficult to maintain, or full of hidden problems.</p><h3>4. AI speed can create technical debt faster</h3><p>The quicker you generate code, the quicker you can fill a project with unnecessary layers and dependencies.</p><h3>5. The developer still owns the result</h3><p>The coding tool does not speak to the customer.</p><p>It does not handle the support request.</p><p>It does not lose trust when something breaks.</p><p>You do.</p><h3>The Future of Software Development</h3><p>We are not reaching the end of coding.</p><p>We are reaching the end of coding being only about writing syntax.</p><p>The work is moving towards directing, reviewing, testing, and deciding.</p><p>That is faster.</p><p>It is also strange.</p><p>Some days, using a coding agent feels like working with a talented developer who understands a large project within minutes.</p><p>On other days, it feels like supervising an intern who has made the same mistake four times and is still completely confident.</p><p>So yes, I use vibe coding.</p><p>I use AI coding tools almost every day.</p><p>They help me build faster.</p><p>They help me test more ideas.</p><p>They help me avoid spending hours on repetitive setup work.</p><p>But before anything reaches a real user, I slow down.</p><p>I review the important changes.</p><p>I run the tests.</p><p>I check the difficult cases.</p><p>And I make sure the vibes did not quietly delete something important.</p><blockquote><strong><em>Vibe coding changed how quickly I can build. It did not change who is responsible for what I ship.</em></strong></blockquote><h3>My Final Thoughts</h3><p>AI has changed how I build software, but not who is responsible for the final result.</p><p>It helps me move faster, test ideas, and avoid repetitive work. But I still review, test, and understand what I ship.</p><p><strong>I can start on vibes. I cannot ship on vibes.</strong></p><p>How has AI changed the way you code? Share your experience in the comments.</p><p>If this resonated, do follow me for more honest stories about building with AI. 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1002275d0385" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Fake Real Classes in Pure C (No C++ Required — Just One Simple Trick)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://levelup.gitconnected.com/how-i-fake-real-classes-in-pure-c-no-c-required-just-one-simple-trick-0d9e98b965d2?source=rss-2def82b6e88d------2"><img src="https://cdn-images-1.medium.com/max/2600/0*z111OuW8VUoc17eh" width="3936"></a></p><p class="medium-feed-snippet">Picture this. You&#x2019;re knee-deep in a C project, loving every second of it. The code is fast, it&#x2019;s bare-metal honest, and it never gets in&#x2026;</p><p class="medium-feed-link"><a href="https://levelup.gitconnected.com/how-i-fake-real-classes-in-pure-c-no-c-required-just-one-simple-trick-0d9e98b965d2?source=rss-2def82b6e88d------2">Continue reading on Level Up Coding »</a></p></div>]]></description>
            <link>https://levelup.gitconnected.com/how-i-fake-real-classes-in-pure-c-no-c-required-just-one-simple-trick-0d9e98b965d2?source=rss-2def82b6e88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d9e98b965d2</guid>
            <category><![CDATA[level-up-coding]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[c-programming]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Abhijith Purohit]]></dc:creator>
            <pubDate>Mon, 13 Apr 2026 15:03:22 GMT</pubDate>
            <atom:updated>2026-04-13T15:03:22.778Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[From Grief to Freedom: How I, a 28-Year-Old Engineer from India, Started Building a Life That…]]></title>
            <link>https://medium.com/write-a-catalyst/from-grief-to-freedom-how-i-a-28-year-old-engineer-from-india-started-building-a-life-that-actual-985e62656388?source=rss-2def82b6e88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/985e62656388</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[write-a-catalyst]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Abhijith Purohit]]></dc:creator>
            <pubDate>Tue, 31 Mar 2026 04:16:29 GMT</pubDate>
            <atom:updated>2026-03-31T07:03:59.931Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Grief to Freedom: How I, a 28-Year-Old Engineer from India, Started Building a Life That Actually Feels Like Mine</h3><p>Hi, I am Abhijith. I am a 28-year-old engineer with five and a half years of experience, still living with my parents in Bengaluru, India. A few years ago, my life felt completely frozen. In 2021, during the second wave of COVID in India, my father passed away, and everything I thought I had under control fell apart. Today I am not perfect, but I am moving forward. I am planning my financial independence, I took my first big trip abroad last year, and I have started paying attention to the people I spend time with, the decisions I make, and the daily routines that shape my days.</p><p>This is not a polished success story. It is the real, messy middle part. If you feel stuck right now, no matter your age or job, I wrote this for you. Here is exactly how I began to get unstuck, one uncomfortable step at a time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SEVnhekH9AnZl6Op8KWW1A.jpeg" /><figcaption>Me in Bali :)</figcaption></figure><h3>The Year Everything Stopped</h3><p>In 2021, like millions of others in India, I watched the world shut down again during the devastating second wave of COVID. My father was one of the people we lost. Suddenly I was the only one left to hold things together at home. Work from home became work-plus-everything-else-from-home. I kept showing up for my job, but inside I was running on empty.</p><p>I stayed inside the same four walls, ate the same comfort food, scrolled the same apps, and told myself “this is just a phase.” The phase lasted years. My comfort zone had turned into a cage, and I did not even notice until the cage started feeling normal.</p><p>Looking back, that low point taught me the first real lesson: grief does not announce when it is ready to let you go. You have to decide to start moving while it is still sitting on your chest.</p><h3>The First Tiny Wins That Changed Everything</h3><p>I did not wake up one morning and overhaul my life. I started with things so small they almost felt stupid.</p><p>After work, I began going to the gym in the evening. Nothing fancy at first, just showing up. I use a tracker now, but even before that, the simple act of lifting weights and moving my body after a long day became my anchor. Some days I hated it. Most days it was the only thing that made me feel like I still had some control.</p><p>I also started writing down three things I was grateful for every night. Not the Instagram version. Real ones, like “the project deadline I met today” or “the long call with my college friend who still checks on me.” It sounds cheesy until you realize it slowly rewires what your brain notices.</p><p>These small habits did not fix my grief or my finances, but they proved I could keep promises to myself. That proof became the foundation for everything that came next.</p><blockquote>Showing up for yourself in the evening, even when the whole day has drained you, builds a quiet kind of confidence that no morning routine can match.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pFlioP41_KqVX4IJjNFXHQ.jpeg" /><figcaption>Mt. Batur Peak</figcaption></figure><h3>Bali Was Not a Vacation. It Was a Permission Slip</h3><p>Last year I did something I had never done before. I booked a trip to Bali with three friends. Ten days, no parents, no work laptop, no safety net of routine.</p><p>I was nervous the entire flight. What if something went wrong? What if I wasted money I should have saved? What if I missed my family?</p><p>None of that happened. Instead, I did the famous 130-metre bungee jump for the first time in my life. Then I tried scuba diving even though I did not know how to swim. The rush of free-falling and the silence underwater made me think about my life differently. For the first time in years, I felt light and alive.</p><p>Coming home from Bali was the real test. I could have treated it as a one-off “fun memory” and slipped back into old patterns. Instead I used it as proof: I am capable of choosing discomfort and still being okay. Those two moments in Bali became my reference point whenever fear tries to talk me out of trying something new.</p><blockquote>Sometimes one scary jump or one deep breath underwater is all it takes to remind yourself that you are braver than your daily routine lets you believe.</blockquote><h3>Who You Spend Time With Becomes Your Future</h3><p>After Bali I started looking at my calendar differently. I noticed how certain people left me energized and others left me drained. I began making deliberate choices about who I said yes to.</p><p>I now protect time for the friends who ask good questions and celebrate my small wins. I also started saying no to social plans that felt like obligations. It was awkward at first. It still is sometimes. But my energy levels and decision-making both improved dramatically once I stopped treating my time like it was free for everyone else.</p><p>The same rule applies to the voices in my head. I catch myself when old thoughts like “you are too old to change careers” or “you should stay safe” creep in. I replace them with evidence from my own life: I survived the hardest year of my life, jumped off a 130-metre bridge, and still managed to travel abroad. That evidence is stronger than any fear.</p><h3>Building Routines That Actually Serve Me</h3><p>My days look different now. Evenings are non-negotiable gym time because that is when my energy actually works for me. I have a simple routine that includes reviewing my top three priorities for the day and ten minutes of planning how I will move closer to financial independence.</p><p>I track my expenses honestly every Sunday. I opened a separate savings account for “future me” and started putting a fixed amount in it before I spend on anything else. I am also upskilling in areas that genuinely interest me, not just what looks good on a resume.</p><p>These routines are not about perfection. They are about momentum. On bad days I still follow 70 percent of them because the habit is now stronger than my mood.</p><blockquote>Your best routine is the one that fits your real life, not someone else’s perfect morning. For me, evenings at the gym became the reset button I actually used.</blockquote><h3>The Road to Financial Independence</h3><p>Living with parents after losing my father gave me stability when I needed it most. Now it is time to turn that stability into freedom.</p><p>I sat down and calculated exactly what financial independence looks like for me. Not some influencer number, but my number. I factored in rent, travel, emergencies, and the kind of life I actually want.</p><p>I am not there yet, but I have a clear plan: side projects that could become income streams, consistent investing, and conversations with my family about the transition. Every rupee I save and every skill I learn feels like a vote for the future version of myself who is not stuck.</p><h3>How You Can Start Improving Your Life Today (Using My Story as Proof)</h3><p>If my journey feels familiar, here is how you can borrow the same steps and make them yours:</p><ul><li>Start with one evening habit that recharges you. For me it was the gym after work. Pick something that fits your schedule, not an influencer’s. Show up even when you are tired. That single commitment will quietly change how you see yourself.</li><li>Use one bold experience as your new reference point. You do not need to fly to Bali. Book a local adventure, sign up for a class that scares you, or have that honest conversation you have been avoiding. Feel the discomfort, then let it remind you that you can handle more than you think.</li><li>Audit your circle and your decisions. Spend one week noticing who lifts you up and which choices leave you feeling better or worse. Protect your time like it is your most valuable asset, because it is.</li><li>Build tiny proofs of progress. Track your gym sessions, your savings, or your grateful notes. When doubt hits, open that list. My tracker and my notes app have saved me on more low days than I can count.</li><li>Celebrate the messy middle. Tell a friend about your small win or write it down. You need to hear that you are already doing better than yesterday.</li></ul><h3>My Final Thoughts</h3><p>You do not have to have it all figured out to start moving. I am still 28, still an engineer, still living at home in Bengaluru, and still figuring out the next steps. But I am no longer stuck. I have momentum. I have proof from my own life that I can handle discomfort and come out the other side happier.</p><p>The comfort zone is warm, but it is also where dreams go to wait forever. I am choosing not to wait anymore.</p><p>What is one small evening step you are going to take this week? Drop it in the comments. I read every single one.</p><p>If this story gave you even a little push to get unstuck, do three quick things right now: clap if it resonated, share it with one friend who feels stuck like I once did, and follow me here on Medium for more honest stories, practical routines, and real updates on my journey toward financial independence.😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=985e62656388" width="1" height="1" alt=""><hr><p><a href="https://medium.com/write-a-catalyst/from-grief-to-freedom-how-i-a-28-year-old-engineer-from-india-started-building-a-life-that-actual-985e62656388">From Grief to Freedom: How I, a 28-Year-Old Engineer from India, Started Building a Life That…</a> was originally published in <a href="https://medium.com/write-a-catalyst">Write A Catalyst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Use GDB to Debug a Real C Bug Step by Step]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://levelup.gitconnected.com/how-to-use-gdb-to-debug-a-real-c-bug-step-by-step-86a9cde406a1?source=rss-2def82b6e88d------2"><img src="https://cdn-images-1.medium.com/max/2600/0*VLI2MGkhOUFcJeQe" width="6000"></a></p><p class="medium-feed-snippet">Photo by Hitesh Choudhary on Unsplash</p><p class="medium-feed-link"><a href="https://levelup.gitconnected.com/how-to-use-gdb-to-debug-a-real-c-bug-step-by-step-86a9cde406a1?source=rss-2def82b6e88d------2">Continue reading on Level Up Coding »</a></p></div>]]></description>
            <link>https://levelup.gitconnected.com/how-to-use-gdb-to-debug-a-real-c-bug-step-by-step-86a9cde406a1?source=rss-2def82b6e88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/86a9cde406a1</guid>
            <category><![CDATA[c-programming]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[gdb]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Abhijith Purohit]]></dc:creator>
            <pubDate>Mon, 16 Mar 2026 15:51:28 GMT</pubDate>
            <atom:updated>2026-03-17T04:29:48.149Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Will AI Take Your Job? Relax, Adapt, and Win — a Practical Playbook for Engineers and Teams]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/write-a-catalyst/will-ai-take-your-job-relax-adapt-and-win-a-practical-playbook-for-engineers-and-teams-3bf7f5103e02?source=rss-2def82b6e88d------2"><img src="https://cdn-images-1.medium.com/max/1536/1*RuNw1UukWDa99aIsNDLeEw.png" width="1536"></a></p><p class="medium-feed-snippet">You have three options when something big changes your work. Panic, pretend nothing happened, or learn to use the change to your advantage&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/write-a-catalyst/will-ai-take-your-job-relax-adapt-and-win-a-practical-playbook-for-engineers-and-teams-3bf7f5103e02?source=rss-2def82b6e88d------2">Continue reading on Write A Catalyst »</a></p></div>]]></description>
            <link>https://medium.com/write-a-catalyst/will-ai-take-your-job-relax-adapt-and-win-a-practical-playbook-for-engineers-and-teams-3bf7f5103e02?source=rss-2def82b6e88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bf7f5103e02</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[ai-and-job-security]]></category>
            <category><![CDATA[write-a-catalyst]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Abhijith Purohit]]></dc:creator>
            <pubDate>Sat, 07 Feb 2026 17:26:15 GMT</pubDate>
            <atom:updated>2026-02-07T17:26:15.015Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Understanding the Liskov Substitution Principle: The Backbone of SOLID Design]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://abhijithpurohit.medium.com/understanding-the-liskov-substitution-principle-the-backbone-of-solid-design-5f58f0f2a288?source=rss-2def82b6e88d------2"><img src="https://cdn-images-1.medium.com/max/1248/1*57XWYNxALDXTCELxdwpYlg.png" width="1248"></a></p><p class="medium-feed-snippet">In the world of object-oriented programming (OOP), designing robust and maintainable software is an art as much as a science.</p><p class="medium-feed-link"><a href="https://abhijithpurohit.medium.com/understanding-the-liskov-substitution-principle-the-backbone-of-solid-design-5f58f0f2a288?source=rss-2def82b6e88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://abhijithpurohit.medium.com/understanding-the-liskov-substitution-principle-the-backbone-of-solid-design-5f58f0f2a288?source=rss-2def82b6e88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f58f0f2a288</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[solid-principles]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Abhijith Purohit]]></dc:creator>
            <pubDate>Tue, 18 Nov 2025 18:27:14 GMT</pubDate>
            <atom:updated>2025-11-18T18:27:14.134Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Craft Flexible Code with the Open/Closed Principle]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://abhijithpurohit.medium.com/craft-flexible-code-with-the-open-closed-principle-6086592b0df5?source=rss-2def82b6e88d------2"><img src="https://cdn-images-1.medium.com/max/768/1*xDh81MpfnMNVchVP4q7wsA.jpeg" width="768"></a></p><p class="medium-feed-snippet">Ever dreamed of writing code that grows without breaking? Code that welcomes new features like a friendly host, without needing a complete&#x2026;</p><p class="medium-feed-link"><a href="https://abhijithpurohit.medium.com/craft-flexible-code-with-the-open-closed-principle-6086592b0df5?source=rss-2def82b6e88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://abhijithpurohit.medium.com/craft-flexible-code-with-the-open-closed-principle-6086592b0df5?source=rss-2def82b6e88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6086592b0df5</guid>
            <category><![CDATA[solid-principles]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[clean-code]]></category>
            <dc:creator><![CDATA[Abhijith Purohit]]></dc:creator>
            <pubDate>Fri, 25 Jul 2025 14:32:51 GMT</pubDate>
            <atom:updated>2025-07-25T14:32:51.549Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[What’s Telematics? Your Guide to Connected Vehicles and IoT]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://abhijithpurohit.medium.com/whats-telematics-your-guide-to-connected-vehicles-and-iot-2401952de67e?source=rss-2def82b6e88d------2"><img src="https://cdn-images-1.medium.com/max/2600/0*gJTfbH_8TostcpO9" width="3840"></a></p><p class="medium-feed-snippet">Hey there! I&#x2019;m a developer who loves tinkering with telematics, helping motorcycles chat with the cloud using tools like C++ and embedded&#x2026;</p><p class="medium-feed-link"><a href="https://abhijithpurohit.medium.com/whats-telematics-your-guide-to-connected-vehicles-and-iot-2401952de67e?source=rss-2def82b6e88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://abhijithpurohit.medium.com/whats-telematics-your-guide-to-connected-vehicles-and-iot-2401952de67e?source=rss-2def82b6e88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2401952de67e</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[embedded-systems]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[telematics]]></category>
            <dc:creator><![CDATA[Abhijith Purohit]]></dc:creator>
            <pubDate>Wed, 09 Jul 2025 16:46:49 GMT</pubDate>
            <atom:updated>2025-07-09T16:46:49.430Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Write Better C++ Code with the Single Responsibility Principle]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://abhijithpurohit.medium.com/write-better-c-code-with-the-single-responsibility-principle-080c6d252964?source=rss-2def82b6e88d------2"><img src="https://cdn-images-1.medium.com/max/768/1*plmHA7qEOGAsYP4msdW49w.jpeg" width="768"></a></p><p class="medium-feed-snippet">Writing clean code is a must for any developer who wants their work to shine. It&#x2019;s not just about getting your program to run; it&#x2019;s about&#x2026;</p><p class="medium-feed-link"><a href="https://abhijithpurohit.medium.com/write-better-c-code-with-the-single-responsibility-principle-080c6d252964?source=rss-2def82b6e88d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://abhijithpurohit.medium.com/write-better-c-code-with-the-single-responsibility-principle-080c6d252964?source=rss-2def82b6e88d------2</link>
            <guid isPermaLink="false">https://medium.com/p/080c6d252964</guid>
            <category><![CDATA[coding-tips]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[solid-principles]]></category>
            <dc:creator><![CDATA[Abhijith Purohit]]></dc:creator>
            <pubDate>Sat, 05 Jul 2025 06:07:27 GMT</pubDate>
            <atom:updated>2025-07-05T07:18:43.816Z</atom:updated>
        </item>
    </channel>
</rss>