<?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 Radha Kotecha on Medium]]></title>
        <description><![CDATA[Stories by Radha Kotecha on Medium]]></description>
        <link>https://medium.com/@radhakotecha?source=rss-88f2e06d8c4b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*IMVO3_JopPA38bir.jpg</url>
            <title>Stories by Radha Kotecha on Medium</title>
            <link>https://medium.com/@radhakotecha?source=rss-88f2e06d8c4b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:31:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@radhakotecha/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[What Happened to the Global Village We Built?]]></title>
            <link>https://medium.com/@radhakotecha/what-happened-to-the-global-village-we-built-a2b8ffd8f540?source=rss-88f2e06d8c4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2b8ffd8f540</guid>
            <category><![CDATA[double-standard]]></category>
            <category><![CDATA[geopolitics]]></category>
            <category><![CDATA[discord]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[cross-cultural]]></category>
            <dc:creator><![CDATA[Radha Kotecha]]></dc:creator>
            <pubDate>Mon, 12 May 2025 09:10:55 GMT</pubDate>
            <atom:updated>2025-05-12T12:11:31.688Z</atom:updated>
            <content:encoded><![CDATA[<p>During the isolating days of the COVID-19 pandemic, I found connection and comfort in an unexpected place — a Discord server. It was a space filled with people from all corners of the world. We laughed, played games, shared stories, and built friendships that felt genuine and rare. Some of those friends were from neighboring nations and Muslim-majority countries, and despite our different cultures and nationalities, we found common ground. We respected each other, learned from one another, and celebrated our differences. It truly felt like a mini global village.</p><p>But that ideal was tested — if not shattered — on May 7th.</p><p>Following India’s military retaliation for the Pahalgam attack, emotions ran high. I was deeply affected by the events, but I also hoped our little community could remain a place for understanding rather than hostility. Unfortunately, what followed was a painful unraveling of the bonds we had built.</p><p>The reactions from friends across the border were understandably intense — political events closely tied to national identity often stir deep emotions. However, the shift in tone was abrupt and, in many ways, felt unfair. What could have been thoughtful conversations quickly devolved into accusations. A one-sided narrative began to take hold, with India being portrayed in broad, reductive terms. Some even drew parallels between India and Israel, casting it as an emerging aggressor without acknowledging the complexity of the situation — or taking the time to understand the perspectives of those of us who spoke up for India within the group.</p><p>In moments like these, the influence of social media can’t be ignored. It often amplifies emotionally charged narratives, sometimes at the expense of accuracy or context. It’s important to recognize how quickly misinformation can spread, shaping opinions before facts are fully understood. Before rushing to judgment, it’s worth pausing to verify information and approach these situations with a willingness to question, research, and reflect — especially when friendships and trust are at stake.</p><p>There were certainly individuals who recognized that this was a complex situation as India and Pakistan have a long, sensitive history and naturally, there would be differing perspectives and patriotic sentiments. I genuinely appreciated those who remained open to dialogue despite the tension.</p><p>However, it was disheartening to witness how, when some of us tried to share our perspectives, we were immediately labeled as “lusting for blood” by some people.</p><p>And these reactions weren’t limited to friends across the border — some voices from other Muslim-majority countries echoed similar sentiments. The double standard was difficult to overlook: expressions of national or religious solidarity from one side were allowed to raise their opinions, while those of us speaking from our own identity or patriotism were urged into silence.</p><p>This led me to ask a difficult question: <em>How valid is this one-sided narrative? </em>And more importantly — <em>why are friendships so easily discarded in the face of political disagreement?</em></p><p>What happened to the mutual respect we so proudly upheld? What happened to the idea of a global village — a space where people of different faiths, ethnicities, and worldviews could coexist and even thrive together?</p><p>I don’t have all the answers. But I do know this: if we truly believe in the values of dialogue, empathy, and cross-cultural friendship, we must be willing to listen — even when it’s uncomfortable. We must be able to differentiate between political critique and personal attack. And we must not let geopolitical events destroy the bridges we’ve worked so hard to build.</p><p>If friendship can’t withstand disagreements or if it silences someone’s voice, can it truly be called friendship at all?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2b8ffd8f540" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data Demystified]]></title>
            <link>https://medium.com/@radhakotecha/data-demystified-7926e76c4284?source=rss-88f2e06d8c4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7926e76c4284</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[algorithms]]></category>
            <category><![CDATA[career-growth]]></category>
            <category><![CDATA[data-structures]]></category>
            <category><![CDATA[learning-in-public]]></category>
            <dc:creator><![CDATA[Radha Kotecha]]></dc:creator>
            <pubDate>Mon, 05 May 2025 05:08:59 GMT</pubDate>
            <atom:updated>2025-05-05T05:08:59.950Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hello, everyone!</h3><p>I’m <strong>Radha</strong> — a 28-year-old software engineer with about 7 years of experience, currently on a mission to <strong>relearn Data Structures from the ground up</strong>.</p><p>I figured this would be the perfect opportunity to document what I’m learning — so if I confuse myself along the way, at least I’ll confuse others with me (you’re welcome).</p><p>At the end of this series, I’ll be sharing all the resources I’ve used, so stay tuned!</p><p>Before we dive in, occasional bad jokes will be sprinkled in — sorry, not sorry.</p><h3>So, where do we begin?</h3><p>Ah yes — the very foundation of it all: <strong>data</strong>.</p><p>Think about it: from life-saving decisions like predicting heart attacks using medical data, to guiding planes safely across continents with flight data… all the way down to your phone reminding you how many steps you’ve taken today — or Netflix desperately trying to guess what you’ll binge next based on your “guilty pleasure” history.</p><p>Even that random BuzzFeed quiz telling you what kind of bread you are? Yep, <strong>that’s data at work.</strong></p><h3>Let’s make this visual.</h3><p>Imagine <strong>Instagram</strong> has tens of thousands of users.<br> Now, think of all these usernames scribbled randomly on tiny pieces of paper scattered across a room.</p><p>Sure, it’s data — but in that form, it’s about as useful as socks without their pair.</p><p>So what do we do? We <strong>organize</strong> it.</p><p>Suppose we want to arrange usernames alphabetically. We might:</p><ul><li>Create piles for names starting with A, B, C, and so on</li><li>Separate them into small labeled bags</li><li>Or even map them out on a giant sheet of paper like a Pinterest mood board</li></ul><p>Whatever method we choose to organize this data — that system of organization is what we call a <strong>data structure.</strong></p><p>(Yes, even if it involves sticky notes and chaos.)</p><p>Now that the data is structured, we need a way to <strong>store</strong> it.<br> Because if we don’t store it, every time we need to look up a username, we’ll have to go through the whole organizing mess again — and honestly, who has the energy?</p><p>Let’s say we draw the organized pattern on a big sheet of paper.<br> That paper is where the structured data lives.</p><p>In technical terms, <strong>that’s your database.</strong></p><p>But here’s the thing: <strong>data keeps growing.</strong><br> Like, “I swear I just cleaned this room and it’s messy again” kind of growing.</p><p>A typical Instagram user scrolls through at least <strong>100 reels a day</strong> (don’t lie, you know it’s true).<br> Let’s say we log every reel a user watches on a sheet of paper (<strong>Paper 1</strong>).</p><p>Five years later, Paper 1 runs out of space. So we start logging on <strong>Paper 2</strong>.</p><p>Fifteen years later? We’ve filled up several papers: <strong>Paper 1, Paper 2, Paper 3, Paper 4, Paper 5.</strong></p><p>If you want to know what a user watched <strong>yesterday</strong>, you’d check the most recent sheet — <strong>Paper 5</strong>.<br> But if you want to give them a <strong>nostalgic throwback</strong> to what they were watching ten years ago, you’d have to dig into <strong>Paper 3</strong>.</p><p>All these older sheets — Paper 1, Paper 2, Paper 3, Paper 4 — together form what we call a <strong>data warehouse.</strong></p><p>They’re usually stored separately from the current, active data (Paper 5), like that “miscellaneous drawer” we all have but pretend we don’t.</p><p>Now imagine you want to figure out <strong>the latest reel trends across all Instagram users in India.</strong><br> To do that, you’d need to analyze <strong>every reel watched by every user in the country.</strong></p><p>That’s… a lot of data.<br> Like, “I’m going to need more coffee” level of data.</p><p>That’s exactly where <strong>big data</strong> comes into play.</p><h3>In short:</h3><p>✅ Organizing data = <strong>Data Structure</strong><br> ✅ Storing data = <strong>Database</strong><br> ✅ Collecting historical data over time = <strong>Data Warehouse</strong><br> ✅ Handling massive, complex datasets = <strong>Big Data</strong></p><h3>Cool, we know what data is… but now we need to do stuff with it.</h3><p>Suppose we want to go through all the users to search for a specific one, or maybe to perform an action on each of them.</p><p>There isn’t just one way to do it. We could:</p><ul><li>Go through the list from start to finish</li><li>Skip around in a pattern</li><li>Use a smarter shortcut to narrow things down faster</li></ul><p>Each method of going through the data is a different <strong>algorithm.</strong></p><p>In simple terms, <strong>an algorithm is a set of steps or rules we follow to get something done with data.</strong></p><p>Think of it like a recipe, but instead of cookies, it’s… user data. (But if you bring cookies, even better.)</p><p>We know there are <strong>multiple ways to traverse the user list.</strong></p><p>Let’s say I need to perform an operation <strong>at least 100 times a day.</strong><br> I have three different algorithms I could use:</p><ul><li><strong>Algorithm 1</strong> takes <strong>100 minutes</strong></li><li><strong>Algorithm 2</strong> takes <strong>50 minutes</strong></li><li><strong>Algorithm 3</strong> takes <strong>25 minutes</strong></li></ul><p>Which one would I choose?<br> <strong>Obviously, the one that takes 25 minutes!</strong><br> (Unless you’re secretly looking for excuses to avoid work, but let’s be real.)</p><p>The <strong>time an algorithm takes to complete its task</strong> is what we call <strong>time complexity.</strong></p><p>In simple terms, <strong>time complexity tells us how efficient an algorithm is, especially as the amount of data grows.</strong></p><p>Choosing the right algorithm isn’t just about getting the job done — it’s about getting it done <strong>faster, smarter, and with fewer “ugh” moments.</strong></p><p>✨ Thanks for sticking around! I’ll be back with more learnings (and probably more paper metaphors) in the next part.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7926e76c4284" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>