<?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 Jayashree Joraram Kesharam on Medium]]></title>
        <description><![CDATA[Stories by Jayashree Joraram Kesharam on Medium]]></description>
        <link>https://medium.com/@jayashree.jorar?source=rss-d51a8bf0498a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Jayashree Joraram Kesharam on Medium</title>
            <link>https://medium.com/@jayashree.jorar?source=rss-d51a8bf0498a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:53:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jayashree.jorar/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[Returning to Work: How AI Saved My Work-Life Balance]]></title>
            <link>https://medium.com/@jayashree.jorar/returning-to-work-how-ai-saved-my-work-life-balance-63b1aa7f4e47?source=rss-d51a8bf0498a------2</link>
            <guid isPermaLink="false">https://medium.com/p/63b1aa7f4e47</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[worklife-balance]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Jayashree Joraram Kesharam]]></dc:creator>
            <pubDate>Thu, 27 Aug 2026 07:47:20 GMT</pubDate>
            <atom:updated>2026-08-27T07:47:20.983Z</atom:updated>
            <content:encoded><![CDATA[<p>Going back to a corporate job after my maternity leave was overwhelming. Honestly, I wasn’t even worried about getting back up to speed or finding my groove. My real nightmare? The tech. While I was away, the industry hadn’t just changed, it had accelerated at breakneck speed. AI was everywhere. It felt like everyone around me was speaking some weird, futuristic language, and I was completely left behind.</p><p>It genuinely felt like waking up inside a bad dream.</p><p><strong>My First Attempts Were a Mess</strong></p><p><em>Let’s be real:</em> my first shot at using AI was a total disaster. I’d watched people use ChatGPT for everything — generating cool images, pulling fast answers, you name it. I figured, <em>hey, how hard can it be? I’ll catch on in a few days.</em></p><p>Wrong.</p><p>In the beginning, using ChatGPT was just exhausting. I’d type a prompt. The answer would come back sort of close, but not really what I wanted. So I’d tweak the words, try again, and get another weird result. Just a never-ending loop. It took way more patience than I had. More than once, I sat there thinking, <em>maybe my brain just isn’t wired for this.</em></p><p><strong>The Real Turnaround</strong></p><p>I didn’t fix this overnight by downloading a magic app. It took a ton of annoying trial and error. I’d botch a prompt, change a few words, fail again, and slowly start to spot what worked. I ended up watching basic YouTube tutorials just to understand how these tools think.</p><p>The real game-changer was shifting my own mindset. I stopped expecting the AI to read my mind on the first try. I started small. I gave it tiny, basic tasks before moving on to the heavy stuff. Just being okay with messing up mattered way more than the software itself.</p><p>Once I figured out how to actually talk to the machine, moving over to GitHub Copilot inside VS Code was a turning point. Finally, I could use my prompting skills right inside my actual code editor. No more constant window-switching. The tutorials gave me the logic, but the integration is what actually made me fast — and that’s when the time savings really started to show.</p><p><strong>Saving Hours, Stealing Back Moments</strong></p><p>Before AI, debugging code was a total black hole. It would easily eat up an entire afternoon. I’d get completely trapped in a loop of searching old forums like Stack Overflow, testing fixes, and getting nowhere. My productivity was basically zero.</p><p>Now? Copilot handles a lot of the detective work. I give it the direction and context, and together we fix the bug in a few minutes instead of hours. Developing a brand-new screen used to take me four or five solid hours with all the integrations. Now it takes maybe 30 or 45 minutes. Tops.</p><p>Every single hour I win back goes straight to my daughter. Those saved minutes mean reading books together, playing, and actually being there for the little things. The quick, fleeting parts of her day that I would’ve completely missed if I were stuck staring at a monitor.</p><p>Look, a tiny part of me feels a bit weird about it. The AI handles a significant share of the heavy lifting these days, as long as I set it up with the right context. But honestly? I feel proud. I had to learn how to prompt like a pro to get these results. That growth feels real, even if the tech speeds up the finish line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M1wOS7e7eWrKR124q2BvNw.png" /></figure><p><strong>Like Having an Intern</strong></p><p>At some point, things just clicked. I stopped treating AI like a search engine and started treating it like a smart intern. Someone who already knows my process and can take over entire workflows.</p><p>Take those hectic weeks when I’m balancing three different projects with tight deadlines. Instead of spending half a day trying to make sense of messy client requirements, I hand them over to the AI, which helps me organize the chaos in minutes. Then I can build accurate prototypes fast and walk into client demos feeling confident.</p><p>The same delegation works just as well on my calendar. Once I give it context on my workload and priorities, it helps me map out a realistic day — something the standard productivity blogs never managed, since those tips were built for someone else’s life, not mine.</p><p>I know exactly which days are going to be brutal and which ones are lighter, so I can schedule my heavy work hours and childcare around each other instead of guessing. It even helps me plan quiet activities for my daughter during my longest meetings so I can get through them without a single meltdown.</p><p><strong>The Real Win</strong></p><p>The time I save doesn’t just get filled with more work. I give it all to my family. Those are the exact moments I was terrified of losing when I decided to go back to work.</p><p>What I thought would be a total nightmare — falling behind, struggling to keep up, and feeling like an outsider in the tech world — actually became the exact thing that saved my work-life balance.</p><p><strong>To Anyone Making a Comeback</strong></p><p>If you’re heading back to work after a long break and you’re terrified of the whole AI revolution, I completely get it. I was right there.</p><p>But you don’t need to be an expert on day one. Just take that very first step. Be completely fine with making mistakes. Start with small tasks and scale up. Use these tools to back you up instead of letting fear keep you stuck.</p><p><em>Your career after a break doesn’t have to be scary. It just comes down to how you choose to look at it, plan for it, and use what’s right in front of you.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63b1aa7f4e47" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>