<?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 Minisha Murugan on Medium]]></title>
        <description><![CDATA[Stories by Minisha Murugan on Medium]]></description>
        <link>https://medium.com/@minisha.mit?source=rss-a9b334def111------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UM0MtG1089XLAuML94Y8tA@2x.jpeg</url>
            <title>Stories by Minisha Murugan on Medium</title>
            <link>https://medium.com/@minisha.mit?source=rss-a9b334def111------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:32:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@minisha.mit/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[Abstract and physical thinking]]></title>
            <link>https://medium.com/@minisha.mit/abstract-and-physical-thinking-91316c557465?source=rss-a9b334def111------2</link>
            <guid isPermaLink="false">https://medium.com/p/91316c557465</guid>
            <dc:creator><![CDATA[Minisha Murugan]]></dc:creator>
            <pubDate>Sun, 03 Nov 2024 16:13:25 GMT</pubDate>
            <atom:updated>2024-11-03T16:13:25.244Z</atom:updated>
            <content:encoded><![CDATA[<h4>Abstract and physical thinking are two different modes of understanding and interacting with the world, each with its strengths and applications.</h4><p>1. Abstract Thinking involves processing concepts, ideas, and relationships that are not directly tied to concrete or physical experiences. It enables people to understand complex ideas, make generalizations, consider possibilities, and think about things that are not immediately present. This form of thinking is often associated with:</p><p>•	Conceptualization: Forming ideas or theories based on abstract relationships or principles.</p><p>•	Problem-solving: Using patterns, analogies, and hypothetical reasoning to address complex issues.</p><p>•	Creativity and Innovation: Imagining new ideas or solutions beyond what currently exists or what can be seen.</p><p>•	Mathematics and Logic: Working with numbers, symbols, and relationships that represent abstract ideas rather than tangible objects.</p><p>•	Metaphor and Analogy: Thinking in terms of symbols or representations rather than literal interpretations.</p><p>Abstract thinking is essential for fields like philosophy, mathematics, theoretical physics, and even art, where ideas are often more important than their physical counterparts.</p><p>2. Physical thinking, or concrete thinking, is more direct and involves processing information about tangible, observable things. It’s grounded in sensory experience and involves:</p><p>•	Practical Problem-solving: Addressing immediate, hands-on challenges (like building something or fixing a physical object).</p><p>•	Spatial Awareness: Understanding physical space, objects, and the relationships between them.</p><p>•	Motor Skills: Applying knowledge of physical principles to perform actions (like driving, sports, or craftsmanship).</p><p>•	Direct Observation and Empiricism: Basing understanding on observable facts and direct evidence.</p><p>•	Action-Oriented Approaches: Focusing on doing and interacting with the physical environment.</p><p>Physical thinking is essential in fields like engineering, construction, biology, and athletics, where understanding physical reality is key to success.</p><p>Importance of Both Modes of Thinking</p><p>Both abstract and physical thinking are crucial, as they complement each other. Abstract thinking allows us to innovate and dream up possibilities beyond the current physical reality, while physical thinking grounds us, enabling us to implement ideas and interact effectively with the material world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91316c557465" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working on yourself]]></title>
            <link>https://medium.com/@minisha.mit/why-working-on-yourself-is-so-hard-84e7a21fb67e?source=rss-a9b334def111------2</link>
            <guid isPermaLink="false">https://medium.com/p/84e7a21fb67e</guid>
            <dc:creator><![CDATA[Minisha Murugan]]></dc:creator>
            <pubDate>Sun, 27 Oct 2024 11:49:24 GMT</pubDate>
            <atom:updated>2024-10-27T11:57:58.114Z</atom:updated>
            <content:encoded><![CDATA[<h2>Why Working on Yourself Feels So Hard (and Why It’s Worth It)</h2><p>Working on yourself is challenging for several reasons, and it’s often harder than tackling external tasks or goals. Here’s why:</p><ol><li>Self-Awareness is Uncomfortable</li></ol><p>Self-improvement requires you to be honest about your flaws, habits, and limitations. It can be painful to confront parts of yourself that you don’t like, especially if you’ve been avoiding or rationalizing them for a long time.</p><p>2. Habits Are Deeply Embedded</p><p>Much of our behavior is automatic, influenced by deeply ingrained habits. Changing these habits demands consistent effort over time, which is hard to maintain, especially when the mind prefers the comfort of familiar routines.</p><p>3. Immediate Results Are Rare</p><p>Self-improvement doesn’t often show quick results. This lack of instant gratification can make it hard to stay motivated, as it may feel like progress is slow or nonexistent, even if you’re moving in the right direction.</p><p>4. Fear of Failure or Success</p><p>Growth means stepping into the unknown, which can trigger fears of both failure and success. Failure might confirm our self-doubts, while success can bring new responsibilities, expectations, and changes that disrupt the comfort zone.</p><p>5. Mental and Emotional Resistance</p><p>Working on yourself requires emotional strength because it often involves addressing uncomfortable feelings and past traumas. The mind sometimes resists change because it’s trying to protect you from these uncomfortable emotions.</p><p>6. Requires Consistent Effort</p><p>Unlike projects with a clear endpoint, self-work is an ongoing process without a set finish line. This continuous demand for effort, introspection, and adaptability can be draining.</p><p>7. Lack of External Accountability</p><p>External tasks often have deadlines, peer pressure, or accountability structures, but self-improvement is personal, and you’re often the only one keeping yourself on track. Without external accountability, it’s easier to procrastinate or give up when things get hard.</p><p>8. Complexity of Inner Conflicts</p><p>Our values, beliefs, and desires sometimes conflict with each other. For example, you may want success but also fear rejection or criticism. Navigating these contradictions can be confusing and emotionally exhausting.</p><p>9. Self-Sabotage and Limiting Beliefs</p><p>Deep-seated limiting beliefs can lead to self-sabotage, where you unconsciously undermine your own efforts. Rewriting these beliefs is a complex, lengthy process that requires constant self-awareness and self-compassion.</p><p>Working on yourself is difficult, but each step can bring genuine growth and fulfillment. Embracing the process, even in its messiness, can lead to a stronger, more authentic sense of self.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84e7a21fb67e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mystery calculator]]></title>
            <link>https://medium.com/@minisha.mit/mystery-calculator-19d3fb6802b6?source=rss-a9b334def111------2</link>
            <guid isPermaLink="false">https://medium.com/p/19d3fb6802b6</guid>
            <category><![CDATA[math-games-for-kids]]></category>
            <category><![CDATA[math-games]]></category>
            <dc:creator><![CDATA[Minisha Murugan]]></dc:creator>
            <pubDate>Mon, 08 Apr 2024 19:20:42 GMT</pubDate>
            <atom:updated>2024-04-08T19:20:42.151Z</atom:updated>
            <content:encoded><![CDATA[<p>I got the game binary card trick from a Christmas cracker. And I was really intrigued by the math behind it. Lets explore how it works!</p><p>It consist of 6 cards, printed with a series of numbers. Show all the cards to your friends and ask them to select a number from one of the card. Then flash the card one by one and ask them if the selected number is present in the card. Take all the cards on which the number is present, add the number from the top left-hand corner on each card. The total is the number your friend has selected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/361/1*ygF5kaUvkaH9d4USZRE9jA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*2Bi3_dBYnqkffMZs84Fz2Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*8TuJP81X_7IqdWF8Rym6TQ.png" /></figure><p>Say for instance, Tom selected the number 41. It’s available in card 1, 4 and 6, adding the number on left-hand corner will give you 1+8+32 = 41. Tada, you got the number your friend selected!</p><p><strong>How it works?</strong><br>Have a look at the number in top corner 1, 2, 4, 8, 16, 32. Do you see a pattern?</p><p>Thats right, they are powers of 2.<br>2⁰, 2¹, 2², 2³, 2⁴, 2⁵</p><p>Although the number written in those cards looks like randomly selected ones, they are specifically chosen to appear on the card between 1 to 63. All the available numbers in the card can be written using power of 2 because binary/base-2 numbers system used to make up the cards.</p><p><strong>How to make up the cards?</strong><br>Write down the binary expansion of numbers from 1 to 63 as shown in the above table. The numbers in card 1 are the numbers which has one at the 1st position (starting from right to left), numbers in card 2 are those have one at 2nd position and so on.</p><p>Since we have six cards, the number 63 is chosen as the max 2⁸-1. If we want to add one more card the max number to discover would be 2⁹-1 and so on.</p><p>Math is fun! Give it a try with your friends.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19d3fb6802b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhancing Feedback Sessions with the Six Thinking Hats Method: A Guide to Constructive and Balanced…]]></title>
            <link>https://medium.com/@minisha.mit/enhancing-feedback-sessions-with-the-six-thinking-hats-method-a-guide-to-constructive-and-balanced-747ce8f24aa0?source=rss-a9b334def111------2</link>
            <guid isPermaLink="false">https://medium.com/p/747ce8f24aa0</guid>
            <dc:creator><![CDATA[Minisha Murugan]]></dc:creator>
            <pubDate>Sat, 02 Mar 2024 11:01:45 GMT</pubDate>
            <atom:updated>2024-03-02T11:08:05.822Z</atom:updated>
            <content:encoded><![CDATA[<h3>Enhancing Feedback Sessions with the Six Thinking Hats Method: A Guide to Constructive and Balanced Communication</h3><p>When providing feedback, whether in a managerial position or within a team, the goal is to foster an environment of growth, improvement, and mutual respect. One innovative approach to achieve this is by employing the Six Thinking Hats method, developed by Edward de Bono. This technique offers a structured way to explore different perspectives during a feedback session, making it more comprehensive, balanced, and effective. By categorizing thoughts under six distinct areas — information (White Hat), emotions (Red Hat), caution (Black Hat), optimism (Yellow Hat), creativity (Green Hat), and management (Blue Hat) — this method encourages a holistic view of performance and behavior. It not only facilitates clearer communication but also ensures that feedback is well-rounded, addressing not just the areas of improvement but also recognizing strengths and exploring solutions collaboratively. The following examples illustrate how the Six Thinking Hats method can be applied in feedback sessions to encourage open dialogue, promote self-awareness, and inspire positive change.</p><p>Let’s consider a scenario where a team leader needs to provide feedback to a team member, Jordan, who has shown exceptional performance but struggles with team collaboration. Here’s how the Six Thinking Hats method can be applied:</p><p><strong>1. White Hat: Focus on Data and Information</strong><br>Example:</p><p>Jordan, over the past quarter, you’ve consistently exceeded your individual performance targets. For instance, you completed your project deliverables ahead of schedule by 10% on average, which is commendable.</p><p><strong>2. Red Hat: Emotions and Feelings</strong><br>Example:</p><p>I’ve noticed some tension during team meetings and interactions. It seems like there might be some frustration or miscommunication happening. From my side, it’s important that everyone feels supported and collaborative.</p><p><strong>3. Black Hat: Caution and Critical Judgement</strong><br>Example: While your individual contributions are outstanding, the lack of collaboration with the team could lead to missed opportunities for knowledge sharing and might affect the overall team harmony and project success.</p><p><strong>4. Yellow Hat: Optimism and Positive Perspective</strong><br>Example:</p><p>Your ability to deliver exceptional work is a huge asset, and if we can harness that alongside effective teamwork, I believe our team can achieve even greater results. Your leadership in projects can also serve as an inspiration for teamwork excellence.</p><p><strong>5. Green Hat: Creativity and New Ideas</strong><br>Example:</p><p>Let’s explore ways to enhance team collaboration. Perhaps we can initiate a mentorship program where your skills can benefit others, or maybe adjust our meeting structure to allow more open discussion and idea exchange. What are your thoughts on how we can improve this aspect?</p><p><strong>6. Blue Hat: Process Control</strong><br>Example:</p><p>To summarize, while your individual performance is impressive, we need to focus on strengthening team collaboration. Let’s develop a plan that includes specific actions for improving communication and teamwork, such as structured team-building activities or collaborative project roles. We’ll review the progress in our next monthly meeting to ensure we’re moving in the right direction.</p><p>Use Six Thinking Hats to provide balanced and constructive feedback that not only recognizes achievements but also addresses areas for improvement in a supportive and solution-focused manner.</p><p>Give it a try and share ur experience in comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=747ce8f24aa0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Coding at Risk?]]></title>
            <link>https://medium.com/@minisha.mit/is-coding-at-risk-510685967e6e?source=rss-a9b334def111------2</link>
            <guid isPermaLink="false">https://medium.com/p/510685967e6e</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[dangerous-of-ai-on-coding]]></category>
            <category><![CDATA[co-pilot]]></category>
            <category><![CDATA[cody]]></category>
            <category><![CDATA[ai-overreliance]]></category>
            <dc:creator><![CDATA[Minisha Murugan]]></dc:creator>
            <pubDate>Fri, 01 Mar 2024 17:38:53 GMT</pubDate>
            <atom:updated>2024-03-02T10:31:36.335Z</atom:updated>
            <content:encoded><![CDATA[<h3>Is Coding Craftsmanship at Risk?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FgI2gqP5LWCNeePAJVoX-Q.jpeg" /></figure><p>I have been thinking about the recent rapid development in AI. As someone who appreciates the art of coding, seeing tools like Codex and GitHub Copilot has made me ponder:</p><p>Are they going to evolve in a way that will make us not think at all?</p><p>I have noticed that my mother’s and grandmother’s generations were really good at mental math, a skill that seems to be long lost nowadays.</p><p>Is the art of coding going to be the same?”</p><p>In the future, are we just going to click some buttons to make things happen? Is our mind, one of the greatest evolutions, going to vanish?</p><p>Use it or lose it’ is a fundamental truth. Given that, Are we going to evolve into something with capabilities lower than what we have now?</p><p>Too much of anything is good for nothing! We have to be mindful more than ever when using these tools. In my opinion, for sure, if the rapid growth of AI, gets out of hand, is not used in a balanced way, or is not employed correctly to improve ourselves, could significantly affect our cognitive abilities. Becoming overly dependent on it might lead us to lose vital skills. We have to remind ourselves that, improvement isn’t just about creating better gadgets; it’s also about self-enhancement.</p><p>As we advance into this new territory, we should keep in mind that our greatest asset is not the technology we develop, but the people behind it. Ensuring that our minds remain sharp, active, and capable of deep thinking is, above all, the most crucial objective.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=510685967e6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating the Nuances of SMART Goals in Software Engineering]]></title>
            <link>https://medium.com/@minisha.mit/navigating-the-nuances-of-smart-goals-in-software-engineering-5f13aab8c2ee?source=rss-a9b334def111------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f13aab8c2ee</guid>
            <dc:creator><![CDATA[Minisha Murugan]]></dc:creator>
            <pubDate>Thu, 01 Feb 2024 21:36:17 GMT</pubDate>
            <atom:updated>2024-02-01T22:00:29.712Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7HAv0Hx47eNtNnNGDj19-w.png" /></figure><p>In the dynamic world of software engineering, the concept of setting SMART (Specific, Measurable, Achievable, Relevant, Time-bound) goals is widely accepted as a best practice. However, a closer examination reveals that how these goals are formulated can significantly impact their effectiveness and the behavior they drive. This article explores the subtle yet crucial differences in setting SMART goals, particularly in the context of software engineering, using the example of improving unit test coverage.</p><h3>The Pitfall of Purely Quantitative Goals:</h3><p>Consider the goal of “improving unit test coverage by 80%.” On the surface, this goal ticks all the boxes of the SMART framework: it’s specific, clearly measurable, presumably achievable, relevant to software quality, and can be time-bound. However, this goal’s formulation has an intrinsic flaw: its narrow focus on a quantifiable target potentially undermines the broader objective, which is to enhance code quality and stability.</p><p>This approach can inadvertently prioritize quantity over quality. Engineers might rush to meet the numerical target, compromising the integrity and effectiveness of the tests. Such a goal could also create a disconnect between the team’s efforts and the project’s needs, as the deeper purpose of improving code quality might be overshadowed by the rush to hit a numerical target.</p><h3>The Value of Integrating Qualitative Aspects:</h3><p>Now, let’s rephrase the goal: “Enhance the unit test coverage to achieve at least 80%, aiming to significantly improve the overall quality and stability of our code.” This goal still adheres to the SMART principles but does so in a way that emphasizes the ultimate purpose of the task.</p><p>By integrating both qualitative and quantitative elements, the goal encourages a more comprehensive approach. It’s not just about increasing the number of tests but improving the overall quality of the code. This version of the goal aligns with the broader objectives of software development – creating stable, high-quality products – and can be more motivating for the team. Understanding the reason behind a goal can foster a sense of purpose and engagement, leading to more effective and meaningful outcomes.</p><p>In conclusion, while setting measurable goals is crucial in software engineering for tracking progress and ensuring accountability, it’s vital to frame these goals in a way that reflects their broader purpose. By balancing the quantitative aspects with qualitative objectives, engineering managers can set goals that not only meet the SMART criteria but also inspire and guide their teams towards meaningful, quality-driven outcomes. This nuanced approach to goal-setting is not just a managerial tactic but a strategic tool in building successful, motivated software engineering teams.</p><blockquote>Hit the Bullseye: Aim for Quality!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/1*8azjv1De19a7AwE8vl9eWg@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f13aab8c2ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts on Love configurations on Humanoid Robots]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@minisha.mit/thoughts-on-love-configurations-on-humanoid-robots-62cb3d01a4e7?source=rss-a9b334def111------2"><img src="https://cdn-images-1.medium.com/max/1792/1*-qbA2-SmlBrTRyhQ3pyDSQ.png" width="1792"></a></p><p class="medium-feed-snippet">Introduction</p><p class="medium-feed-link"><a href="https://medium.com/@minisha.mit/thoughts-on-love-configurations-on-humanoid-robots-62cb3d01a4e7?source=rss-a9b334def111------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@minisha.mit/thoughts-on-love-configurations-on-humanoid-robots-62cb3d01a4e7?source=rss-a9b334def111------2</link>
            <guid isPermaLink="false">https://medium.com/p/62cb3d01a4e7</guid>
            <category><![CDATA[humanoid-robots-love]]></category>
            <category><![CDATA[humanoid-robot]]></category>
            <dc:creator><![CDATA[Minisha Murugan]]></dc:creator>
            <pubDate>Sun, 21 Jan 2024 17:29:24 GMT</pubDate>
            <atom:updated>2024-01-21T17:35:03.618Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[2024 SMART Goals Framework]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@minisha.mit/2024-smart-goals-framework-2986bee13a67?source=rss-a9b334def111------2"><img src="https://cdn-images-1.medium.com/max/1792/1*FMwToMmsIRK37huf2JVx6A.png" width="1792"></a></p><p class="medium-feed-snippet">In an era filled with dreams and goals, the key to achieving personal and professional growth lies in setting clear, attainable objectives&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@minisha.mit/2024-smart-goals-framework-2986bee13a67?source=rss-a9b334def111------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@minisha.mit/2024-smart-goals-framework-2986bee13a67?source=rss-a9b334def111------2</link>
            <guid isPermaLink="false">https://medium.com/p/2986bee13a67</guid>
            <category><![CDATA[2024-work-goals]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[2024-goal]]></category>
            <category><![CDATA[personal-goals-for-2024]]></category>
            <dc:creator><![CDATA[Minisha Murugan]]></dc:creator>
            <pubDate>Sun, 21 Jan 2024 15:57:57 GMT</pubDate>
            <atom:updated>2024-01-21T19:51:48.964Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[EWIT03 Book Recommendations]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@minisha.mit/ewit03-book-recommendations-4122b748576e?source=rss-a9b334def111------2"><img src="https://cdn-images-1.medium.com/max/1920/1*NOM5tOJbcomHcp_Sofr_zw.jpeg" width="1920"></a></p><p class="medium-feed-snippet">Sharing the book recommendations that were recommended by the attendees of the conference.</p><p class="medium-feed-link"><a href="https://medium.com/@minisha.mit/ewit03-book-recommendations-4122b748576e?source=rss-a9b334def111------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@minisha.mit/ewit03-book-recommendations-4122b748576e?source=rss-a9b334def111------2</link>
            <guid isPermaLink="false">https://medium.com/p/4122b748576e</guid>
            <dc:creator><![CDATA[Minisha Murugan]]></dc:creator>
            <pubDate>Mon, 03 Jul 2023 18:37:00 GMT</pubDate>
            <atom:updated>2023-07-03T18:45:36.189Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[EWIT 2023]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@minisha.mit/ewit-2023-4be858c90008?source=rss-a9b334def111------2"><img src="https://cdn-images-1.medium.com/max/1600/1*i02HaNrPzR12TiVKhnq0dQ.png" width="1600"></a></p><p class="medium-feed-snippet">Day 2 booth visit reflections</p><p class="medium-feed-link"><a href="https://medium.com/@minisha.mit/ewit-2023-4be858c90008?source=rss-a9b334def111------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@minisha.mit/ewit-2023-4be858c90008?source=rss-a9b334def111------2</link>
            <guid isPermaLink="false">https://medium.com/p/4be858c90008</guid>
            <dc:creator><![CDATA[Minisha Murugan]]></dc:creator>
            <pubDate>Sun, 02 Jul 2023 10:44:41 GMT</pubDate>
            <atom:updated>2023-07-02T17:00:08.289Z</atom:updated>
        </item>
    </channel>
</rss>