<?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 Script on Medium]]></title>
        <description><![CDATA[Stories by Script on Medium]]></description>
        <link>https://medium.com/@idscript?source=rss-25880806f120------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Lykrr1uG46uqkZzFbNECRg.jpeg</url>
            <title>Stories by Script on Medium</title>
            <link>https://medium.com/@idscript?source=rss-25880806f120------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:29:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@idscript/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[The React Bug That Annoyed Me More Than It Should Have]]></title>
            <link>https://idscript.medium.com/the-react-bug-that-annoyed-me-more-than-it-should-have-2b9cfa3dcf73?source=rss-25880806f120------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b9cfa3dcf73</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[frontend-development]]></category>
            <dc:creator><![CDATA[Script]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 11:02:59 GMT</pubDate>
            <atom:updated>2026-04-07T11:02:59.631Z</atom:updated>
            <content:encoded><![CDATA[<p>I really thought this bug was going to be a quick one. In my head, it was one of those small issues you spot, fix, and laugh about ten minutes later. Instead, it stayed with me for days and irritated me far more than I would like to admit. At some point, it stopped being just a bug and started feeling personal.</p><p>It started with a CORS error, and because the backend guy had already allowed my localhost, I kept expecting the problem to disappear after the next retry. Every time it showed up again, I became more convinced that something was still wrong on the backend. That assumption became my whole investigation process, which meant I kept looking in the same place over and over again. I was reading the error, but I was also reading it with bias.</p><p>The funny thing is that when an error looks familiar, your brain becomes lazy very quickly. Mine had already decided that CORS meant backend, so I kept treating that conclusion like fact instead of checking every part of the setup properly. I was frustrated, slightly dramatic, and very confident for no good reason. Meanwhile, the actual issue was quietly sitting on my side, waiting for me to stop blaming everyone else.</p><p>What was actually wrong was that I needed to do some Vite configuration to allow the API POST request. That was the part I had completely missed, and once I fixed it, everything started working. I just sat there looking at my screen, half relieved and half annoyed that the answer had been that simple. Days of stress, and the problem was me the whole time.</p><p>I think that bug annoyed me so much because it exposed how quickly assumption can turn into stubbornness. I had spent so much time being sure of where the issue lived that I was no longer investigating properly. The error may have been real, but the story I built around it was wrong. That experience reminded me that debugging gets harder the moment your ego joins the session.</p><p>These days, I try to slow down earlier and question my first conclusion before I marry it. When something breaks, I want to ask myself what I have actually confirmed, what I am only assuming, and which part of the setup I have conveniently ignored because it feels less likely. Bugs like this are annoying, but they are also very good at exposing weak spots in the way you think. Mine definitely did.</p><p>What bug humbled you recently?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b9cfa3dcf73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who I’m Becoming]]></title>
            <link>https://idscript.medium.com/who-im-becoming-8bae8ab7dc8c?source=rss-25880806f120------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bae8ab7dc8c</guid>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[finding-yourself]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Script]]></dc:creator>
            <pubDate>Wed, 01 Apr 2026 13:47:13 GMT</pubDate>
            <atom:updated>2026-04-01T13:47:13.163Z</atom:updated>
            <content:encoded><![CDATA[<h3>I like building things people don’t have to struggle with.</h3><p>That honestly, is the easiest way to explain what I care about, because nothing irritates me faster than an app that behaves like it has personal issues with the user. <em>Maybe that is why frontend feels so personal to me.</em></p><p>I got into tech in 2021 without some big inspiring backstory. I had no plan and no mentor. It was really just me, my laptop, internet, and curiosity doing what curiosity does.</p><p>Somehow I got my first job as a UI/UX designer at 16, which still feels funny to say because what exactly was I doing in a workplace at 16.</p><p>I was young, curious, and very aware that I was surrounded by people who seemed far more experienced than I was, so I paid attention. I think that was the year I started noticing how small things can completely change how something feels. Bad spacing can make a screen feel tense. A strange button placement can make somebody pause longer than they should. A color choice can quietly make something feel cringe, confusing, or harder than it needs to be. Those details look tiny until they start affecting real people.</p><p>And the thing is, when people are struggling to use a product, they usually don’t blame the product first. They blame themselves. They think maybe they missed something obvious. Maybe they are not understanding it properly. I have always hated that. I hate when the design is the one causing the stress, but the user is the one left feeling silly. Good design should make people feel guided, not tested.</p><p>I later moved into web development, and React.js honestly changed the way I think. It made building feel more alive and showed me how one thing could be reused in different ways without losing its purpose. It stopped being just about how something looked and became about how it behaved, how it responded, and how it carried someone from one moment to the next without friction.</p><p>Then React Native made it even more personal.</p><p>Because mobile is intimate. You are building for someone’s hand, someone’s pocket, someone checking their phone when they are tired, distracted, outside, half-awake, or already in a bad mood. That changes everything. It makes every decision feel more human, because now you are not just designing for attention, you are designing for real life.</p><p>Somewhere in between UI/UX, React.js, and React Native, I started writing too. And weirdly, writing made me better at building. Both ask the same thing from me: take something in your head, make it clear, and make somebody else feel comfortable inside it.</p><p>That’s probably the best way I can describe what I care about now. Ease.</p><p>I love products that feel natural from the first tap and help people do what they came to do without confusion, tension, or unnecessary drama. An experience that does not make you stop and think too hard about where to go next, because everything already feels like it is where it should be.</p><p>That is why frontend feels human to me.</p><p>It’s the part people actually touch. The part they see, feel, and judge instantly. The part that can either make someone relax or make them want to throw their phone on the bed and hiss. I care a lot about building the first kind.</p><p>I’m still learning. Still growing. Still the kind of person who notices hover states, loading screens, awkward flows, and buttons that feel emotionally unavailable. But I know what I’m becoming.</p><p>I’m becoming the kind of builder who wants products to feel easy, soft, clear, and considered. Not just “but it works”, but a product that feels like it understands you a little.</p><p>Still becoming.</p><p>So, what have you noticed makes an app instantly feel easy to use?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bae8ab7dc8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It Wasn’t a Runaway Groom. It was a woman who never told her father the wedding was off]]></title>
            <link>https://idscript.medium.com/it-wasnt-a-runaway-groom-it-was-a-woman-who-never-told-her-father-the-wedding-was-off-d92e6d599e0c?source=rss-25880806f120------2</link>
            <guid isPermaLink="false">https://medium.com/p/d92e6d599e0c</guid>
            <category><![CDATA[marriage]]></category>
            <category><![CDATA[sex]]></category>
            <category><![CDATA[relationships]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[short-story]]></category>
            <dc:creator><![CDATA[Script]]></dc:creator>
            <pubDate>Sat, 06 Sep 2025 22:02:09 GMT</pubDate>
            <atom:updated>2025-09-06T22:02:09.922Z</atom:updated>
            <content:encoded><![CDATA[<p>...till today, the man still calls, planning a marriage that no longer exists.</p><p>What happened?</p><p>Adam was engaged to Eve. At first she looked calm and polite. But soon the truth showed. She didn’t cook. She didn’t clean. She didn’t work. She barely spoke, and when she did, her words cut like knife.</p><p>Adam got tired. He told her it was over. “Tell your father,” he said. “The wedding is cancelled.”</p><p>That was when Eve dropped the bomb. She said she was pregnant.</p><p>Adam denied it. He swore he never slept with her. Only foreplay. The timing made no sense. Still, Eve refused to bend.</p><p>Nine months of uncertainty. Suspicion everywhere. Then the baby came.</p><p>DNA confirmed it. Adam was the father.</p><p>He agreed to pay monthly child support. He has also said once the child is weaned, he will take custody.</p><p>But Eve never told her father. The old man still calls, still plans, still believes there is a wedding.</p><p>Meanwhile, Adam has moved on. He is with another woman now. Older. Steady. He says they will marry next year.</p><p>So no, it was not a runaway groom.<br>It was a bride who could not face her own father.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d92e6d599e0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>