<?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 Pratish on Medium]]></title>
        <description><![CDATA[Stories by Pratish on Medium]]></description>
        <link>https://medium.com/@pratishgupta91?source=rss-3559b5c3008b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rLGcA8zgNasSzlHlMLJZDQ.jpeg</url>
            <title>Stories by Pratish on Medium</title>
            <link>https://medium.com/@pratishgupta91?source=rss-3559b5c3008b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:50:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pratishgupta91/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[Tip #1 — Personal Finance — Don’t go near these 3 banks]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Three worst banks to put your savings</p><p class="medium-feed-link"><a href="https://medium.com/@pratishgupta91/tip-1-personal-finance-dont-go-near-these-3-banks-2c696fefeff8?source=rss-3559b5c3008b------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@pratishgupta91/tip-1-personal-finance-dont-go-near-these-3-banks-2c696fefeff8?source=rss-3559b5c3008b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c696fefeff8</guid>
            <dc:creator><![CDATA[Pratish]]></dc:creator>
            <pubDate>Sat, 29 Mar 2025 16:05:18 GMT</pubDate>
            <atom:updated>2025-03-29T16:05:18.103Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A two-line story]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/illumination/a-two-line-story-93306c9573a7?source=rss-3559b5c3008b------2"><img src="https://cdn-images-1.medium.com/max/1280/1*z3h1kwLVw1euqTpVGoe8bQ.jpeg" width="1280"></a></p><p class="medium-feed-snippet">It won&#x2019;t bite!</p><p class="medium-feed-link"><a href="https://medium.com/illumination/a-two-line-story-93306c9573a7?source=rss-3559b5c3008b------2">Continue reading on ILLUMINATION »</a></p></div>]]></description>
            <link>https://medium.com/illumination/a-two-line-story-93306c9573a7?source=rss-3559b5c3008b------2</link>
            <guid isPermaLink="false">https://medium.com/p/93306c9573a7</guid>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[dark]]></category>
            <category><![CDATA[humor]]></category>
            <dc:creator><![CDATA[Pratish]]></dc:creator>
            <pubDate>Mon, 04 Nov 2024 02:22:07 GMT</pubDate>
            <atom:updated>2024-11-04T02:22:07.521Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Confessions of an Introvert]]></title>
            <link>https://medium.com/word-garden/confessions-of-an-introvert-45e9a0ecb8c8?source=rss-3559b5c3008b------2</link>
            <guid isPermaLink="false">https://medium.com/p/45e9a0ecb8c8</guid>
            <category><![CDATA[mindfulness]]></category>
            <category><![CDATA[introvert]]></category>
            <category><![CDATA[wordgarden]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[rain]]></category>
            <dc:creator><![CDATA[Pratish]]></dc:creator>
            <pubDate>Mon, 07 Oct 2024 06:21:07 GMT</pubDate>
            <atom:updated>2024-10-07T06:21:08.412Z</atom:updated>
            <content:encoded><![CDATA[<p>short, as usual!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lDFPgZcDdpke4s-N.jpeg" /><figcaption>Generated by Meta AI</figcaption></figure><p>I am an INTROVERT. Intertwined in my own conflicts with words and voices.</p><p>You were there at the party. Speaking incessantly about your new hobby, or your recent breakdown at work.</p><p>I am wired differently.</p><p>I am incapable of disseminating my inner voices. But, you always nudge me to speak up about anything.</p><p>My voice shakes and I forget my punchline in the middle. I wish I had practised the fake scripts before.</p><p>Perhaps you think I am dumb.</p><p>I know you want to fix me — ask intriguing questions, share quirky facts, use light humor, or offer thoughtful compliments to keep things rolling.</p><p>But countless confusing stories collide and create ripples around my brain — 3 ways to save more for retirement, abstract poetry, react programming, glaciers melting in Alaska … blah blah blah</p><p>My head wants to pick a quirky one and spit it out. I resist.</p><p>Maybe it’s a good thing to <em>talk </em>less and observe . Gives you more time to spin another <em>story</em>.</p><p>Or, maybe it is not. Sometimes, too many voices easily bring down the protagonist.</p><p>So let me tell you a <em>true </em>one this time—<br><em>Just listen to the rain. Sometimes that’s the best story of all.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45e9a0ecb8c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/word-garden/confessions-of-an-introvert-45e9a0ecb8c8">Confessions of an Introvert</a> was originally published in <a href="https://medium.com/word-garden">Word Garden</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Probably Suck at Coding]]></title>
            <link>https://blog.stackademic.com/you-probably-suck-at-coding-47fadc3f34c8?source=rss-3559b5c3008b------2</link>
            <guid isPermaLink="false">https://medium.com/p/47fadc3f34c8</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[c-sharp-programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Pratish]]></dc:creator>
            <pubDate>Mon, 07 Oct 2024 03:14:33 GMT</pubDate>
            <atom:updated>2024-10-07T03:14:33.411Z</atom:updated>
            <content:encoded><![CDATA[<p>And here is the fix!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iKHi8bZ8GWG8Uq80nRVw1g.jpeg" /><figcaption>Generated by Meta AI</figcaption></figure><p>Are you one of those who meticulously chase every byte, crafting code like it’s a delicate masterpiece?</p><p><em>Newsflash: nobody cares!</em></p><p>While you’re sweating over efficiency and memory optimization, the rest of us are reveling in the beauty of simplicity. It’s not just about squeezing out performance or trimming every ounce of memory;</p><p>⚡<strong> It’s about writing code that sings, flows, and gets the job done with elegance.</strong></p><p>In a world of complex problems, clarity and maintainability are the true heroes. So, let go of the obsession with optimization and embrace the joy of creating code that’s as readable and effective.</p><p>Here’s a nicely structured contrast of <strong><em>coding inspirations</em></strong> at beginner, intermediate, and expert levels.</p><h3>🏃LEVEL — BEGINNER</h3><h3>1. For Loops</h3><p><strong>Old Way:</strong></p><pre>for (int i = 0; i &lt; array.Length; i++) { /* process */ }</pre><p><strong>Modern Way:</strong></p><pre>foreach (var item in array) { /* process */ }</pre><p><strong>Reason</strong>: Clearer and safer — less chance of off-by-one errors!</p><h3>2. Manual String Concatenation</h3><p><strong>Old Way:</strong></p><pre>string result = &quot;&quot;;<br>for (int i = 0; i &lt; strings.Length; i++) { result += strings[i]; }</pre><p><strong>Modern Way:</strong></p><pre>var result = string.Join(&quot;&quot;, strings);</pre><p><strong>Reason</strong>: No more O(n²) performance pitfalls — use Join for clarity and speed!</p><h3>3. Counting Elements</h3><p><strong>Old Way:</strong></p><pre>int count = 0;<br>for (int i = 0; i &lt; list.Count; i++) { count++; }</pre><p><strong>Modern Way:</strong></p><pre>int count = list.Count();</pre><p><strong>Reason</strong>: Count directly — one line wins over manual iteration!</p><h3>4. Finding Items</h3><p><strong>Old Way:</strong></p><pre>bool found = false;<br>for (int i = 0; i &lt; list.Count; i++) { if (list[i] == target) found = true; }</pre><p><strong>Modern Way:</strong></p><pre>bool found = list.Contains(target);</pre><p><strong>Reason</strong>: Readable and expressive — stop reinventing the wheel!</p><h3>5. Removing Duplicates</h3><p><strong>Old Way:</strong></p><pre>List&lt;int&gt; results = new List&lt;int&gt;();<br>for (int i = 0; i &lt; numbers.Count; i++) { if (numbers[i] &gt; 10) results.Add(numbers[i]); }</pre><p><strong>Modern Way:</strong></p><pre>var results = numbers.Where(n =&gt; n &gt; 10).ToList();</pre><h3>👽LEVEL — INTERMEDIATE</h3><h3>1. Selecting Properties</h3><p><strong>Old Way:</strong></p><pre>List&lt;string&gt; names = new List&lt;string&gt;();<br>for (int i = 0; i &lt; people.Count; i++) { names.Add(people[i].Name); }</pre><p><strong>Modern Way:</strong></p><pre>var names = people.Select(p =&gt; p.Name).ToList();</pre><p><strong>Reason</strong>: Focus on what you want, not how to get it!</p><h3>2. Flattening Nested Collections</h3><p><strong>Old Way:</strong></p><pre>List&lt;int&gt; flatList = new List&lt;int&gt;();<br>foreach (var sublist in nestedList) { flatList.AddRange(sublist); }</pre><p><strong>Modern Way:</strong></p><pre>var flatList = nestedList.SelectMany(sublist =&gt; sublist).ToList();</pre><p><strong>Reason</strong>: LINQ handles nesting effortlessly — clean and powerful.</p><h3>3. Finding First Match with Complex Conditions</h3><p><strong>Old Way:</strong></p><pre>Person found = null;<br>foreach (var person in people)<br>{<br>    if (person.Age &gt; 30 &amp;&amp; person.City == &quot;London&quot;)<br>    {<br>        found = person;<br>        break;<br>    }<br>}</pre><p><strong>Modern Way:</strong></p><pre>var found = people.FirstOrDefault(p =&gt; p.Age &gt; 30 &amp;&amp; p.City == &quot;London&quot;);</pre><p><strong>Reason</strong>: Clear intent with FirstOrDefault encapsulates the logic.</p><h3>4. Filtering and Selecting in One Go</h3><p><strong>Old Way:</strong></p><pre>var results = new List&lt;string&gt;();<br>foreach (var item in items)<br>{<br>    if (item.IsActive)<br>    {<br>        results.Add(item.Name);<br>    }<br>}</pre><p><strong>Modern Way:</strong></p><pre>var results = items.Where(i =&gt; i.IsActive)<br>                   .Select(i =&gt; i.Name)<br>                   .ToList();</pre><p><strong>Reason</strong>: Chaining methods clarifies both filtering and transforming.</p><h3>5. Counting Frequencies</h3><p><strong>Old Way:</strong></p><pre>var frequency = new Dictionary&lt;string, int&gt;();<br>foreach (var item in items)<br>{<br>    if (frequency.ContainsKey(item))<br>    {<br>        frequency[item]++;<br>    }<br>    else<br>    {<br>        frequency[item] = 1;<br>    }<br>}</pre><p><strong>Modern Way:</strong></p><pre>var frequency = items.GroupBy(i =&gt; i)<br>                     .ToDictionary(g =&gt; g.Key, g =&gt; g.Count());</pre><p><strong>Reason</strong>: Grouping and counting directly expresses the intent.</p><h3>😎LEVEL — EXPERT</h3><h3>1. Joining Two Collections</h3><p><strong>Old Way:</strong></p><pre>var result = new List&lt;string&gt;();<br>for (int i = 0; i &lt; products.Count; i++)<br>{<br>    for (int j = 0; j &lt; categories.Count; j++)<br>    {<br>        if (products[i].CategoryId == categories[j].Id)<br>        {<br>            result.Add($&quot;{products[i].Name} - {categories[j].Name}&quot;);<br>        }<br>    }<br>}</pre><p><strong>Modern Way:</strong></p><pre>var result = products.Join(categories,<br>                            p =&gt; p.CategoryId,<br>                            c =&gt; c.Id,<br>                            (p, c) =&gt; $&quot;{p.Name} - {c.Name}&quot;)<br>                     .ToList();</pre><p><strong>Reason</strong>: LINQ’s Join operator provides clarity and expressiveness.</p><h3>2. Sorting with Complex Criteria</h3><p><strong>Old Way:</strong></p><pre>var sortedList = new List&lt;Person&gt;(people);<br>sortedList.Sort((x, y) =&gt;<br>{<br>    int result = x.LastName.CompareTo(y.LastName);<br>    if (result == 0)<br>    {<br>        return x.FirstName.CompareTo(y.FirstName);<br>    }<br>    return result;<br>});</pre><p><strong>Modern Way:</strong></p><pre>var sortedList = people.OrderBy(p =&gt; p.LastName)<br>                       .ThenBy(p =&gt; p.FirstName)<br>                       .ToList();</pre><p><strong>Reason</strong>: Chaining OrderBy and ThenBy is more readable and concise.</p><h3>3. Complex Data Aggregation with Grouping</h3><p><strong>Old Way:</strong></p><pre>var categoryTotals = new Dictionary&lt;string, double&gt;();<br>foreach (var transaction in transactions)<br>{<br>    if (!categoryTotals.ContainsKey(transaction.Category))<br>    {<br>        categoryTotals[transaction.Category] = 0;<br>    }<br>    categoryTotals[transaction.Category] += transaction.Amount;<br>}</pre><p><strong>Modern Way:</strong></p><pre>var categoryTotals = transactions.GroupBy(t =&gt; t.Category)<br>                                 .ToDictionary(g =&gt; g.Key, g =&gt; g.Sum(t =&gt; t.Amount));</pre><blockquote><em>WRITE CLEAN, READABLE CODE, ALWAYS!</em></blockquote><h3>Stackademic 🎓</h3><p>Thank you for reading until the end. Before you go:</p><ul><li>Please consider <strong>clapping</strong> and <strong>following</strong> the writer! 👏</li><li>Follow us <a href="https://twitter.com/stackademichq"><strong>X</strong></a> | <a href="https://www.linkedin.com/company/stackademic"><strong>LinkedIn</strong></a> | <a href="https://www.youtube.com/c/stackademic"><strong>YouTube</strong></a> | <a href="https://discord.gg/in-plain-english-709094664682340443"><strong>Discord</strong></a></li><li>Visit our other platforms: <a href="https://plainenglish.io/"><strong>In Plain English</strong></a> | <a href="https://cofeed.app/"><strong>CoFeed</strong></a> | <a href="https://differ.blog/"><strong>Differ</strong></a></li><li>More content at <a href="https://stackademic.com/"><strong>Stackademic.com</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47fadc3f34c8" width="1" height="1" alt=""><hr><p><a href="https://blog.stackademic.com/you-probably-suck-at-coding-47fadc3f34c8">You Probably Suck at Coding</a> was originally published in <a href="https://blog.stackademic.com/">Stackademic</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s Never too Late to Quit Mediocrity]]></title>
            <link>https://medium.com/illumination/its-never-too-late-to-quit-mediocrity-a41918b258d7?source=rss-3559b5c3008b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a41918b258d7</guid>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[mediocrity]]></category>
            <category><![CDATA[self-help]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Pratish]]></dc:creator>
            <pubDate>Sat, 05 Oct 2024 14:49:01 GMT</pubDate>
            <atom:updated>2024-10-05T16:07:51.608Z</atom:updated>
            <content:encoded><![CDATA[<p>Start Now!</p><p><strong>Grandma Moses (Anna Mary Robertson Moses)</strong> began painting in her 70s after arthritis made it difficult to continue her work. She went on to become one of the most famous American folk artists, with her work being celebrated worldwide.</p><p>Many of us believe we’ve invested so much time and effort into our jobs that it feels impossible to walk away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zCcvgtqw1C3gMJWwamLB8Q.jpeg" /><figcaption>Generated by Meta AI</figcaption></figure><p>So, we keep showing up to the same small 5x5 office, day after day, even though, deep down, we dread it.</p><p>We don’t have the courage to take a stand and quit.</p><p>We don’t have the courage to go back to zero and start again.</p><p>We don’t have the courage to lose the mediocre identity and create a better one.</p><blockquote>We’ve turned into caffeinated squirrels on a treadmill, racing after the same damn nut every day — except the nut is just a mirage, and we’re not even sure why we wanted it in the first place. Meanwhile, the treadmill keeps speeding up, and we’re wondering how we signed up for this weird gym membership called ‘life’</blockquote><p>There’s a way that has started working for me.</p><h3><strong>Change your surroundings, NOW!</strong></h3><p>If your friends and neighbours are <em>bitching </em>about the job in the night, and then showing up at the same shitty job every single morning, then sooner or later, you will become THEM.</p><p><strong>Run away as fast as you can.</strong></p><p>Find things that you have always been passionate about — poetry, singing, Youtube-ing. Go meet people who have been doing this.</p><p>If you like doing standup-comedy, start with basement comedy gigs. Talk to the newbie comedians and make them your friends.</p><p>If you are into writing, join a writing club and show up.</p><p>How hard can it be?</p><p>Forget the embarrassment for once and take that damn step. Connect with a like-minded community.</p><h3>Increase your worth</h3><p>Don’t be another lazy-a** hooman.</p><p>You are worth something much more. Find your passion and get a coach.</p><p>If you can’t afford one, choose your role models and take inspiration.</p><p>If you can’t find a role model, read a book.</p><p>Consistency and hard work. Get better everyday. Even 0.001% matters in the long run of mathematical compounding.</p><p>Once you start improving, it’s time to find your first free customer.</p><h3>Start Free</h3><p>Sell your skill to someone for free.</p><p>If you are a writer, pitch your skill to a startup for their weekly newsletter. If you are a designer, send free logos to a small home-owned business.</p><p>If it goes south. you will learn the heck out of it. <br>If it goes well, ask you first client to get you a second one, or at least, get a testimony.<br>It’s a win-win.</p><p>The goal is to assess yourself against the market experts. Once you know where you stand, you can come back to your den and start working on your weaknesses.</p><h3>Create Your Brand</h3><p>It’s time to monetize your skills.</p><p>Your skill would be mostly either of these two—</p><ul><li>Building a business</li><li>Helping others build business</li></ul><p>Find ways to put your brand in people’s mouth.</p><p>Use Reddit, X, Facebook, or instagram to put yourself out. Show your best work and testimonials in the posts or ads.</p><p>Start your weekly newsletter about all the good you have been doing.</p><p>Reach out to your popular names in your community and ask them for a review.</p><p>Keep going and get a few more clients. Your business will start growing organically.</p><h3>Final thoughts</h3><p>Picasso once said: “Every child is an artist. The problem is how to remain an artist once we grow up.”</p><p>Amid the demands of daily life, finding time to lead a creative life — even just an hour or two to write, paint, or pursue your passion — can feel like a challenge. Yet, carving out time for creativity, however small, is essential for keeping your spirit alive.</p><p>Consistent practice not only nurtures your creative instincts but also builds resilience. So, no matter how difficult it seems, never give up on your creative pursuits.</p><p>And remember, it’s never too late to find creative success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a41918b258d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/illumination/its-never-too-late-to-quit-mediocrity-a41918b258d7">It’s Never too Late to Quit Mediocrity</a> was originally published in <a href="https://medium.com/illumination">ILLUMINATION</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does Writing Liberate You?]]></title>
            <link>https://medium.com/illumination/does-writing-liberate-you-2061f72b34b5?source=rss-3559b5c3008b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2061f72b34b5</guid>
            <category><![CDATA[illumination]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Pratish]]></dc:creator>
            <pubDate>Wed, 25 Sep 2024 01:46:26 GMT</pubDate>
            <atom:updated>2024-09-25T03:05:08.878Z</atom:updated>
            <content:encoded><![CDATA[<p>You know the answer!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YYtxDZx7ockd7TH7aPfQfA.jpeg" /><figcaption>Generated by Meta-AI</figcaption></figure><p>I have a traditional 9 to 5 job. Most of the time I end my day tired and discontent.</p><p>That’s why a few days back, I decided to pick up this new imaginary writing job after my traditional office.</p><h4><strong>A few new workspace rules —</strong></h4><ul><li>No professional obligations to be polite.</li><li>No need to be punctual. It forgives me even if I skip a writing day.</li><li>No boring leadership meetings.</li><li>No fights for promotion. No b*tt licking.</li><li>No expectations, No salary hike, No fear of getting laid off.</li></ul><p>Pure FUN.</p><p>This writing job liberates me. Period.</p><p>This is the job I always wanted. No restrictions. I can write whatever I want, whenever I want, and wherever I want.</p><p>It makes me feel alive. The same feeling I had when I was in my childhood.</p><p>I am not color-blinded anymore in this virtual cubicle. Rainbows around me. The sunset looks even more dramatic than usual.</p><p>Some days, I do not even have a topic to write about. But my fingers are itching to hit the silent keyboard, begging me to come up with a topic, even a fake one.</p><p>So I write one for them. I discover a new topic and read about it.</p><p>Once I have the inspiration and content in mind, I let my fingers feed on them and create words.</p><p>Write and write and write. I write for my soul. I write to get a goosebump. I write to create something that is personal to me. Only mine.</p><p>50 words</p><p>100..</p><p>200..</p><p>500 words.</p><p>Liberation! Silence! Salvation! Happiness!</p><p>It’s time to leave now. I switch off the lights. Time to sleep.</p><p><em>If you also share the same thoughts, please clap or leave a comment.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2061f72b34b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/illumination/does-writing-liberate-you-2061f72b34b5">Does Writing Liberate You?</a> was originally published in <a href="https://medium.com/illumination">ILLUMINATION</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I learnt in past 7 days on Medium]]></title>
            <link>https://medium.com/illumination/what-i-learnt-in-past-7-days-on-medium-1743c3d7af74?source=rss-3559b5c3008b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1743c3d7af74</guid>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[writer]]></category>
            <category><![CDATA[earn]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[earn-money-online]]></category>
            <dc:creator><![CDATA[Pratish]]></dc:creator>
            <pubDate>Tue, 24 Sep 2024 05:42:27 GMT</pubDate>
            <atom:updated>2024-09-24T05:42:27.321Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s too obvious!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x_UWpgMuY17223E5Q5VaMg.jpeg" /><figcaption>Generated by Dall-E</figcaption></figure><p>If you want to be a top writer on Medium, you need to —</p><ul><li><strong>Write daily</strong></li><li><strong>Read, but with a pinch of salt</strong></li><li><strong>Experiment &amp; Learn</strong></li><li><strong>Find your niche</strong></li></ul><h4>#1 Write Daily</h4><p>99% writers quit after 3 months.</p><p>Why? They get disheartened by the vicious negative feedback loop.</p><p>0 Views<br>1 Clap<br>$0.2 Earnings</p><p>But the real success is in showing up daily.</p><p>Writing is a marathon, not a quick sprint. You will likely fall down with knee cramps and bruises. The winner is the one who keeps the head up and ignores the bleeding knee.</p><p>Start slow and take out 15 minutes everyday to write about anything that pops up in your mind—</p><ul><li>The cat which shows up daily at your front door</li><li>Humor and climate change</li><li>AI and endangered human identity</li><li>Any random thought…</li></ul><h4>#2 Read, but with a pinch of salt</h4><p>Most of us think that reading a lot will make us a better writer.</p><p>Guess what? Reading 30 self-help books will not make you a (good) writer.</p><p>Read to achieve target goals</p><ul><li>I read NYTimes to accelerate my vocabulary.</li><li>I read content of top Medium writers to get better at online writing.</li></ul><p>The real learning is when you start writing and experimenting with new ideas and topics.</p><p>I know writers who sucked at Creative English when they started. Now, with writing consistency and selective learning, they have created their own identity in writing space.</p><h4>#3 Experiment and Learn</h4><blockquote>Only those who will risk going too far can possibly find out how far one can go — TS Eliot</blockquote><p>Experimentation is the bread and butter of an online writer.</p><p>Discover new ideas, and apply them to writing. Observe how popular writers structure their posts.</p><ul><li>Do they use sub-headings too frequently?</li><li>Are the paragraphs short , long, or mix of both?</li><li>Are titles and subtitles trying to talk about a problem?</li></ul><p>Get inspirations and implement some of those. Find out what works for your audience.</p><p>Target getting 1% better everyday.</p><p>Another way to discover ideas are by reading books on online writing. A few I loved reading in the past are—</p><ul><li><a href="https://www.goodreads.com/book/show/55189231-the-art-and-business-of-online-writing">The Art and Business of Online Writing</a></li><li><a href="https://www.goodreads.com/book/show/53343.On_Writing_Well">On Writing Well: The Classic Guide to Writing Nonfiction</a></li></ul><h4>#4 Find your niche</h4><p>You need to find the <em>IKIGAI </em>that defines your purpose for writing.</p><p>Write about something that makes you YOU. Who are you?</p><ul><li>Are you a bada** outer space storyteller?</li><li>Or, a technical writer with cultural fusion?</li><li>Or, maybe a creative dark humor poet?</li></ul><p>If you haven’t found your writing space, now is the time to get creative with your thoughts and write about them.</p><p>Write as much as you can on the topics you love. Pour your heart out on the canvas. Find your niche!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1743c3d7af74" width="1" height="1" alt=""><hr><p><a href="https://medium.com/illumination/what-i-learnt-in-past-7-days-on-medium-1743c3d7af74">What I learnt in past 7 days on Medium</a> was originally published in <a href="https://medium.com/illumination">ILLUMINATION</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is your IDENTITY evolving with Bioconvergence?]]></title>
            <link>https://medium.com/illumination/bioconvergence-and-new-human-identity-9f0855cde3e0?source=rss-3559b5c3008b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f0855cde3e0</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[identity]]></category>
            <dc:creator><![CDATA[Pratish]]></dc:creator>
            <pubDate>Sat, 21 Sep 2024 22:47:18 GMT</pubDate>
            <atom:updated>2024-09-22T16:56:48.167Z</atom:updated>
            <content:encoded><![CDATA[<h4>What does it mean to be human?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*cmzMx17or6B8nbRm4xmt6g@2x.jpeg" /></figure><p><strong>Bio-convergence on humans</strong> is the dynamic fusion of biology and cutting-edge technology — melding AI, robotics, and genetics to amplify human potential.</p><p>The lightning pace of breakthroughs like Neuralink’s mind-powered interfaces and AI’s mastery of protein mapping pushes us to reimagine <strong>what it truly means to be human</strong>.</p><p>These innovations don’t just challenge our understanding — they’re rewriting the narrative of human identity itself.</p><ul><li><a href="https://nypost.com/2024/09/18/business/elon-musks-neuralink-receives-fdas-breakthrough-device-status-for-blindsight-implant/">Elon Musk&#39;s Neuralink brain chip receives FDA&#39;s &#39;breakthrough device&#39; status - and could help blind people see again</a></li><li><a href="https://deepmind.google/technologies/alphafold/">AlphaFold</a></li></ul><p>For centuries, human identity has been rooted in our biology and the <strong>independence of our minds</strong>. But as AI and biotechnology surge forward, the once-clear lines that define what it means to be “human” are dissolving.</p><p>With the rapid expansion of these industries, the essence of humanity is becoming more fluid, reshaping faster than ever before.</p><blockquote><strong>The global healthcare bioconvergence market size accounted for USD 120.89 billion in 2022 and it is expected to hit over USD 259.55 billion by 2032, growing at a CAGR of 7.94% over the forecast period from 2023 to 2032. — </strong><a href="https://www.precedenceresearch.com/healthcare-bioconvergence-market"><strong>Precedence Research</strong></a></blockquote><p>Neuralink’s breakthrough, where minds control machines with mere thoughts, shatters our long-held notions of agency and autonomy. No longer is the human body the only vessel for action; our very cognition is now bleeding into the digital world.</p><h3>This raises important questions: If technology can act as an extension of our minds, does it become part of our identity?</h3><p>The rise of bio-convergence in Israel raises the same profound philosophical questions about the essence of life and our role within it. As we develop technologies like 3D-printed tumors and phage therapies, we shift from passive observers to active shapers of biology. This prompts us to consider:</p><h3>If we can engineer life, what does it mean to be alive?</h3><p><a href="https://pubs.aip.org/aip/jap/article/135/14/140701/3281997/Recent-advances-in-3D-printing-for-in-vitro-cancer">Recent advances in 3D printing for in vitro cancer models</a></p><ul><li>Are we enhancing human experience, or risking its authenticity by reducing life to programmable elements?</li><li>At what point does the boundary between the “natural” human and the artificial enhancement dissolve?</li></ul><p>These questions touch on deeper concerns about individuality and control — if our thoughts can interface with machines, how do we safeguard against external manipulation or loss of autonomy?</p><p>Ultimately, the choices we make will redefine our understanding of humanity, urging us to reflect on how we honor the complexities of life while embracing the promise of technological advancement. This convergence of AI and biology hints at a future where identity is no longer strictly defined by our biology or cognitive boundaries.</p><blockquote>We are moving toward a post-human world where technology and biology are so interwoven that the very essence of<strong> “self” </strong>becomes more fluid.</blockquote><p>Peace.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f0855cde3e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/illumination/bioconvergence-and-new-human-identity-9f0855cde3e0">Is your IDENTITY evolving with Bioconvergence?</a> was originally published in <a href="https://medium.com/illumination">ILLUMINATION</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 mistakes beginners make in React useState hook]]></title>
            <link>https://medium.com/betterreact/3-mistakes-beginners-make-in-react-usestate-hook-45d980e33905?source=rss-3559b5c3008b------2</link>
            <guid isPermaLink="false">https://medium.com/p/45d980e33905</guid>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[react-hook]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Pratish]]></dc:creator>
            <pubDate>Sat, 14 Sep 2024 22:43:33 GMT</pubDate>
            <atom:updated>2024-09-14T22:43:33.515Z</atom:updated>
            <content:encoded><![CDATA[<p>Be a better React Dev!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H2vt_8n6_Pgj3yFPgqZFAA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mael_balland?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Maël BALLAND</a> on <a href="https://unsplash.com/photos/person-holding-blue-and-black-fishing-baits-ZWF1DVAXXLY?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p>Learning React might feel like skimming the surface of a calm sea. Watch a one-hour tutorial, and you’re off — building components, styling with ease, and thinking, <em>“This is simple!”</em> But don’t be fooled by the calm waters. Beneath the surface lies an ocean of complexities, side effects lurking like unseen currents.</p><p><em>You won’t notice it at first. State updates flow smoothly, components render effortlessly, and everything seems harmonious — until, out of nowhere, it hits you: unexpected bugs, performance issues, and re-renders spiraling out of control.</em></p><h3>1. Stale State in Closures</h3><p>Imagine wiring up a button to an event handler that increments a counter. Simple, right? 😎 But here’s the catch: every time you press the button, the event handler may not be working with the most up-to-date version of the counter. Instead, it’s relying on an old copy of the count state.</p><pre>function Counter() {<br>  const [count, setCount] = useState(0);<br><br>  const handleClick = () =&gt; {<br>    setTimeout(() =&gt; {<br>      setCount(count + 1); // This may use stale `count` value.<br>    }, 1000);<br>  };<br><br>  return &lt;button onClick={handleClick}&gt;Increment: {count}&lt;/button&gt;;<br>}</pre><p>📢 What happens as a result? The number of clicks and the displayed counter value start falling out of sync. You keep pressing the button, expecting the count to climb steadily, but the number on the button lags behind or <strong>updates inconsistently</strong>.</p><p>This mismatch occurs because <strong>React’s state updates are asynchronous </strong>💡, and the handler might be holding on to a <strong>stale snapshot </strong>of the count.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/1*QN5ULuq0d9J3yeT1-IiB4Q.gif" /><figcaption>Image by author</figcaption></figure><p>To ensure that the event handler always gets the latest state, you need to use <strong>a functional update</strong>. This way, the state is recalculated based on the most current value, keeping the button’s display and the actual counter perfectly in sync.✌</p><pre>function Counter() {<br>  const [count, setCount] = useState(0);<br><br>  const handleClick = () =&gt; {<br>    setTimeout(() =&gt; {<br>      setCount(prevCount =&gt; prevCount + 1); // Use functional update to avoid stale state.<br>    }, 1000);<br>  };</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/0*L5QOQ7plHx5j3SXe.gif" /><figcaption>Image By Author</figcaption></figure><h3>2. Updating the state inside the render</h3><blockquote>Changing the DOM directly in the render phase is like trying to paint a canvas while it’s still being prepared. 👀</blockquote><p>It disrupts React’s efficient update process, leading to inconsistencies and performance issues. Let React handle DOM updates by returning JSX and <strong>avoid direct DOM manipulation during render </strong>for a smooth and reliable UI.</p><p>If you update the state directly inside your render method or a body of a functional component, it will cause an infinite loop.</p><pre>function App() {<br>  const [count, setCount] = useState(0);<br><br>  setCount(1); // infinite loop<br><br>  return ...<br>}</pre><p>Do you want to update a state only one time when the component mounts? Use useEffect with an empty array as a dependency.</p><pre>function App() {<br>  const [count, setCount] = useState(0);<br><br>  useEffect(() =&gt; {<br>    setCount(1);<br>  }, [])<br><br>  return ...<br>}</pre><p>This useEffect hook runs once after the component has been mounted (since it has empty dependency array []). 🌏</p><p><a href="https://medium.com/betterreact/understanding-useeffect-a-complete-guide-to-reacts-side-effect-hook-4aed18bf424b">Understanding useEffect: A Complete Guide to React&#39;s Side Effect Hook</a></p><h3>3. Saving Function Identity in useState</h3><p>When you store functions in state or pass them as dependencies to hooks, React uses strict equality checks (===) to determine if something has changed. If the function reference changes, React assumes the function has been altered and may cause unnecessary re-renders or effect executions.</p><h4>Example</h4><p>Consider a component that stores a function (prints Hello)in state and uses it in useEffect.</p><pre>function Example() {<br>  const [callback, setCallback] = useState(() =&gt; () =&gt; console.log(&#39;Hello&#39;));<br><br>  useEffect(() =&gt; {<br>    callback(); // Effect runs every time `callback` changes<br>  }, [callback]);<br><br>  const updateCallback = () =&gt; {<br>    setCallback(() =&gt; () =&gt; console.log(&#39;Updated Hello&#39;));<br>  };<br><br>  return &lt;button onClick={updateCallback}&gt;Update Callback&lt;/button&gt;;<br>}</pre><p>In this example:</p><ul><li>Here, callback is initialized with a function that logs &#39;Hello&#39;. This function is stored in the component&#39;s state. ⛵</li><li>useEffect depends on callback. This means that whenever callback changes, the effect will run and execute the function callback(). Initially, this will log &#39;Hello&#39;.</li><li>🔁 When the button is clicked, updateCallback is called. This updates the callback state to a new function that logs &#39;Updated Hello&#39;.</li><li>Clicking this button triggers the updateCallback function, which sets a new function in the state.</li></ul><p>Each render creates a new function reference for callback, 💩 which causes useEffect to execute again. This might lead to unnecessary re-renders or effect executions.</p><h4>Fix 💎</h4><p>To avoid recreating function references on each render, you should use useCallback to <strong>memoize functions</strong>. This ensures that the function reference remains stable unless its dependencies change.</p><pre>import React, { useState, useCallback, useEffect } from &#39;react&#39;;<br><br>function Example() {<br>  const [callback, setCallback] = useState(() =&gt; () =&gt; console.log(&#39;Hello&#39;));<br><br>  const memoizedCallback = useCallback(() =&gt; {<br>    console.log(&#39;Updated Hello&#39;);<br>  }, []); // Add dependencies if needed<br><br>  useEffect(() =&gt; {<br>    callback(); // Effect runs every time `callback` changes<br>  }, [callback]);<br><br>  const updateCallback = () =&gt; {<br>    setCallback(memoizedCallback); // Use memoized callback<br>  };<br><br>  return &lt;button onClick={updateCallback}&gt;Update Callback&lt;/button&gt;;<br>}</pre><ul><li>memoizedCallback is created using useCallback, ensuring that the function reference remains the same as long as its dependencies (in this case, none) don’t change.</li><li>Instead of creating a new function every time, we use the memoizedCallback to update the state. This preserves the function identity and avoids unnecessary re-renders or effects. 🥳</li></ul><p>Thanks for reading. If you loved the content, if you have more questions, leave them in the comments. I will try to reply back within an hour.</p><p>Follow <a href="https://medium.com/betterreact">BetterReact </a>for more on React.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45d980e33905" width="1" height="1" alt=""><hr><p><a href="https://medium.com/betterreact/3-mistakes-beginners-make-in-react-usestate-hook-45d980e33905">3 mistakes beginners make in React useState hook</a> was originally published in <a href="https://medium.com/betterreact">BetterReact</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guide to useEffect hook in React]]></title>
            <link>https://medium.com/betterreact/understanding-useeffect-a-complete-guide-to-reacts-side-effect-hook-4aed18bf424b?source=rss-3559b5c3008b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4aed18bf424b</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[useeffect]]></category>
            <category><![CDATA[react-hook]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[reactjs]]></category>
            <dc:creator><![CDATA[Pratish]]></dc:creator>
            <pubDate>Sun, 08 Sep 2024 18:37:28 GMT</pubDate>
            <atom:updated>2024-09-16T19:38:44.843Z</atom:updated>
            <content:encoded><![CDATA[<p>Be a better React dev!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OveU2nR4yuMDTwRCI9yMXA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@felipesantana?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Felipe Santana</a> on <a href="https://unsplash.com/photos/pink-flower-garden-JLLjPytm9go?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><blockquote>If React components were characters in a play, useEffect would be the versatile stagehand, silently working behind the scenes, handling all the necessary side tasks to keep the performance running smoothly.</blockquote><p>From data fetching to event listeners, useEffect is your go-to tool when you need to interact with the outside world—beyond the familiar render loop of React. It&#39;s the bridge that connects your clean React components to the noisy real world of APIs, timers, and dynamic UI interactions.</p><p>But don’t be fooled by its quiet presence. useEffect is as powerful as it is subtle. When wielded correctly, it transforms your components from static elements into dynamic, responsive parts of a living app. Let’s take a journey into this magic and unlock its full potential.</p><h4>The Basics: useEffect at a Glance</h4><p>At its core, useEffect is a hook that runs your side effects after React updates the DOM. That means it’s designed to handle things that need to happen after the component renders—like fetching data, subscribing to a service, or manually tweaking the DOM.</p><p>Here’s the simplest useEffect structure:</p><pre>useEffect(() =&gt; {<br>  // Side effect code here<br>  return () =&gt; {<br>    // Cleanup code here (optional)<br>  };<br>}, [dependencies]);</pre><ul><li>The <strong>effect function</strong> does the actual work — whether it’s fetching data, updating the page title, or listening for an event.</li><li>The <strong>dependency array</strong> is where the magic happens. It tells React when to re-run the effect, keeping things efficient and responsive.</li><li>useEffect can return a <strong>cleanup</strong> function that runs before the component is removed from the DOM or before the effect re-runs due to a change in dependencies. This is useful for things like clearing timers or unsubscribing from event listeners.</li></ul><h3>Four Different Uses You Need to Know</h3><h4>No Dependencies? Infinite Loops of Action!</h4><p>What happens when you leave out the <strong>dependency</strong> array? useEffect becomes a hyperactive sidekick, running after <strong>every single render, </strong>which can cause performance issues if the effect is expensive. This can be useful for something you want to check on every update, but it’s rarely what you need.</p><pre>useEffect(() =&gt; {<br>  console.log(&quot;Running on every render!&quot;);<br>});</pre><p>Imagine you’re setting up a live event that re-fires every time the curtain lifts — no matter how small the scene. Overkill, right? Use this with caution!</p><h4>Running Once: The Calm Before the Storm</h4><p>Sometimes, you only need your effect to run once — right after the component mounts.</p><blockquote>Think of it as setting the stage before the performance begins. By passing an <strong>empty array</strong> as the second argument, you tell React, “Run this once, and then sit back and enjoy the show.”</blockquote><pre>useEffect(() =&gt; {<br>  console.log(&quot;Running only on component mount&quot;);<br>}, []);  // Empty dependency array</pre><p>It’s perfect for things like API calls that should happen just once, like fetching a user’s profile data as soon as they log in.</p><h4>Tracking Changes: Reacting to Specific Updates</h4><p>But what if you want your effect to run only when certain variables change — like props or state? That’s where useEffect really shines. It allows you to respond to specific changes, re-running only when something important happens.</p><pre>useEffect(() =&gt; {<br>  console.log(&quot;Count updated!&quot;);<br>}, [count]);  // Effect runs only when &#39;count&#39; changes</pre><p>This is like giving useEffect a very clear instruction: “Only take action when <strong>this specific thing</strong> changes.” It’s the cornerstone of making your components dynamic and reactive, yet efficient.</p><h4>Leave No Trace: Cleanup</h4><p>Every good stagehand knows when to step out of the spotlight. And that’s what makes useEffect so useful—it can <strong>clean up</strong> after itself. Whether it’s unsubscribing from an event listener, clearing a timer, or resetting some state, useEffect ensures that your component doesn’t leave a mess when it’s done.</p><pre>useEffect(() =&gt; {<br>  const timer = setInterval(() =&gt; {<br>    console.log(&quot;Running every second...&quot;);<br>  }, 1000);<br><br>  return () =&gt; clearInterval(timer);  // Cleanup<br>}, []);</pre><p>Here, the interval runs, but when the component unmounts (or if the effect needs to be cleaned up before a re-run), React clears the timer for you. Without this, your app might end up with rogue intervals or event listeners, creating potential <strong>memory leaks or unexpected behavior</strong>.</p><h3>Real-World Magic: A Practical Example</h3><p>Let’s get out of the abstract and into the real world. Imagine a dashboard that needs to fetch data about user activities whenever the user’s role changes. useEffect steps in, listening for the role update and then fetching the data.</p><pre>import { useState, useEffect } from &quot;react&quot;;<br><br>const UserActivity = ({ role }) =&gt; {<br>  const [activities, setActivities] = useState([]);<br><br>  useEffect(() =&gt; {<br>    // Fetch activities based on the user&#39;s role<br>    const fetchActivities = async () =&gt; {<br>      const response = await fetch(`/api/activities?role=${role}`);<br>      const data = await response.json();<br>      setActivities(data);<br>    };<br><br>    fetchActivities();<br>  }, [role]);  // Effect runs when &#39;role&#39; changes<br><br>  return (<br>    &lt;div&gt;<br>      &lt;h2&gt;User Activities&lt;/h2&gt;<br>      &lt;ul&gt;<br>        {activities.map((activity) =&gt; (<br>          &lt;li key={activity.id}&gt;{activity.description}&lt;/li&gt;<br>        ))}<br>      &lt;/ul&gt;<br>    &lt;/div&gt;<br>  );<br>};</pre><p>In this case, useEffect is the invisible bridge that connects the changing role with a fresh batch of activities, making sure the data is always up-to-date without redundant re-fetching.</p><h3>Pitfalls of useEffect</h3><ol><li><strong>The Case of Missing Dependencies</strong>: Picture a detective missing key clues — without the right variables in the dependency array, your effect won’t react to changes, leaving your component stuck in the past, unaware of the evolving state.</li><li><strong>The Overstuffed Effect</strong>: Don’t turn your useEffect into a cluttered closet! Cramming too many responsibilities into one effect leads to chaos. Instead, organize your side effects like a well-curated toolkit, with each tool handling a single job.</li><li><strong>The Infinite Loop Trap</strong>: Beware of the loop that never ends! Updating state inside useEffect can trigger endless re-renders if you’re not careful. Always guard your updates with thoughtful dependency management to avoid a never-ending cycle.</li></ol><p>At its heart, useEffect is all about controlling what happens <strong>after</strong> your component renders—giving you the tools to handle everything from fetching data to managing subscriptions. By mastering useEffect, you gain control over the <strong>side effects</strong> of your app, making your React components more powerful, dynamic, and responsive.</p><p>Whether you’re mounting a one-time effect, responding to state changes, or cleaning up after an event, useEffect is your secret weapon in creating efficient, side-effect-driven components. Understanding its nuances will help you craft better apps, ones that not only look great but also perform flawlessly behind the scenes.</p><p>Go ahead! Unleash the power of useEffect</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4aed18bf424b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/betterreact/understanding-useeffect-a-complete-guide-to-reacts-side-effect-hook-4aed18bf424b">Guide to useEffect hook in React</a> was originally published in <a href="https://medium.com/betterreact">BetterReact</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>