<?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 Abhigyan Jha on Medium]]></title>
        <description><![CDATA[Stories by Abhigyan Jha on Medium]]></description>
        <link>https://medium.com/@abhigyanjha?source=rss-0c116d3eef9f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GY66GjA9C6sNatenfaRkXg.jpeg</url>
            <title>Stories by Abhigyan Jha on Medium</title>
            <link>https://medium.com/@abhigyanjha?source=rss-0c116d3eef9f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:57:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abhigyanjha/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[Does AI Make Developers Better, or Just More Dependent on It?]]></title>
            <link>https://medium.com/@abhigyanjha/does-ai-make-developers-better-or-just-more-dependent-on-it-a788122c4ecd?source=rss-0c116d3eef9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a788122c4ecd</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Abhigyan Jha]]></dc:creator>
            <pubDate>Sun, 25 Oct 2026 12:27:08 GMT</pubDate>
            <atom:updated>2026-10-25T12:27:08.229Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pjuQ4BWdCRMDN0H1brtTOQ.png" /><figcaption>AI GENERATED</figcaption></figure><p>When I first joined X, I saw people building amazing things in tech. People were creating projects, launching products, and sharing things they had built themselves.<br>Looking at them, I felt like I was way behind.<br>I wanted to build things like them, so instead of taking my time to learn coding properly, I started vibe coding with AI.<br>And honestly, it felt amazing.<br>I could turn my ideas into working projects without knowing everything about the code. Every new project felt like progress. I thought I was learning faster.<br>But after a month, I realized something.<br><strong>I was building projects, but I wasn’t building my skills at the same pace.</strong><br>I was getting things done, but I wasn’t sure how much I could do on my own.<br>That’s when I started thinking: Is AI actually making me a better developer, or just helping me look like one?</p><h3>The Good Side of AI</h3><p>I don’t think AI is the problem. In fact, one of the best things about it is that it lets beginners explore ideas they might not have been able to build on their own yet.<br>Maybe some of the things I’m building today with AI are things I would have been able to build independently one or two years from now.<br>AI gave me a chance to try those ideas earlier.<br>It can explain errors, help us understand unfamiliar code, and make it easier to experiment. For someone who’s just starting, that can make a huge difference.<br>And I don’t want to ignore that just because I’ve experienced its<strong> </strong>downsides<strong>.</strong></p><p><strong>The problem isn’t that AI helps us build faster. The problem is when building faster makes us think we’re learning faster, too.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aBdEuqpYxtFN36Jhb6C5XQ.png" /><figcaption>AI GENERATED</figcaption></figure><h3>When Help Turns Into Dependency</h3><p>Imagine building a project with AI. Everything works, the UI looks good, and you’re excited to share it.<br>Then something breaks.<br>You ask AI to fix it. It gives you another solution, and the project works again.<br>But what if you don’t understand why it broke in the first place?<br>You might have a working project, but the next time you face the same problem, you’ll probably need AI again.<br>That’s the difference between using a tool and depending on it.<br>I’ve realized that finishing a project isn’t the only thing that matters. I also need to understand what I’m building, why it works, and how to fix it when something goes wrong.<br>Otherwise, I might keep building more projects without becoming much better at coding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*qAU1qW7W3bTGna4WxoJW_Q.jpeg" /><figcaption>AI GENERATED</figcaption></figure><h3>What I’m Trying to Do Differently</h3><p>I haven’t stopped using AI, and I don’t think I need to.<br>I’m just trying to change how I use it.<br>Instead of asking AI to do everything, I want to understand the code it gives me. When something breaks, I want to know why before moving on. And sometimes, I want to solve problems myself, even if it takes longer.<br>I know I won’t understand everything immediately. I’m still a beginner, and there’s a lot left to learn.<br><strong>But I’d rather spend extra time understanding one thing than build ten projects without knowing how they actually work.</strong></p><h3>So, Does AI Make Developers Better?</h3><p>I think AI gives us the opportunity to become better developers, but it doesn’t guarantee that we will.<br>We can use it to learn things faster, explore bigger ideas, and improve our skills. Or we can use it to skip the learning process and become comfortable with getting answers without understanding them.<br>Both are possible with the same tool.<br>Looking back, I don’t regret using AI to build projects. It helped me explore things I might not have tried otherwise.<br>I just don’t want to confuse what AI can do for me with what I can do myself.<br><strong>I want AI to help me build things I couldn’t build yesterday, while helping me become someone who can build more of them on my own tomorrow.</strong></p><p>Maybe that’s what becoming a better developer actually looks like.<strong><br>Not avoiding AI. Not depending on it for everything. But learning enough to know when to use it, when to question it, and when to figure things out</strong> <strong>yourself.</strong><br><strong>And that’s the kind of developer I’m trying to become.</strong><br>What about you? Is AI helping you become a better developer, or making it easier to avoid learning the hard parts?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a788122c4ecd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Problem With Trying to Learn Everything at Once]]></title>
            <link>https://medium.com/@abhigyanjha/the-problem-with-trying-to-learn-everything-at-once-ede2af1fdf5d?source=rss-0c116d3eef9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ede2af1fdf5d</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[deep-thoughts]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[iit-jee]]></category>
            <dc:creator><![CDATA[Abhigyan Jha]]></dc:creator>
            <pubDate>Sun, 13 Sep 2026 07:01:58 GMT</pubDate>
            <atom:updated>2026-09-13T07:01:58.616Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>— Lessons from a JEE drop year on managing focus, coding, writing, and the trap of endless side quests.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EJ8RDh1ogUzYoP9ZMn_-LQ.jpeg" /></figure><p>There was a time when I thought learning more things meant I was moving forward faster.</p><p><strong>JEE preparation.<br>Coding.<br>Writing.<br>Building projects.<br>Reading.<br>Learning about AI.<br>Posting on X.<br>Making genuine connections.</strong></p><p>And somehow, I wanted to do all of it at the same time.</p><p>I am currently in my JEE drop year, so technically my main job should be pretty simple: prepare for JEE.<br>But my brain doesn’t really work that way.<br>I started writing when I was in Class 8. Back then, I wasn’t thinking about becoming a writer or publishing on Medium. I just liked writing things. Sometimes they were good. Sometimes they were probably terrible.<br>I wrote anyway.<br>Then came coding.<br>Now I want to learn Python, understand web development, build projects, explore AI, and eventually figure out where I fit in the tech world.<br>At the same time, I want to keep writing, stay active on X, meet new people and build some genuine connections for my future.<br>So here I am, trying to figure out JEE, coding, writing, the internet, and my future all at once.</p><p><strong>Sounds productive, right?</strong></p><p>Sometimes it is.<br>Sometimes it is just <strong>chaos with a productivity filter on top.</strong></p><h3>The illusion of progress</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ISwcHL-E59zbHTABhit5Fw.png" /></figure><p>One of the biggest problems with trying to learn everything at once is that it feels like progress.<br>You watch a Python tutorial.<br>Read something about AI.<br>Save a post about web development.<br>Write some code.<br>Study Physics for two hours.<br>Have a few conversations on X.<br>At the end of the day, you feel like you did a lot.<br>Then you ask yourself:<br><strong>What did I actually get better at?</strong><br>Sometimes the answer is uncomfortable.<br><strong>Not much.</strong></p><p>The problem isn’t having different interests.<br>The problem is constantly switching between them without giving any of them enough time to become a real skill.<br>There is a difference between being exposed to something and actually learning it.<br>I have definitely confused the two.</p><h3>The more I learn, the more I want to learn</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PYLiDZXmN2cy4fxXoWZAFw.png" /></figure><p>This is probably where most of my trouble starts.<br>Whenever I learn something interesting, I immediately find five other things connected to it.<br>I started learning coding.<br>Then I wanted to understand web development.<br>Then AI.<br>Then backend.<br>Then DSA.<br>Then I saw someone building something completely different and thought,<br><strong>Wait, I should learn that too.</strong></p><p>The internet makes this incredibly easy.<br>You can go from a Python tutorial to a machine learning course to a startup thread to someone’s LeetCode journey in about fifteen minutes.<br>And suddenly your simple learning plan has become a list of seventeen things.<br><strong>None of them are finished.</strong></p><p>I’ve done the same thing with writing.<br>I wanted to write better.<br>Then I started reading about storytelling.<br>Then personal branding.<br>Then Medium.<br>Then X.<br>Then networking.<br>There is always something else to learn.<br>And that’s where curiosity can quietly turn into distraction.</p><h3>Being interested in everything isn’t the problem</h3><p>I don’t think curiosity is a bad thing.<br>Actually, it is one of the reasons I enjoy learning in the first place.<br>When JEE gets exhausting, coding gives me something different to think about.<br>When coding gets frustrating, writing gives me a way to slow down and put my thoughts somewhere.<br>And when I spend too much time studying alone, talking to people online reminds me that there is a world outside my room.<br>These things genuinely matter to me.<br>I don’t want to become someone who only knows how to prepare for an exam.<br>But I also don’t want to become someone who knows a little about everything and never becomes good at anything.<br><strong>That’s the line I’m still trying to figure out.</strong></p><h3>My JEE drop year made this even harder</h3><p>A drop year comes with its own kind of pressure.<br>There is always another chapter waiting.<br>Another question to solve.<br>Another test to give.<br>Another mistake to analyse.<br>Another formula you somehow forgot.<br>And at the same time, I don’t want my entire year to become just JEE.<br>I don’t want to wake up after the exam and feel like I spent an entire year doing nothing except preparing for one result.<br>Maybe that’s why I keep coming back to writing and coding.<br>They give me a different kind of progress.<br>In JEE, progress can sometimes feel invisible.<br>You can study for hours and still get a question wrong.<br>With coding, I can start with a blank screen and end with something that actually works.<br>With writing, I can take a thought that has been sitting in my head and turn it into something another person can read.<br><strong>That feeling matters to me.</strong><br>But I’ve also learned that keeping these things alive doesn’t mean I have to make all of them equally important.</p><h3>Everything doesn’t need the same amount of attention</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l5t2CwzW8Nl2KQUOf20yhA.png" /></figure><p>For a long time, I thought my problem was time management.<br>Maybe I needed a better timetable.<br>Maybe I needed to wake up earlier.<br>Maybe I needed a better productivity app.<br>Maybe I needed to plan every hour of my day.<br>Eventually, I realised it wasn’t always a time problem.<br><strong>It was an attention problem.</strong></p><p>There are only so many things I can genuinely focus on.<br>JEE can be a priority without me giving up writing.<br>Writing can matter without me publishing every day.<br>Coding can stay in my life without me trying to become a developer overnight.<br>And making connections can happen slowly without turning networking into another task on my checklist.<br><strong>Everything doesn’t need the same amount of attention.</strong></p><p>That’s something I’m slowly learning.</p><h3>The internet makes everyone look ahead of you</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VhBHWFi1bk4Ncg3Vun4-xw.png" /></figure><p>This might be the hardest part.<br>You open X and see an 18-year-old building an AI startup.<br>Someone else is solving hundreds of DSA problems.<br>Someone has an internship.<br>Someone is writing their tenth article.<br>Someone has thousands of followers.<br>Someone is already making money from something they built.<br>And suddenly, your own progress looks insignificant.<br>So you add another goal.<br>Then another.<br>Not necessarily because you need it, but because someone else is already doing it.<br>I’ve caught myself doing this more times than I’d like to admit.<br>The internet is great for finding people who inspire you.<br>But if you’re not careful, the same people can make you feel like you’re constantly behind.<br><strong>Someone else’s timeline isn’t a deadline for me.</strong></p><p>I’m still learning.<br>I’m still figuring things out.<br>And honestly, I think that’s okay.</p><h3>I don’t want to become good at everything</h3><p>I think this is where I’m slowly changing my mindset.<br><strong>I don’t actually want to know everything.</strong><br>I want to become really good at a few things that genuinely matter to me.<br>I want to keep writing because I’ve loved it since Class 8.<br>I want to learn coding because I enjoy building things.<br>I want to give JEE my honest effort because I chose this drop year for a reason.<br>And I want to meet good people along the way because the future isn’t built completely alone.<br><strong>That’s enough.</strong></p><p>I don’t need to learn every programming language.<br>I don’t need to understand every new AI tool.<br>I don’t need to publish every day.<br>I don’t need to know exactly what my career will look like five years from now.<br><strong>I just need to keep moving.</strong></p><h3>I’m trying to build slowly</h3><p>My goal with writing is pretty simple right now:<br><strong>One article a week.</strong><br>Not because every article will be amazing.<br>Some will probably be awkward.<br>Some ideas will be better than others.<br>But if I keep writing, I’ll eventually have enough work to look back at and see how much I’ve changed.<br>The same goes for coding.<br><strong>One concept.<br>One project.<br>One bug.<br>One small improvement.</strong></p><p>That’s how skills are built anyway.<br>Not through one huge transformation.<br>Mostly through small repetitions that don’t feel important while you’re doing them.<br>And maybe that’s the part I was missing.<br><strong>I don’t need to do everything every day.</strong></p><p>I just need to keep the things that matter to me alive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tb7FnVkPugL5mxFUWC1O6g.png" /></figure><h3>I’m still figuring it out</h3><p>I don’t have some magical productivity system.<br>I’m still a student trying to figure out what I want.<br>I’m still preparing for JEE.<br>I’m still learning how to code.<br>I’m still learning how to write better.<br>I’m still learning how to approach new people and make genuine connections.<br>And I’m still figuring out what kind of person I want to become.<br>I still get distracted.<br>I still make ridiculously long lists of things I want to learn.<br>I still see someone building something cool and immediately think,<br><strong>I should learn that.</strong></p><p>Maybe that isn’t going away anytime soon.<br>But I’m learning to pause before turning every interest into another commitment.<br>Because there is a difference between:<br><strong>“That’s interesting. I want to learn it someday.”</strong><br>and<br><strong>“I need to learn it right now.”</strong></p><p>I don’t need everything right now.<br>Some things can wait.<br>Some things can stay as side quests.<br>Some things can grow quietly in the background.<br>And some things might never happen.<br><strong>That’s not failure.</strong></p><p>That’s just choosing.<br>I’m still a JEE dropper.<br>Still learning to code.<br>Still writing.<br>Still trying to meet people and build something meaningful for the future.<br>I don’t know exactly where all of this will take me.<br>But maybe I don’t need to know yet.<br><strong>Maybe I just need to stop trying to become five different people at once.</strong></p><h3>One thing at a time.</h3><p>That’s probably enough for now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ede2af1fdf5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Took a Drop Year for JEE. Here’s What Failure Actually Taught Me]]></title>
            <link>https://medium.com/@abhigyanjha/i-took-a-drop-year-for-jee-heres-what-failure-actually-taught-me-5507d9c6aeed?source=rss-0c116d3eef9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5507d9c6aeed</guid>
            <category><![CDATA[jee-mains]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[Abhigyan Jha]]></dc:creator>
            <pubDate>Sun, 30 Aug 2026 13:11:47 GMT</pubDate>
            <atom:updated>2026-08-30T13:32:06.220Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>I’m not an expert. I’m just a dropper documenting my journey with exams, coding, and growth.</strong></p><p>When you decide to take a drop year for JEE, everyone gives you the same advice: &quot;Work harder, follow the schedule, and stay motivated.&quot; Self-help books tell you that failure is just a stepping stone to success. Teachers tell you that consistency is key.</p><p><strong>It<em> </em>all sounds great on paper. But paper doesn’t prepare you for the quiet pressure of a drop year.</strong></p><p>I used to think seniors were trying to scare us when they said: <strong>&quot;Padh lo... warna drop lena padega.&quot;</strong></p><p>Now I get it. It’s not just about one more year of studying physics formulas or organic chemistry mechanisms. It’s watching your friends start college, move into dorms, and post about their new lives while you’re sitting in the same room, repeating the exact same chapters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6BEpGFPQzB0K4ySr9RcFCQ.jpeg" /></figure><p><strong>Being a year behind the people you started with hurts the most.</strong> No textbook prepares you for that quiet psychological toll.</p><h3>1. Failure Isn’t a Verdict; It’s Just Feedback</h3><p>Before taking a gap year, I thought failure meant seeing a bad score on a report card.<br>Now, I realize failure happens in small, quiet moments throughout the day. It happens when a mock test score drops by twenty marks, or when an organic chemistry mechanism makes zero sense after two hours of trying.<br>In movies, failure is portrayed as a dramatic plot point where the hero turns everything around in a montage. In real life, <strong>there is no background music.</strong> You just have to look at the wrong options you marked, figure out why you marked them, and fix it.<br><strong>Failure isn’t a statement about your intelligence.</strong> It’s just feedback telling you what to adjust next. Whenever I feel like slipping, I remind myself why I chose this drop year in the first place I don’t want to waste the opportunity I’ve been given.</p><h3>2. Systems Beat Motivation Every Time</h3><p>Self-help books love to preach about passion and drive. But passion doesn’t keep you focused on a random Tuesday afternoon when you’re exhausted and the exam date is creeping closer.</p><p>What actually works is building a simple, repeatable system:</p><p><strong>Track inputs, not outputs:</strong> I focus on completing 40 solid practice problems today rather than stressing over a rank that is months away.<br><strong>Normalize bad days:</strong> Some days you operate at 100%, and some days at 40%. The goal is to make sure the 40% days still happen instead of turning into 0% days.<br><strong>Keep an outlet:</strong> For me, it’s writing code and watching an episode of anime at night. Do not strip away everything that makes you human just to clear an exam.</p><h3>3. What Coding Taught Me About Prep</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*MZR91pNE1h6j29ft4Sg47g.jpeg" /></figure><p>When you write code, errors are normal. You write twenty lines, run the program, and get a SyntaxError. You don’t sit there questioning your entire life purpose because a bracket was missing. You debug it. You search for the fix, apply it, and test it again.</p><p>I started applying that developer mindset to my prep. Got a question wrong in Physics? Don’t spiral debug it. Was it a calculation error, a conceptual gap, or poor time management? Fix the bug and move on.</p><h3>4. Learning While Still in the Process</h3><p>I don’t know yet how this drop year will end. I’m not sitting here as a top ranker giving a victory speech. I am still in the trenches, solving problems, making mistakes, and adjusting my routine every day.</p><p>Even if things don’t go as planned, this year has taught me two things that will stay with me forever:</p><p><strong>Routine matters more than natural talent:</strong> Staying disciplined on days when you feel low builds far more strength than relying on sudden bursts of talent.<br><strong>Do the work today to avoid regret tomorrow: </strong>You eventually have to do the hard work anyway. Putting it off only makes it harder and more painful down the road.</p><p>I chose to write on Medium not to pretend to be an expert, but to document the process as it happens. If you are also in a gap year, learning to code, or simply trying to bounce back from a setback know that you aren’t the only one figuring it out as you go.<br>Failure only gets the final say if you stop debugging. Until then, it’s just part of the code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5507d9c6aeed" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>