<?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 Elif İrem Kara Kadyrov on Medium]]></title>
        <description><![CDATA[Stories by Elif İrem Kara Kadyrov on Medium]]></description>
        <link>https://medium.com/@elfrmkr98?source=rss-f3d0b65da8bb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bh-laFr7jXn5AbTjnFVtSA.jpeg</url>
            <title>Stories by Elif İrem Kara Kadyrov on Medium</title>
            <link>https://medium.com/@elfrmkr98?source=rss-f3d0b65da8bb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:58:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@elfrmkr98/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 Happens When Self-Improvement Becomes Another Way to Hate Yourself]]></title>
            <link>https://medium.com/@elfrmkr98/what-happens-when-self-improvement-becomes-another-way-to-hate-yourself-61658f3f0890?source=rss-f3d0b65da8bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/61658f3f0890</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[wellness]]></category>
            <category><![CDATA[mental-health]]></category>
            <dc:creator><![CDATA[Elif İrem Kara Kadyrov]]></dc:creator>
            <pubDate>Thu, 17 Sep 2026 11:52:52 GMT</pubDate>
            <atom:updated>2026-09-17T11:52:52.834Z</atom:updated>
            <content:encoded><![CDATA[<p><em>When personal growth stops feeling like expansion and begins to feel like self-correction.</em></p><figure><img alt="Picture of a child statue of stone carving himself with tools" src="https://cdn-images-1.medium.com/max/1024/0*MYJBw7juaOuIaEdu" /><figcaption>Photo by <a href="https://unsplash.com/@vikraw?utm_source=medium&amp;utm_medium=referral">Vikram Singh</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There is always something we wish we could do better.</p><p>Manage our time better. Move our bodies more. Read more. Wake up earlier. Waste less of our brief lives. Build better habits. Become more disciplined.</p><p>We want to step into a version of ourselves that feels more… complete.</p><p>There is nothing inherently wrong with that.</p><p>Wanting to grow is one of the most deeply human impulses we have. Sometimes it really is as simple as discovering something you care about, wanting to master it, and showing up for the work.</p><p>But a subtle threshold exists where self-improvement stops feeling like expansion and starts to feel like correction.</p><p>You no longer think,<em> I want to learn this.</em></p><p>You think<em>, I should already know this.</em></p><p>You no longer think, <em>I want to become more organized.</em></p><p>You think, <em>Why am I still such a mess?</em></p><p>From the outside, almost nothing changes. You still read the books, go for the run, check the boxes, and plan your days. You might accomplish more than you did before.</p><p>But internally, the foundation has shifted.</p><p>You are no longer improving because you are curious about who you could become. You are improving because you are uncomfortable with who you are now.</p><h3><strong>Collecting Evidence Against Yourself</strong></h3><p>I have fallen into this trap many, many times.</p><p>I would have one particularly amazing day and suddenly decide that this was the person I was supposed to be all the time.</p><p>One good day to become a blueprint for my entire life.</p><p>I would plan the next day, the next week, sometimes even the next version of myself. I would add things almost as if I were building a character in a game.</p><p>For a while, it felt exciting. I wasn’t just changing my habits. I was becoming <em>the </em>person who finally had it all together.</p><p>Then, reality would intervene. I would get tired. Something unexpected would happen. An evening would disappear. I would miss a workout or two or spend three hours staring at my phone doomscrolling.</p><p>And sometimes, I wouldn’t even know why.</p><p>When there is an obvious reason you couldn’t do something, it is easier to forgive yourself. When there isn’t one, the mind starts filling in the blanks. <em>I’m lazy. I’m inconsistent. I could be so much more if I just tried harder.</em></p><p>Instead of asking, <em>Was this plan reasonable?</em>, I would ask, <em>Why can’t I ever stick to anything?</em></p><p>The routine that was supposed to improve my life had become a courtroom where I am both the prosecutor and the judge, systematically collecting evidence of my own inadequacy.</p><p>I think this is where self-improvement becomes particularly dangerous. We tend to build our expectations around our best days and then judge ourselves by them on our worst ones.</p><p>We plan for the version of ourselves who slept well, had energy, felt motivated, had no unexpected problems, and could focus for hours. Someone who never gets tired, never grieves, and never collapses onto the couch at 8 PM eating cereal straight out of the box because work was a nightmare. So when reality disrupts the plan, we blame our character instead of questioning the architecture.</p><p>But sometimes the problem isn’t that we lack discipline. Sometimes the plan was built for a person with a different amount of capacity. And capacity is not always visible.</p><h3>But isn’t wanting to be better a good thing?</h3><p>Of course it is.</p><p>That’s what makes this complicated.</p><p>Not every desire to improve comes from self-hatred. Ambition, curiosity, and genuine enjoyment are healthy drivers. Dissatisfaction isn’t inherently destructive. Sometimes being unhappy with something is exactly what we need for a change.</p><p>The problem isn’t wanting more from ourselves. The problem is making <em>more</em> a condition for being worthy of our own respect.</p><p>There is a difference between saying, <em>I want to get better at this because it matters to me.</em></p><p>And saying, <em>I need to get better at this because who I am right now is not acceptable.</em></p><p>The actions might look the same. The difference is what happens when you fail. If I miss a day and think, <em>That’s okay. I’ll try again tomorrow;</em> it’s healthy. If I miss a day and immediately think, <em>Of course I failed again. I never follow through with anything,</em> then maybe the goal has become something else.</p><p>The question isn’t simply, <em>Am I improving? </em>It is also: <em>What do I say to myself when I don’t?</em></p><h3>More, and more, and more</h3><p>There is another problem with self-improvement when it becomes tied to self-worth. There is no natural stopping point.</p><p>There will always be another habit to build, weakness to fix, skill to learn, and a person to compare yourself with. We can always find something to improve. This makes it frighteningly easy to postpone satisfaction indefinitely.</p><p><em>I’ll finally feel proud when I’ve become the person I know I can be. </em>But what happens when we get there? Often, there is simply another goal waiting. The finish line moves.</p><h3>Maybe the Goal Needs to Change</h3><p>I’ve started thinking that perhaps the questions we ask ourselves matter as much as the goals we set.</p><ul><li><em>Do I actually want this, or have I convinced myself that I should want it?</em></li><li><em>Would this fit into the life I actually have, or only the life I imagine I should have?</em></li><li><em>What happens when I can’t keep up?</em></li></ul><p>And perhaps the most important one:</p><ul><li><em>Can I pursue this goal without making my worth dependent on achieving it?</em></li></ul><p>We don’t have to abandon ambition or stop trying. Skipping a workout doesn’t make you lazy, and a chaotic week isn’t proof that you’re undisciplined. You aren’t losing some invisible race just because someone else is moving faster. A period when you accomplish less does not mean you have become less.</p><p>A good day is not a contract. A bad day is not a confession. Sometimes your capacity is simply different today. Sometimes a routine doesn’t work.</p><p>Useful data, maybe. But definitely not a verdict on who you are.</p><p>If improvement comes from genuine interest, it stays flexible. We can experiment, adjust, fail, or decide a goal is no longer relevant. We can change the plan without turning on the person who couldn’t follow it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61658f3f0890" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Slow Down. Life is Happening While We Hurry]]></title>
            <link>https://medium.com/@elfrmkr98/slow-down-life-is-happening-while-we-hurry-2f858f2f07d5?source=rss-f3d0b65da8bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f858f2f07d5</guid>
            <category><![CDATA[wellness]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Elif İrem Kara Kadyrov]]></dc:creator>
            <pubDate>Wed, 26 Aug 2026 15:52:07 GMT</pubDate>
            <atom:updated>2026-08-26T15:52:07.881Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A woman standing by a window while watching outside" src="https://cdn-images-1.medium.com/max/1024/0*2Ikz7Avg3lxMThjP" /><figcaption>Photo by <a href="https://unsplash.com/@cristina_gottardi">Cristina Gottardi</a> on Unsplash</figcaption></figure><p>Somewhere along the way, we started treating every moment as if it were leading to something more important than itself.</p><p>We hurry through the streets as if the destination always matters more than the place we are already in. We eat too quickly. We brush our teeth too hard, rush through conversations, and glance at the clock more often than we look out the window. Even our rest has to be productive somehow. If we’re sitting still, we feel guilty, like we’re falling behind.</p><p>It’s strange how urgency can become such a habit that we stop questioning it. We wake up already thinking about what’s next. We finish one chapter only to start worrying about the next one immediately. Every achievement quietly becomes the starting point for the next thing we feel we must prove. We keep telling ourselves that once we finish this week, this project, this semester, this phase of life, we’ll finally slow down. But somehow, “later” keeps moving further away.</p><p>The <em>rush </em>changes the way we experience the world. We become impatient with people we love. Small inconveniences feel much bigger than they are. We get frustrated by red lights, slow walkers, long lines, the messages that take too long to answer. We stop paying attention to the songs playing in the background or the way the evening light falls across a room. We become so focused on getting somewhere that we forget there is life happening along the way.</p><p>I notice this in myself more often than I would like to admit. I catch myself feeling impatient during moments that don’t actually require speed. Waiting for a page to load, standing in line for coffee, walking somewhere familiar…</p><p>It is strange how easily we can turn even ordinary moments into things we need to get through.</p><p>Maybe that’s why so many days seem to blur together. Because we were only partially there for so much of it. Our attention is always somewhere else: tomorrow, next week, the next goal, the next responsibility. We’re physically here, but mentally we’re already leaving.</p><figure><img alt="Busy city terminal/ rushing through life" src="https://cdn-images-1.medium.com/max/1024/0*qAoJZpj8sVWJIDoM" /><figcaption>Photo by <a href="https://unsplash.com/@smee85?utm_source=medium&amp;utm_medium=referral">Sebastian Meier</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Of course, life isn’t always slow. Some seasons of life are meant to be carried, not savored. There are bills to pay, people to care for, losses to survive. Slowing down doesn’t mean escaping responsibility. It means remembering that responsibility is something we carry through life, not something that should consume it.</p><p>The strange thing about rushing through life is that we often do it because we want more of it. We hurry because we want to achieve more, experience more, become more. But somewhere along the way, we forget that the moments we are rushing through are also the life we are trying so hard to build.</p><p>When we slow down, we don’t discover a different life. We finally notice the one that was already there. This day, no matter how ordinary it feels, is still a part of your life. And life is made of these small pieces. Not the future we are always chasing, but the present we are already standing inside.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f858f2f07d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Engineering Taught Me a Better Way to Fail]]></title>
            <link>https://code.likeagirl.io/software-engineering-taught-me-a-better-way-to-fail-4f74580ff5d0?source=rss-f3d0b65da8bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f74580ff5d0</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Elif İrem Kara Kadyrov]]></dc:creator>
            <pubDate>Tue, 14 Jul 2026 01:42:45 GMT</pubDate>
            <atom:updated>2026-07-14T01:42:45.057Z</atom:updated>
            <content:encoded><![CDATA[<p>Every time I write, refactor, or merge code, I <strong>expect </strong>something to break.</p><p>I don’t stare at the screen when something eventually goes wrong, thinking, <em>“I’m a terrible developer.”</em></p><p>Instead, I think, <em>“Interesting. What did I miss?” or “Which part didn’t work exactly?”</em></p><h3>The Process of Debugging</h3><p>What do I do when I get an error?</p><p>Sometimes the mistakes are very simple, like overlooked typos or faulty conditions.</p><p>Annoying, but generally easy to fix.</p><p>Sometimes they are complicated. Maybe not even reproducible and occasionally occurring.</p><p>There can be thousands of ways to cause an error.</p><p>The important thing is, my brain doesn’t immediately jump to <em>“I’m a terrible engineer” </em>when something breaks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T1hKQi4_WDmwPLo_gfBQhw.png" /><figcaption>Image of a woman developer debugging code— ChatGPT</figcaption></figure><p>I take a breath and do what developers do:</p><ul><li>Look at the error/logs</li><li>Compare the recent changes</li><li>Retracing steps</li><li>Form a hypothesis</li><li>Test the hypothesis</li><li>Repeat till it works</li><li>If all else fails, ask for help</li></ul><p>This process has not yet failed me. The profession is built on this.</p><p>We anticipate problems, which is exactly why debugging exists.</p><h3>When Things Don’t Go the Way We Want in Life</h3><p>I’ve noticed something interesting: I often don’t apply the same logic to my own life that I use in coding. When I fail to accomplish something or feel like I’m not performing well, I tend to engage in self-blame. I often assume it’s my own shortcomings or lack of motivation, rather than taking the time to analyze the situation and understand what went wrong.</p><p>Somewhere between my coding environment and my everyday life, I seem to have forgotten the methodical approach I rely on to solve problems. What happened to that structured plan I use to address challenges?</p><p>Well… when the code breaks, I don’t feel like <em>I </em>am broken. The problem exists outside of me. It is something I can observe, understand, and work on. But when something goes wrong in my own life, that distance disappears.</p><p>I realized I saw difficult moments as evidence that something was wrong on my part. A missed goal felt like proof that I wasn’t disciplined enough.</p><p>I was skipping the part where I investigate. I was skipping the questions that help me understand the root cause.</p><p><em>“What was the main issue?”</em></p><p><em>“What can I try differently next time?”</em></p><p>The same curiosity that helps me solve problems every day tends to disappear when the problem is my own.</p><p>Maybe that’s because our lives are much harder to debug than our code. There is no clear error message indicating where and what went wrong. Emotions, memories, fears, and expectations are all intertwined in the situation. However, I realized that the same process may still be applicable.</p><p>Here are my takeaways:</p><ul><li>I will try not to judge myself before understanding the problem.</li><li>I will remind myself that, as a human being, it is okay to make mistakes.</li><li>I am not gonna assume that the only culprit is me.</li><li>I am not gonna treat every mistake as a reflection of who I am.</li></ul><p>Software engineering has taught me that problems are not failures. They are invitations to investigate.</p><p>The next time something in my life isn’t working, I want to stop asking:</p><p><em>“What’s wrong with me?”</em></p><p>And start asking the question I have asked countless times while debugging code:</p><p><em>“Where should I start looking?”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f74580ff5d0" width="1" height="1" alt=""><hr><p><a href="https://code.likeagirl.io/software-engineering-taught-me-a-better-way-to-fail-4f74580ff5d0">Software Engineering Taught Me a Better Way to Fail</a> was originally published in <a href="https://code.likeagirl.io/">Code Like A Girl</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our Brains Are Adaptation Machines. And It’s Hurting Us.]]></title>
            <link>https://medium.com/illumination/our-brains-are-adaptation-machines-and-its-hurting-us-fba29e518b58?source=rss-f3d0b65da8bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/fba29e518b58</guid>
            <category><![CDATA[mindfulness]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Elif İrem Kara Kadyrov]]></dc:creator>
            <pubDate>Mon, 29 Jun 2026 13:04:54 GMT</pubDate>
            <atom:updated>2026-06-29T13:04:54.924Z</atom:updated>
            <content:encoded><![CDATA[<p>Our brains are adaptation machines.</p><p>We tend to neutralize whatever we repeat.</p><p>Because once they are integrated into the fabric of our lives, they are separated from their emotional weight.</p><p>You don’t get stressed over the things you do every day. They cost you zero mental bandwidth.</p><h3>1. The Good Side: Erasing the Friction</h3><p>Our minds are incredibly trickable. When you look at a massive goal, it feels like a mountain. It feels like a huge chore. But when you break it down into something you do <em>every single day</em>, the mountain flattens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QHKKH4Pbx_QBmy-y" /><figcaption>Photo by <a href="https://unsplash.com/@danielleone?utm_source=medium&amp;utm_medium=referral">Daniel Leone</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The first time you exercise, it will feel exhausting.</p><p>The first time you sit in silence for five minutes, your brain will fight you to fill the stillness.</p><p>The first time you go for a walk instead of scrolling, it will be a drag.</p><p>But by day 50? 80? It’s just what you do at 8:00 AM, 3:00 PM, and at midnight. Repetition is the ultimate antidote to fear and friction.</p><p>What was once difficult becomes <strong><em>expected</em></strong>. What was once stressful becomes routine.</p><p>There is a beautiful quote from one of my favorite comfort shows, spoken by the character Shinsuke Kita.</p><blockquote>“I am basically built upon the small things I do every day, and the end results are no more than a byproduct of that.”</blockquote><p>The real transformation happens long before the result arrives. It happens in daily practice. In the repeated action... In the ordinary moments that nobody notices…</p><h3>2. The Double-Edged Sword: When We Normalize the Bad</h3><p>But this psychological superpower is a double-edged sword. Just as we can habituate ourselves to ease, we can easily habituate ourselves to suffering.</p><p>If you smoke every day, drink every day, doomscroll for three hours every night, or live in a constant state of fight-or-flight, your brain adapts to that, too. It becomes your new normal.</p><p>That doesn’t mean they’re harmless.</p><p>It only means we’ve gotten used to carrying them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZoPtAcIaEj4ZEgNG" /><figcaption>Photo by <a href="https://unsplash.com/@wilhelmgunkel?utm_source=medium&amp;utm_medium=referral">Wilhelm Gunkel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This is the tragedy of human adaptability. We can learn to tolerate carrying a crushing weight every day, convincing ourselves that <em>“this is just life.”</em></p><p>But we weren’t built to carry a heavy burden as a baseline. We weren’t created to live without sunlight, trapped in a loop of digital anxiety, fear, and physical neglect.</p><h3>3. Rewriting Who You Are</h3><p>If we are what we repeatedly do, then we have the power to rewrite who we are.</p><p>What changes a life is accumulation.</p><p>If you want to change your life, don’t look for a massive, dramatic overhaul. Look at your Tuesday morning. Look at your Thursday evening. What are you normalizing?</p><p>By intentionally choosing what we repeat, we can slowly shift our baseline. We can turn the things that heal us — walking, breathing, creating — into things that are as effortless and as beautifully boring as brushing our teeth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x6GHtNFxcXtf3p9p" /><figcaption>Photo by <a href="https://unsplash.com/@danielhering?utm_source=medium&amp;utm_medium=referral">Daniel Hering</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Because one day, whatever you do every day will no longer feel like something you have to force yourself to do.</p><p>It will simply feel like you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fba29e518b58" width="1" height="1" alt=""><hr><p><a href="https://medium.com/illumination/our-brains-are-adaptation-machines-and-its-hurting-us-fba29e518b58">Our Brains Are Adaptation Machines. And It’s Hurting Us.</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[How to Use Debounce and Throttle to Build Faster Web Apps]]></title>
            <link>https://javascript.plainenglish.io/how-to-use-debounce-and-throttle-to-build-faster-web-apps-d1643b4fefe3?source=rss-f3d0b65da8bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1643b4fefe3</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Elif İrem Kara Kadyrov]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 11:30:55 GMT</pubDate>
            <atom:updated>2026-06-04T11:30:55.651Z</atom:updated>
            <content:encoded><![CDATA[<p>In modern web development, we often deal with events that fire rapidly. Think of scrolling, typing in a search bar, window resizing, etc. If a heavy function (like an API call) is attached to these events, it may significantly impact browser performance.</p><p><strong><em>Debounce</em></strong><em> </em>and <strong><em>Throttle</em></strong><em> </em>are two techniques used to control how many times a function is executed over time. They are <a href="https://www.freecodecamp.org/news/higher-order-functions-in-javascript-explained/">higher-order functions</a> that take a function as an argument and return a new, controlled version of it.</p><p><strong>Note:</strong> In a professional production environment, it’s standard practice to use a reliable library like <strong><em>Lodash </em></strong>or <strong><em>Underscore </em></strong>for implementing these patterns. While understanding the mechanics is important for interviews and essential logic, these libraries address complex edge cases, helping you avoid unexpected bugs.</p><h3>The Problem: Event Overload</h3><p>Imagine a search bar. As a user types “JavaScript,” the input event fires 10 times. Without control, your app might send 10 separate API requests to your server in under a second, which is inefficient and expensive.</p><p>Similarly, when a user scrolls down a page, the scroll event can fire hundreds of times. This can lead to a laggy experience for users as the browser struggles to keep up.</p><p>So, what can we do about these?</p><h4>Debouncing: Wait for the Pause</h4><p><a href="https://developer.mozilla.org/en-US/docs/Glossary/Debounce">Debouncing </a>is a programming context where, if operations occur too rapidly, the function is only executed after a specified amount of time has passed since it was last invoked.</p><p>Think of it as the elevator in your building. When the door is about to close, but someone walks in, the timer resets. The elevator only moves once people stop getting in for a few seconds.</p><p><strong>Real Life Use Cases:</strong></p><ul><li><strong>Search Bar Autocomplete:</strong> Wait until the user stops typing to fetch results.</li><li><strong>Form Validation:</strong> Validate an email address only after the user pauses.</li><li><strong>Window Resize:</strong> Recalculate layout only when the user finishes dragging.</li></ul><p>Basic JavaScript implementation could be like this:</p><pre>function debounce(func, delay) {<br>  let timer;<br>  return function(...args) {<br>    clearTimeout(timer);<br>    timer = setTimeout(() =&gt; {<br>      func.apply(this, args);<br>    }, delay);<br>  };<br>}</pre><p>This implementation uses a <strong>closure(</strong>a feature where an inner function remembers and has access to variables from its outer function’s scope<strong>) </strong>to keep track of a timer variable across multiple function calls.</p><p>Every time the returned function is triggered, it clears the previous timer and starts a new one. The original function only actually runs if the user stops triggering the event long enough for the setTimeout to finish its countdown.</p><p>And for the library implementation:</p><pre>import { debounce} from &#39;lodash&#39;;<br><br>const handleSearch = debounce((query) =&gt; {<br>  console.log(&quot;Searching for:&quot;, query);<br>}, 300);</pre><h4>Throttling: Stable Execution</h4><p><a href="https://developer.mozilla.org/en-US/docs/Glossary/Throttle">Throttling</a> in programming means limiting a process so that an operation can only occur once at a specified rate, regardless of how many times an event is triggered.</p><p><strong>Real Life Use Cases:</strong></p><ul><li><strong>Infinite Scroll:</strong> Checking the scroll position once every 100ms instead of 1,000 times a second.</li><li><strong>Button Spamming:</strong> Preventing a <em>Submit</em> button from being clicked 20 times in a row.</li><li><strong>Gaming:</strong> Limiting how fast a player can “fire” a weapon.</li></ul><p>Basic JavaScript implementation could be like this:</p><pre>function throttle(func, limit) {<br>  let inThrottle;<br>  return function(...args) {<br>    if (!inThrottle) {<br>      func.apply(this, args);<br>      inThrottle = true;<br>      setTimeout(() =&gt; inThrottle = false, limit);<br>    }<br>  };<br>}</pre><p>The function uses a flag to determine whether it is allowed to run. When the event is triggered, the code only executes if the flag is false<strong>.</strong> It immediately locks the function and starts a timer to unlock it after a specified duration.</p><p>And for the library implementation:</p><pre>import {throttle} from &#39;lodash&#39;;<br><br>const handleScroll = throttle(() =&gt; {<br>  console.log(&quot;Updating scroll position...&quot;);<br>}, 100);</pre><h3>Visualization</h3><p>This <a href="https://css-tricks.com/debouncing-throttling-explained-examples/">blog </a>from CSS-TRICKS provides live demos that show the difference between raw events and debounced/throttled ones as you interact with the codepens.</p><p>Also, <a href="https://css-tricks.com/the-difference-between-throttling-and-debouncing/#demo">this</a> older one has a demo that shows the difference between them in the same snippet.</p><p>I tried to scroll the same amount in all three of them to see the difference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*6RRENllH39z9EQXVi7k3-Q.png" /><figcaption>Image: Comparison of scroll trigger of throttled and debounced events</figcaption></figure><h3>Conclusion</h3><p>Both debouncing and throttling serve essential roles in optimizing application performance, especially when dealing with high-frequency events.</p><p>As a concept, throttling and debouncing are quite similar. The key difference is that throttling limits the operation to a maximum rate, while debouncing delays the execution until there have been no invocations for a specified duration.</p><p>Understanding the mechanics of these patterns allows developers to create more efficient applications by minimizing unnecessary function calls.</p><p>Happy coding, everyone!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1643b4fefe3" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/how-to-use-debounce-and-throttle-to-build-faster-web-apps-d1643b4fefe3">How to Use Debounce and Throttle to Build Faster Web Apps</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning Accessibility (A11y) | Part 2: Focus Order & Management in Dynamic UI]]></title>
            <link>https://medium.com/@elfrmkr98/learning-accessibility-a11y-part-2-focus-order-management-in-dynamic-ui-3adcf2a57170?source=rss-f3d0b65da8bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/3adcf2a57170</guid>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Elif İrem Kara Kadyrov]]></dc:creator>
            <pubDate>Mon, 04 May 2026 08:21:38 GMT</pubDate>
            <atom:updated>2026-05-04T08:21:38.328Z</atom:updated>
            <content:encoded><![CDATA[<p>In case you missed it, <a href="https://medium.com/javascript-in-plain-english/learning-accessibility-a11y-in-javascript-part-01-keyboard-accessible-interactions-ff0bff757ea2">Part 1</a> covers Keyboard-Accessible Interactions.</p><p><strong>A Note on Context:</strong> It is important to remember that “best practice” in accessibility often depends on the specific user journey or the design pattern of the application. The goal is always to create the most predictable and usable experience for <em>your</em> specific interface. Think of the examples below as foundational blueprints that you can adapt to fit your unique use case.</p><h3>Rule: When the UI changes, move the focus to the right place</h3><blockquote><em>When an element is removed from the page or a transition occurs, the focus must be intentionally moved to a logical, nearby location.</em></blockquote><p><strong>The Source: </strong><a href="https://www.w3.org/WAI/WCAG22/Understanding/focus-order.html">WCAG 2.2 — Success Criterion 2.4.3: Focus Order</a></p><h4>Why is it needed?</h4><p>While many people navigate the web via a pointer, those using keyboards or certain screen readers often rely on a <strong>sequential path</strong>. For these users, focus acts as their anchor; they typically move through the interface element by element, following the logical flow you’ve established in your code.</p><p>Imagine you are following a map, and suddenly the map is replaced with a new one, but your finger remains on the previous map below. Without effective focus management, anyone who isn’t using a pointer (like a mouse or touchscreen) can easily lose their place. This issue is more significant than it seems, as it can lead to digital dead ends, preventing someone from completing a purchase, sending a message, or closing a sensitive window.</p><h4>Example: The Navigation Modal</h4><p>Imagine a button that opens a side navigation menu. When a person activates this button, a significant shift occurs in the layout.</p><p>If the focus remains on the button while the menu slides out, it’s like opening a door for a guest but leaving them standing on the porch. Even though the room (the menu) is now open and visible, the person navigating via keyboard or screen reader is still stuck outside.</p><figure><img alt="Gif 1: Demonstraiting navigation via tab with proper focus" src="https://cdn-images-1.medium.com/max/800/0*lnpVYv4hRxtTZRU3.gif" /><figcaption>Gif 1: Demonstraiting navigation via tab with proper focus</figcaption></figure><p>By shifting the focus, we align the visual reality, what is on screen, with the programmatic reality.<strong> </strong>After the menu opens, our focus shifts to the modal&#39;s elements. When a temporary interaction ends, the most intuitive experience is often to return the user to their previous context — usually the trigger button.</p><p>Here is the JavaScript for this functionality:</p><pre>    &lt;script&gt;<br>        const trigger = document.getElementById(&#39;menu-trigger&#39;);<br>        const menu = document.getElementById(&#39;mobile-menu&#39;);<br>        const closeBtn = document.getElementById(&#39;menu-close&#39;);<br><br>        // SAVE THE CONTEXT (The inclusive &quot;Bookmark&quot;)<br>        let lastFocusedElement;<br><br>        trigger.addEventListener(&#39;click&#39;, () =&gt; {<br>            // Remember where the user was<br>            lastFocusedElement = document.activeElement; <br><br>            menu.classList.add(&#39;is-open&#39;);<br>            trigger.setAttribute(&#39;aria-expanded&#39;, &#39;true&#39;);<br><br>            // TAKE USER INTO THE MENU<br>            closeBtn.focus();<br>        });<br><br>        closeBtn.addEventListener(&#39;click&#39;, () =&gt; {<br>            menu.classList.remove(&#39;is-open&#39;);<br>            trigger.setAttribute(&#39;aria-expanded&#39;, &#39;false&#39;);<br><br>            // RETURN THE USER HOME<br>            // Without this, the user is lost at the end of the DOM<br>            if (lastFocusedElement) {<br>                lastFocusedElement.focus();<br>            }<br>        });<br>    &lt;/script&gt;</pre><h4>Why return to the trigger instead of the element after it?</h4><p>Initially, it seems reasonable to move forward after completing the menu; however, there are valid reasons not to do so. Returning focus to the triggering element (the button) is a core requirement of the <strong>W3C WAI-ARIA Authoring Practices</strong> for several critical reasons:</p><ul><li><strong>Predictability:</strong> Imagine you are reading a book and you look up a word in the glossary at the back. When you’re done, you want to put your finger back on the word you were just reading — not the word <em>after</em> it. It’s supposed to be the answer to<em> “Where was I?”.</em> The trigger button is the user’s anchor. If you move them to the next element, you’ve decided for them that they are done with that section, which might not be true.</li><li><strong>Confirmation of Action: </strong>When a person who navigates via a screen reader closes a menu, they need to know that the action was successful. By returning focus to the trigger button, the screen reader will announce the button’s name again (e.g., “Menu, button”). This serves as “You are back where you started, and the menu is now closed.”</li></ul><h4>The Lesson: Beyond “Modal”</h4><p>Focus management is effectively the management of user intent.<strong> </strong>When someone interacts with a menu, they intend to engage with that new content. When they close it, their intent is typically to resume their previous task. By managing this transition, you ensure the interface feels like a continuous, reliable conversation.</p><p>This principle applies to almost any partial page update. Whenever a script adds, removes, or hides content, we should consider where the user’s focus needs to be to keep the experience predictable.</p><p>To help structure this thinking across different types of components, you can use these three steps as a guide:</p><ol><li><strong>Identify the Trigger:</strong> Pinpoint the specific element or action that initiates the change on the screen.</li><li><strong>Determine the Destination:</strong> Where does the user need to be to understand the change? This could be a modal, a newly appeared error message, or the first item in a filtered list.</li><li><strong>Manage the Departure:</strong> If the user leaves that new area, identify where the most logical starting point is for them to return to. (Usually the trigger).</li></ol><h4>Practical Applications</h4><p>This logic should be adapted based on how your specific interface behaves. There is no one-size-fits-all answer, but here are some common patterns:</p><ul><li><strong>Search &amp; Manual Actions:</strong> If a user types a query and then hits an “Apply” or “Search” button, they intend to move to the results. In this case, moving the focus to a <strong>“Results Found” </strong>heading or the first item in the list provides immediate confirmation that the search was successful.</li><li><strong>Live/Auto-Filtering:</strong> Personally, as a user, I’m not a big fan of this application because I generally want to apply multiple filters before I search for results. If your app adjusts results automatically as the user interacts (like checking boxes in a sidebar), it’s better not to move the focus away from the filter. The user is likely making multiple selections and needs to stay in the filter zone.</li><li><strong>Single Page Routing:</strong> In frameworks like React or Vue, where a page change doesn’t trigger a full browser refresh, moving the focus to the new &lt;h1&gt; or the top of the main content area can mimic a traditional page load. This anchors the person in their new location within the app.</li><li><strong>Form Validations:</strong> If a form is submitted with errors, leaving the focus on the “Submit” button may leave the user unaware of what went wrong. Directing them toward an error summary or the first invalid field allows them to perceive and address the issue immediately.</li></ul><p>Let&#39;s be honest: nobody enjoys a glitchy, confusing interface. Accessibility is fundamentally about empathy. It involves creating a smooth, reliable path so that anyone who visits your site feels genuinely welcomed.</p><p>Let’s keep building better, together.</p><p>Happy coding, everyone!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3adcf2a57170" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning Accessibility (A11y) in JavaScript | Part 01: Keyboard-Accessible Interactions]]></title>
            <link>https://javascript.plainenglish.io/learning-accessibility-a11y-in-javascript-part-01-keyboard-accessible-interactions-ff0bff757ea2?source=rss-f3d0b65da8bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff0bff757ea2</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Elif İrem Kara Kadyrov]]></dc:creator>
            <pubDate>Tue, 17 Mar 2026 12:19:29 GMT</pubDate>
            <atom:updated>2026-03-17T12:19:29.897Z</atom:updated>
            <content:encoded><![CDATA[<p>Lately, I’ve been spending more time studying accessibility requirements, trying to understand what they actually mean when building JavaScript interfaces.</p><p>The more I looked into the guidelines and common issues, the more I realized that many problems come from small patterns we repeat every day in front-end development.</p><p>Each rule represents a small principle that affects how we build UI components, handle events, or structure our markup. My goal is to explore them one at a time, understand why they exist, and see how they apply to real JavaScript code.</p><p>I want to share some notes as I work through this.</p><h3>Rule: Every Interactive Element Must Be Keyboard Accessible</h3><blockquote><em>“If an element can be clicked, it must be focusable and triggerable via keyboard.”</em></blockquote><p><strong>The Source:</strong> <a href="https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html">WCAG 2.1 Success Criterion 2.1.1 (Keyboard)</a> states that all functionality of the content must be operable through a keyboard interface.</p><h4>Why is it needed?</h4><p>Keyboard interactions are essential for many users who cannot rely on a mouse. This is particularly important for individuals with <strong>motor impairments</strong>, who may have difficulty performing precise pointer movements required by traditional mouse interactions.</p><p>Keyboard navigation is also widely used by people who rely on <strong>alternative input devices</strong>, such as specialized keyboards, switch devices, or single-pointer input systems. These assistive technologies often emulate keyboard input to control software.</p><p>Hence, any interface that can be operated with a mouse should also be operable with a keyboard.</p><h4>Broken Example (The “Div-Button”)</h4><p>Many developers do this because it’s easy to style and avoids default browser “button” behaviors (like focus rings or internal padding).</p><pre>// A button with div in React<br>const divButton = ({ onClick, children }) =&gt; {<br>  return (<br>    &lt;div <br>      className=&quot;custom-btn&quot; <br>      onClick={onClick}<br>    &gt;<br>      {children}<br>    &lt;/div&gt;<br>  );<br>};</pre><p>Problems with this:</p><ul><li><strong>No Focus:</strong> You cannot reach this element by pressing Tab.</li><li><strong>No Keyboard Activation:</strong> Pressing Enter or Space does nothing.</li><li><strong>No Role or Accessible Name</strong> — Screen readers treat it as <strong>generic text</strong>.</li></ul><p>As an example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*nSeHtNLVlrg_SvPD1STn-w.png" /><figcaption>Table 1: Screen reader example of elements</figcaption></figure><p>Properly implemented interactive elements provide a <strong>role</strong> (button), an <strong>accessible name</strong> (the text or label), and optionally a <strong>description</strong> (via aria-describedby) if extra context is needed. Without these, assistive technologies have no way to convey that the element is interactive.</p><h4>The Refactor</h4><p>You <em>could </em>add tabIndex={0} and a onKeyDown listener to the div, but that’s writing 10 lines of JS to fix the problem that HTML already solved.</p><p><strong><em>Use the native tag whenever possible.</em></strong></p><h4>Accessible Solution</h4><p>In this case, we use the &lt;button&gt; element.</p><pre>const accessibleButton = ({ onClick, children }) =&gt; {<br>  return (<br>    &lt;button <br>      className=&quot;custom-btn&quot; <br>      onClick={onClick}<br>    &gt;<br>      {children}<br>    &lt;/button&gt;<br>  );<br>};</pre><p>Buttons already support:</p><ul><li>Keyboard focus</li><li>Enter/Space key activation</li><li>Correct semantics for screen readers</li></ul><p>No extra JavaScript required.</p><h4>The Lesson: Beyond the Button</h4><p>When adding JavaScript-driven interactions, it’s important to think about <strong>how users perceive and interact with elements beyond just clicking</strong>. Many accessibility issues arise when behavior is added visually but not structurally. A card looks clickable; a dropdown opens on click; a menu item toggles something. But if the HTML doesn’t communicate that these are interactive, not all users can use them.</p><p>Anytime JavaScript turns a static element into an interaction, it must be exposed semantically. As examples:</p><ul><li><strong>Navigation vs. Action:</strong> This is the most common crossroads. If the interaction changes the URL or moves the user to a new page/section, an &lt;a&gt; is usually the right tool. If it triggers a change on the <em>current</em> page (like opening a modal or toggling a theme), a &lt;button&gt; is the standard choice.</li><li><strong>The Dropdowns:</strong> If you’re just showing/hiding a list, a &lt;button&gt; with aria-expanded is generally used. Though if your dropdown is actually for selecting options, you might lean on a hidden &lt;input type=&quot;checkbox&quot;&gt; or &lt;input type=&quot;radio&quot;&gt; pattern. This allows the browser to handle the &quot;checked&quot; state and keyboard toggling natively.</li><li><strong>Dynamic Tabs:</strong> For tabbed interfaces, the goal is to ensure every “tab” is a focusable element that the user can reach and trigger via keyboard, typically utilizing a button or a specifically managed link.</li></ul><p><strong>The Takeaway:</strong> Considering whether the default actions of these elements align with our intended functionality is the key.</p><h4>Final Thoughts: Build Structurally, Not Just Visually</h4><p>As developers, we often focus on the “view.” But accessibility happens in the <strong>structure</strong>. The most robust pattern you can follow is:</p><ol><li><strong>Start with the correct HTML element</strong> (&lt;button&gt;, &lt;a&gt;, &lt;input&gt;).</li><li><strong>Style it</strong> however your design requires.</li><li><strong>Layer your JavaScript</strong> behavior on top.</li></ol><p>Why this is important:</p><ul><li><strong>Leaner Code:</strong> You don’t have to write onKeyDown listeners or manage tabIndex for every interaction manually. The browser does it for you.</li><li><strong>SEO Wins:</strong> Search engines prioritize pages with clear, semantic structures.</li><li><strong>Universal Access:</strong> Your site becomes inclusive, catering to a diverse range of users—from highly proficient keyboard users to those who use screen readers or assistive switches.</li></ul><p>I tried this with the navigation section of my portfolio. Here are the results:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/0*kx7xjA4wM5xrQZ3k.gif" /><figcaption>Gif:Navigation via Tab</figcaption></figure><p>As a <strong><em>challenge</em></strong>, try to navigate your latest project using only the Tab and Enter keys. If you cannot access your main features, your project needs adjustments. It&#39;s time to make those changes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff0bff757ea2" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/learning-accessibility-a11y-in-javascript-part-01-keyboard-accessible-interactions-ff0bff757ea2">Learning Accessibility (A11y) in JavaScript | Part 01: Keyboard-Accessible Interactions</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Burden of Regret: The Choices We Never Made]]></title>
            <link>https://medium.com/illumination/the-burden-of-regret-the-choices-we-never-made-425101282a86?source=rss-f3d0b65da8bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/425101282a86</guid>
            <category><![CDATA[short-story]]></category>
            <category><![CDATA[short-fiction]]></category>
            <category><![CDATA[fiction]]></category>
            <dc:creator><![CDATA[Elif İrem Kara Kadyrov]]></dc:creator>
            <pubDate>Sat, 28 Feb 2026 20:19:24 GMT</pubDate>
            <atom:updated>2026-02-28T20:28:30.036Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JmMZDO96IKqg9qqc" /><figcaption>Photo by <a href="https://unsplash.com/@gakusuyama?utm_source=medium&amp;utm_medium=referral">Gaku Suyama</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It was a Friday night again, as they sat on a park bench together.</p><p><em>“How do you do it?”</em> Maya asked, staring at the setting sun.</p><p><em>“How do I do what exactly?”</em> Ethan said, waiting for clarification.</p><p>Maya sighed, <em>“I keep asking myself, what if... what if I’m always making the wrong choices? It’s like I’m at a crossroads, and every path feels terrifying. I keep replaying my options, worried I’ve overlooked something crucial.”</em> Her eyes remained fixed on the duck swimming in a small puddle. <em>“I look at others and wonder if they’ve figured it all out or if they feel lost too. So... how do you do it? How do you know you’re making the right choice?”</em></p><p><em>“I don’t know,” </em>he said simply. “<em>I just… make the choice and try not to worry about whether it was right or wrong.”</em></p><p>She frowned.<em> </em>She didn’t like that answer. <em>“What do you mean? Don’t you regret anything? I can’t stop thinking about… what if I messed up. What if any alternative was way better than whatever this is?”</em></p><p>Her brow furrowed as she lightly drummed her fingers against her knee, frustration evident on her face. How could he be so calm? She had made so many choices she regretted, and with each attempt to be cautious or thorough, she felt she was wasting time and missing out on valuable opportunities.</p><p>Ethan observed her, noticing how she fidgeted with the hem of her sleeve and the tension in her jaw. He could feel the weight of her past decisions pressing down on her. It was clear she was struggling, and he wanted to help her see things differently. He decided to share the perspective that had helped him keep moving forward, even when every choice felt daunting.</p><p><em>“I get it,”</em> he said finally. <em>“I know how heavy it feels, thinking about all the roads you didn’t take. Feeling like everything might have been better if you’d done something differently.”</em></p><p>He leaned back, looking at the ducks rippling the water, and said, <em>“I’m not saying everything I did was perfect. I just accept them for what they were. You didn’t have today’s knowledge yesterday. Regret feels heavy because we measure the past with the clarity we have now. But that clarity… it wasn’t real back then.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AUn2Xg84vUYU1Otm" /><figcaption>Photo by <a href="https://unsplash.com/@astro_civil?utm_source=medium&amp;utm_medium=referral">Chelsey Marques</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Maya stayed silent for a moment, her hands twisting in her lap. <em>“So… even if I realize it wasn’t the correct choice, I shouldn’t be this devastated? Even when it feels like I’ve ruined everything for myself or someone else?”</em></p><p><em>“Yes,”</em> he said firmly. <em>“Even then. Every choice you made, every mistake, every hesitation… they all made the person you are now. Regret can be overwhelming, but it’s also a teacher. You can’t undo an experience. It is the way it is. You can’t change the past, but you can learn from it</em>.<em>”</em></p><p>Maya exhaled slowly, staring at the fading reflection of the sun on the puddle. <em>“So you just… accept it?”</em></p><p><em>“I accept it. Those regrets don’t define you alone.”</em> Ethan said. <em>“Acceptance doesn’t mean you’re happy about what happened; it means you are recognizing it and allowing yourself to learn.”</em></p><p>She let her hands rest loosely in her lap for a moment, blinking slowly, as if letting some of the tension drain away. Then she reached over, nudging Ethan’s shoulder gently. <em>“Okay… maybe I can stop hating every decision I’ve ever made for a minute.”</em> Ethan nodded with a slight smile, and they sat quietly. Together, they watched the sun set for good.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=425101282a86" width="1" height="1" alt=""><hr><p><a href="https://medium.com/illumination/the-burden-of-regret-the-choices-we-never-made-425101282a86">The Burden of Regret: The Choices We Never Made</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[The Final Song of a Life]]></title>
            <link>https://medium.com/illumination/the-final-song-of-a-life-1bfe4fa68a7f?source=rss-f3d0b65da8bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bfe4fa68a7f</guid>
            <category><![CDATA[short-story]]></category>
            <category><![CDATA[short-fiction]]></category>
            <category><![CDATA[fiction]]></category>
            <dc:creator><![CDATA[Elif İrem Kara Kadyrov]]></dc:creator>
            <pubDate>Mon, 16 Feb 2026 21:22:16 GMT</pubDate>
            <atom:updated>2026-02-17T11:08:53.099Z</atom:updated>
            <content:encoded><![CDATA[<p>The room was quiet. The lamp on the bedside table radiated a soft light. It pooled around the framed photograph of a woman with a glowing smile that seemed brighter than the dim autumn afternoon outside.</p><p>Raindrops were slightly tapping on the glass with a steady rhythm. Beyond, a tree stood bare, its branches gnarled and dark against the dark sky. Most of its leaves had already surrendered to the season. Scattered across the ground like forgotten memories…</p><p>There was just one remaining, clinging to a high, swaying branch. It was brownish-orange now, curled and flaky. It kept its composure against the wind that tried to snatch it away. He had been watching the scene all day, the way it debated whether to stay or let go.</p><p>The wind picked up, rustling the fallen leaves and sending ripples through the puddles below. The remaining leaf trembled, defiant against the inevitable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H8IhV_WEoxeSwy7n" /><figcaption>Photo by <a href="https://unsplash.com/@johndoesphoto?utm_source=medium&amp;utm_medium=referral">John Park</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>He sighed softly as his gaze shifted to his wrinkled and spotted hands. His once-strong physique had faded with time. The sharp jawline and broad shoulders that had once drawn attention were long gone, replaced by sunken cheeks and weakened limbs. Time had taken so much from him, but nothing compared to the absence of his beloved, which had truly hollowed him out. Ten years had passed, but the pain of missing her had not dulled in the slightest.</p><p>He glanced at the photograph again, his lips curling into the softest hint of a smile. Gently, he picked up the photograph and stroked it, imagining what it would be like to hold her face in his hands once more.</p><p><em>“Oh, Maggie…”</em> he murmured, his voice raspy and low. <em>“You always knew how to make everything magical.”</em></p><p>The room answered with silence, except for the continuous whisper of the rain. A knock at the door interrupted his trance, soft but deliberate. He frowned. It wasn’t time for the nurse. She came at seven every evening, and the clock on the wall showed it was too early for her usual visit.</p><p><em>“Come in,”</em> he said.</p><p><em>“I thought I’d be alone,”</em> he murmured when he saw her enter. She smiled gently. A young woman stood by his bedside. She was perhaps in her late twenties and dressed simply in a white, flowing dress that seemed to shift the light when she moved. Her golden eyes sparkled with innocence and tenderness. Her smile felt like a warm, comforting embrace.</p><p>He squinted at her, trying to place her. He hadn’t met her before, but yet, he felt like he’d known her all along, in some distant, forgotten way.</p><p><em>“Who are you?”</em> he asked. His eyes darted to the photograph, then back to her.</p><p><em>“I’m just someone to keep you company,”</em> she replied. Her voice, like the rain, was soft, steady, and endlessly familiar. <em>“May I sit?”</em></p><p>He nodded, though his suspicion remained. She pulled a chair close to his bed and sat, folding her hands neatly in her lap. For a moment, neither of them spoke. The rain filled the silence between them.</p><p>Her eyes met his, and he was struck by how still they were. No trace of nervousness or uncertainty. Just a calm, steady gaze that felt as if it could see through him — past the wrinkles and flaws, into something deeper.</p><p><em>“You’ve felt it, haven’t you?”</em> she said, gently breaking the silence between them. <em>“The way the seasons change. The way the world shifts when it’s time to move on.”</em></p><p>He didn’t answer. He didn’t need to. She was right, of course. He’d known for days, maybe weeks. The heaviness in his limbs, the way his breath came shorter with each passing day. He’d felt it in his bones, like that last leaf clinging to the tree outside.</p><p><em>“I’m not ready,”</em> he whispered finally, his voice breaking. His eyes glistened, though no tears fell. <em>“I thought I would be, but I’m not.”</em></p><p>Her expression softened, and she leaned forward slightly. <em>“No one ever truly is,”</em> she said. <em>“But it doesn’t have to be frightening. It can be peaceful. Like a song… one final, beautiful note to end a lifelong melody.”</em></p><p>She reached out a hand, not to touch, but to gesture toward the photograph he was holding. Her words stirred something in him. A trembling breath escaped his lips, and his gaze wandered back to the window. The leaves... The rain... Memories began to surface, vivid and sharp, as though the room itself had grown heavy with the weight of his past.</p><p><em>“It’s strange,”</em> he spoke after a long pause, his voice filled with surprise. <em>“When I think about my life, the details… the events are all blurry. But the feelings… those stay.”</em> he swallowed before continuing.</p><p><em>“I remember how it felt to hold Maggie’s hand the first time, how my chest felt like it would burst.”</em> his voice wavered, and he closed his eyes. <em>“I can’t even recall the exact time she passed, but the hollowness… the grief… the grief when I lost her… that has never left.”</em></p><p>The young woman listened in silence, her expression was unreadable yet sincerely attentive. He continued speaking, his words flowing out of him as if they had been waiting for release.</p><p><em>“I was a hard man once,”</em> he said. <em>“Stoic. Tough. My father made sure of that. He taught me that feelings were a weakness. But Maggie… she saw through all that. She laughed at me, you know?”</em> he let out a painful chuckle. <em>“She said I took myself too seriously. She had a way of making the world lighter.”</em></p><p>His lips curved into a faint smile, but his eyes were still wet. <em>“I loved her so much, and I never told her enough. I thought time would stretch on forever. And then it didn’t.”</em></p><p>The young woman’s presence provoked a vivid memory, sending him back to a bright summer evening at a lively dance party near the farmland. The upbeat music pulsed alongside the laughter of friends dancing under colorful lights. Leaning against a wooden post with his arms crossed, he wore a mask of indifference; this wasn’t his thing—he was only there because his friends had dragged him along. Then he saw her. Margaret. His Maggie. Her laughter cut through the noise, captivating him and making the world around him fade away.</p><p>She had been laughing, her head thrown back like sunlight breaking through a cloudy day. Her dress was simple and pale blue, but on her, it might as well have been spun from starlight. When she smiled, it wasn’t just her lips — it was her whole face, her entire being, warm and inviting. She looked at him, and in that instant, something shifted.</p><p><em>“I don’t know why she came over,”</em> he mumbled, half to himself. <em>“I was a block of stone back then. Hard, cold. But she did. She walked right up and asked me to dance. Didn’t take no for an answer.”</em></p><p>The memory played out like a movie in his mind. He could still feel the heat rising in his face as she pulled him onto the dance floor, and he could still hear her teasing laugh when he stumbled over his own feet. She had been gentle, guiding him with her soft hand in his. By the end of the night, he didn’t want to let her go.</p><p><em>“She was… incredible.”</em> There was still an admiration in his voice. <em>“She was the only one who could do that to me,” he said softly. “Make me feel like more than I was. Make me want to be better. For her.”</em></p><p>The young woman leaned closer, her voice gentle.</p><p><em>“And you were. You were better, weren’t you?”</em> Her voice threaded through his thoughts like a quiet, steady current. <em>“You became the man she saw in you.”</em></p><p>He swallowed hard, his throat tightening at her words. <em>“I don’t know if I ever lived up to that,”</em> he admitted.<em> “But I tried. I tried every day.”</em></p><p>He looked at her photograph again. Holding onto it like it was the only thing that mattered.</p><p><em>“I wish I could see your beautiful face again, my Maggie. I wish I could hold you in my arms once more...”</em> Finally, a tear couldn’t bear the weight of his emotions and fell slowly. He closed his eyes. He let himself feel, maybe for the one last time.</p><p>The young woman started to hum a melody. It felt awfully familiar but also unique.</p><p><em>“You’ve carried so much love, so much grief. It’s time to let it rest, don’t you think, Mr.Russell?”</em> her velvety voice echoed through his veins.</p><p>He understood that the time had come for him, too. He hesitated at first, but then asked. <em>“Will it… will it hurt?”</em> his voice trembling.</p><p>She shook her head. <em>“No. Not with me here.”</em></p><p>She held his hand gently and began to sing. His final song… He closed his eyes, and all he could see were good memories he had collected his entire life, most involving Maggie. Her song guided him through his recollections, the things he was sure he had forgotten a long time ago. A small smile appeared on his face. He whispered, <em>“Thank you…”</em> on his final breath. He was still holding Maggie’s photo on his chest.</p><p>The room was quiet. Even the wind had stopped hitting the room window. She finished his song, and a tear in her eye threatened to fall. A while later, the time hit 7 o’clock, and his nurse knocked on the door. She brought his dinner and medicine.</p><p><em>“Mr. Russell?”</em> she said, her voice filled with excitement. <em>“Today we have your favorite! I know you don’t want to admit it, but I can tell you really like the roasted beef days. You usually finish your entire plate, unlike on other days.”</em> She chuckled as she entered the room.</p><p>The room was deafeningly quiet, with no sign of anyone else. As usual, the nurse placed the plate on the movable table. <em>“Mr. Russell? Are you taking a nap?”</em> she asked, approaching him curiously. She noticed him holding onto a photo of his late wife, a small smile on his face, and his eyes closed, which made her heart melt.</p><p><em>“Mr. Russell? It’s time for dinner, I’m afraid.”</em> She gently shook him, but he didn’t wake up. Her smile faded into a frown as she searched for a heartbeat, only to realize he was already gone. <em>“Oh, Mr. Russell…”</em></p><p>She pulled the same chair as the young woman before her and sat down, looking at his peaceful embrace. Her hands were shaky. She didn’t expect to come to this.</p><p><em>“I truly enjoyed your company while you were here, even if you could be a bit grumpy, Mr. Russell,”</em> she said, grabbing his hand and taking a deep breath. <em>“I hope you get to see your Maggie again.”</em></p><p>As she spoke, the final leaf on the tree fell, swaying in the wind before landing softly on the water.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bfe4fa68a7f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/illumination/the-final-song-of-a-life-1bfe4fa68a7f">The Final Song of a Life</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[The Quiet Truth About New Goals]]></title>
            <link>https://medium.com/@elfrmkr98/the-quiet-truth-about-new-goals-e4e356451985?source=rss-f3d0b65da8bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4e356451985</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Elif İrem Kara Kadyrov]]></dc:creator>
            <pubDate>Fri, 23 Jan 2026 13:14:43 GMT</pubDate>
            <atom:updated>2026-01-23T13:14:43.594Z</atom:updated>
            <content:encoded><![CDATA[<p>As 2025 faded into memory, a familiar thought surfaced again:<em> Next year will be my year.</em></p><p>It comes with more plans, better habits, and bigger dreams. The one we’ve always dreamed of being.</p><p>We surround ourselves with bold intentions and high expectations, rarely stopping to ask whether all of it is realistic, sustainable, or even necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IX28wT7dgH78BeZO" /><figcaption>Photo by <a href="https://unsplash.com/@martenbjork?utm_source=medium&amp;utm_medium=referral">Marten Bjork</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For a long time, I thought setting goals meant looking forward only. But what I’ve learned, especially now, is that meaningful progress begins by looking back. Not just at the highlights, but at the quieter moments too. The small wins, disappointments, and pauses that felt unproductive at the time but quietly shaped us anyway.</p><h4>The Importance of Reflection</h4><p>A couple of years ago, I did things the other way around. I started with resolutions.</p><p>It was the dawn of a new year, and the air buzzed with the promise of fresh beginnings. With a pencil in hand and a heart full of hope, I sat down to design my future. It felt exhilarating to imagine all the possibilities ahead.</p><p>I wrote the perfect protagonist that I wished to become. She was brave, kind, and endlessly motivated. She handled challenges with ease, inspired others, radiated confidence, and somehow excelled at several hobbies at once. Always chasing the feeling of accomplishment...</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9rAr0XLXnYrU5pNJ" /><figcaption>Photo by <a href="https://unsplash.com/@teacreativelife?utm_source=medium&amp;utm_medium=referral">TEAcreativelife │ Soo Chung</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Imagination is generous like that. It asks for nothing in return.</p><p>As the year went on, reality caught up. That ideal version of myself began to feel more like an illusion. And let&#39;s be honest, if this were a novel or a movie, who would want to follow a character who never struggles? A protagonist who breezes through life without resistance would make for a completely dull story.</p><p>What I began to understand was this: it was never about becoming ideal. It was to stay in motion. The movement toward something meaningful, rather than a sudden, magical transformation, however tempting that idea may be.</p><p>By the end of that year, many goals were unfinished. Some never made it past the page. But it didn’t feel like failure. It felt like perspective.</p><p>Reviewing a year isn’t about proving how productive you were. It’s about understanding <em>how you lived.</em></p><h4>Asking Better Questions</h4><p>Now, instead of rushing into plans, I begin with reflection.</p><p>I ask myself:</p><ul><li>What actually made me happy this year?</li><li>What did I explore or experience for the first time?</li><li>When did I feel frustrated, and what triggered it?</li><li>What drained my energy? What gave it back?</li><li>What did I keep wishing I had more space for?</li></ul><p>These questions reveal patterns. They show what consistently matters, not just what sounds good on paper.</p><h4>Choosing Goals That Can Breathe</h4><p>Only after that clarity do goals start to make sense.</p><p>Maybe goals aren’t about doing more, becoming more, or fixing ourselves. Maybe, they’re about listening, noticing patterns, and the desires we’ve been quietly carrying all year.</p><p>Realistic goals leave room for bad days. They respect our energy instead of constantly demanding it. They don’t expect us to wake up the next day as a brand-new person; they simply ask us to show up as we are, a little more aware than before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s3jBiMGnE07_jgar" /><figcaption>Photo by <a href="https://unsplash.com/@dinoreichmuth?utm_source=medium&amp;utm_medium=referral">Dino Reichmuth</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Progress doesn’t need to be loud or constant. Small changes compound over time. Sometimes growth looks like rest. Sometimes it looks like saying no. Sometimes it’s letting go of things that no longer fit, even if they once mattered deeply.</p><p>As we move forward, our intentions don’t have to sound impressive. They can be subtle, flexible, and honest. Gentle promises we can actually keep.</p><p>We don’t need to become perfect protagonists. We just need to stay present in the story we’re already living and keep moving. Quietly, in a direction that feels true.</p><p>And most days, that is more than enough.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4e356451985" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>