<?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 Tuhin on Medium]]></title>
        <description><![CDATA[Stories by Tuhin on Medium]]></description>
        <link>https://medium.com/@tuhinsubhramitra?source=rss-bf9bca3c14b5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*a9nVgepQh7w-GVSSv5YkwQ.jpeg</url>
            <title>Stories by Tuhin on Medium</title>
            <link>https://medium.com/@tuhinsubhramitra?source=rss-bf9bca3c14b5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:43:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tuhinsubhramitra/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[Golem and Pygmalion effects — traps to avoid as an Engineering Manager]]></title>
            <link>https://medium.com/doctolib/golem-and-pygmalion-effects-traps-to-avoid-as-an-engineering-manager-4160360933c3?source=rss-bf9bca3c14b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/4160360933c3</guid>
            <category><![CDATA[team-development]]></category>
            <category><![CDATA[long-term-growth]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[cognitive-bias]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Tuhin]]></dc:creator>
            <pubDate>Wed, 18 Mar 2026 13:10:09 GMT</pubDate>
            <atom:updated>2026-03-19T06:23:39.510Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4q67KO-xH83NpXJLLqPCWw.png" /><figcaption>Golem and Pygmalion effects</figcaption></figure><p>You heard Stella was a “coding prodigy” during the interview. When Stella ships a bug in week two, you see it as a “learning opportunity.” You pair with her, offer encouraging feedback, and give her a high-visibility feature for the next sprint. Stella feels valued, takes ownership, and crushes the deadline. You think, <em>“I knew they were a rockstar.”</em></p><p>You were lukewarm on Dave’s technical test, fearing they might be a “slow starter.” When Dave hits a similar bug in week two, you think, <em>“Here we go.”</em> You take the task away to “save time” and give them documentation updates instead. You check in three times a day, signaling a lack of trust. Dave feels stifled and anxious. They stop asking questions to avoid looking “stupid,” fall behind, and eventually disengage. You think, <em>“I knew they weren’t a great fit.”</em></p><p>Both engineers had the same potential on day one. The only difference was the lens through which you viewed them. These two biases — <strong>the Golem and Pygmalion effect (high or low expectations influencing performance)</strong> — are two sides of the same self-fulfilling prophecy coin. They describe how a leader’s expectations — even the unspoken ones — directly dictate an individual’s performance.</p><h3>Breaking the Curse: An EM’s Guide to High Expectations</h3><p>The <strong>Golem Effect</strong> is the psychological phenomenon where lower expectations from a manager lead to lower performance from the employee. It’s the dark cousin of the Pygmalion Effect.</p><p>In the high-stakes world of engineering, this usually manifests as “The Death Spiral”: a manager thinks a dev is “junior,” gives them menial tasks, the dev loses motivation, and their performance actually drops.</p><p>Here are some scenarios you’ve likely heard about or encountered, and how to counteract them.</p><h3>Episode 1: The “Label” Trap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MaKaEGho6sG1tHASGLnyfQ.png" /><figcaption>The “Laebl” Trap</figcaption></figure><p><strong>The Scene:</strong> Manager “Mike” is looking at a Jira board. He points to “Dev Dave” and thinks, <em>“Dave is just a tech-maintenance guy. He can’t handle the new API architecture.”</em></p><p><strong>The Pitfall:</strong> Pre-judging capabilities based on past hiccups or narrow roles.</p><p><strong>The Solution: </strong>Practice leadership philosophies like <strong>self-reflection and growth opportunities.</strong></p><ul><li><strong>Check Your Own Narrative: </strong>Instead of just “auditing biases,” take a quiet moment before you assign a task to look at your internal “story” for each person. Realize that every time you bypass Dave, you aren’t just saving time — you’re actively shrinking his future.</li><li><strong>The “Day One” Mindset: </strong>If you hold onto the version of Dave that struggled six months ago, you won’t notice the version of Dave that’s ready to lead today. Give him the space to surprise you; more often than not, people will rise to the level of the person you decide to see.</li></ul><h3>Episode 2: The Micromanagement Shadow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pHUV_SH-oMYoQe14xoPfAQ.png" /><figcaption>The Micromanagement Shadow</figcaption></figure><p><strong>The Scene:</strong> Mike is hovering over Dave’s shoulder, commenting on every line of code in real-time. Dave looks like a deer in headlights.</p><p><strong>The Pitfall:</strong> Low expectations lead to over-monitoring. This kills autonomy and signals a lack of trust, which crushes dev productivity.</p><p><strong>The Solution: </strong>When<strong> </strong>I hover, I’m telling my engineer, <em>“I don’t think you can do this without me.”</em> That’s a <strong>heavy weight for them to carry.</strong></p><ul><li><strong>Trust the “Why,” Release the “How”</strong>: I need to be crystal clear on the goal, but I have to leave the path to them. I’ll measure success by the final product, not by whether they did it exactly the way I would have.</li><li><strong>The “Safety Net” Promise:</strong> Instead of watching them work, I’ll tell them: <em>“I’m stepping back because I trust your judgment, but I’m right here if you hit a wall.”</em> It changes my role from a “guard” to a “resource.”</li></ul><h3>Episode 3: The “Easy Task” Feedback Loop</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g4eP0QCAv97dV_l_V2MULQ.png" /><figcaption>The “Easy Tsk” Feedback Loop</figcaption></figure><p><strong>The Scene:</strong> Dave is buried under a mountain of “Change Color of Button” tickets. He looks bored. Mike thinks, <em>“See? He’s slow even on the easy stuff!”</em></p><p><strong>The Pitfall:</strong> Giving “safe” tasks prevents growth. If an engineer isn’t challenged, they won’t innovate, confirming your low opinion of them.</p><p><strong>The Solution: </strong>Instead of considering these a rigid formula and treat them as a personal commitment to your team’s growth; offer <strong>sponsorship</strong> and <strong>psychological safety.</strong></p><ul><li><strong>The “Growth Budget”</strong>: If an engineer spends 100% of their time doing things they already know how to do, they aren’t gaining a year of experience — they’re just repeating one month of experience twelve times. Allocate some flexible time where an engineer can explore unfamiliar territories, which will help her grow.</li><li><strong>Guided Bravery: </strong>Forget “scaffolding” — think of this as <strong>being the safety net, not the crutch.</strong> It’s about giving them challenging work but making sure they know they aren’t alone in the dark.</li></ul><h3>Episode 4: The One-on-One Pivot</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*58CMDY068ddsF6LJWFSxKw.png" /><figcaption>The One-on-One Pivot</figcaption></figure><p><strong>The Scene:</strong> In a 1:1 meeting, Mike says, “Just get these bugs done” instead of saying “What part of the system do you want to own next quarter?”</p><p><strong>The Pitfall:</strong> Transactional management, a style that relies on a clear structure of rewards for high performers and punishments for failure.</p><p><strong>The Solution: </strong>Spread the<strong> intentional belief</strong>; be the person who sees their potential before they even see it themselves.</p><ul><li><strong>Casting the vision:</strong> If you only interact with the “Current Dave,” he stays stuck. If you interact with the “Future Senior Dave,” he starts to unconsciously reach for that standard.</li><li><strong>Active Encouragement:</strong> Use “I’m giving you this because I know you can handle the complexity,” even if they seem hesitant.</li></ul><h3>The Pedestal Peril: Balancing the Pygmalion Effect</h3><p>The <strong>Pygmalion</strong> effect, aka the “Golden child” trap, it’s the phenomenon where high expectations lead to improved performance — which sounds great until you realize it can lead to <strong>burnout, favoritism, and “Star Player” silos.</strong> In engineering, this usually looks like a manager giving the “Rockstar” all the cool projects while everyone else gets the leftovers.</p><p>Here are some scenarios you’ve likely heard about or encountered, and how to counteract them.</p><h3>Episode 1: The “Hero” Bottleneck</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8bEXNLtzGIfFNli3Ak-ufQ.png" /><figcaption>The “Hero” Bottleneck</figcaption></figure><p><strong>The Scene:</strong> Manager “Mike” hands a critical, high-visibility project to “Star Player Stella” for the fifth time this month. In the background, the rest of the team is playing Minesweeper because they have nothing impactful to do.</p><p><strong>The Pitfall:</strong> Over-relying on your top performers because you “know they’ll crush it.” This creates a single point of failure and builds resentment.</p><p><strong>The Solution: </strong>It’s the mental shift<strong> from protecting the project to building the people</strong></p><ul><li><strong>Investing in future talent:</strong> It’s a conscious choice to stop taking the easy path of least resistance (giving it to the person who already knows how) and start taking the path of most growth.</li><li><strong>Turning Heroes into Multipliers:</strong> Redefine what it means to be a ‘Senior’ on this team; instead of just doing the work themself, by becoming a Multiplier, they use their intelligence to amplify the capabilities of everyone around them.</li></ul><h3>Episode 2: The “Halo” Blind Spot</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvqQZo9dLrJuw40A-TubDQ.png" /><figcaption>The “Halo” Blind Spot</figcaption></figure><p><strong>The Scene:</strong> Stella pushes code that breaks the build. Mike laughs it off, saying, <em>“Classic Stella, she’s just moving fast!”</em> Meanwhile, another dev gets a formal warning for a smaller mistake.</p><p><strong>The Pitfall:</strong> High expectations can blind you to a top performer’s actual flaws or toxic behaviors (the “Brilliant Jerk” syndrome).</p><p><strong>The Solution: </strong>Real leadership isn’t about protecting your best player; it’s about protecting the integrity of the whole team.</p><ul><li><strong>Equal Standards:</strong> High expectations must apply to <strong>process</strong>, not just <strong>output</strong>. Use the same automated linting and PR review standards for everyone.</li><li><strong>360 Feedback:</strong> Don’t just rely on your own view; ask the team how working with the “star” actually feels.</li></ul><h3>Episode 3: The Burnout Pedestal</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oZzIGM5lf3NT7Yrt_VZklQ.png" /><figcaption>The Burnout Pedastel</figcaption></figure><p><strong>The Scene:</strong> Stella is at her desk at 10 PM. She looks exhausted. Mike sends her a Slack: <em>“I know only you can solve this by tomorrow morning! You’re a legend!”</em></p><p><strong>The Pitfall:</strong> Using high expectations as a psychological whip. Your belief in their “superhuman” ability can make them feel they aren’t allowed to struggle or rest.</p><p><strong>The Solution: </strong>Protect the Person, Not Just the “Asset”</p><ul><li><strong>De-clutter the Ego:</strong> Remind your stars that their value isn’t tied to being “the best” every single day.</li><li><strong>Predictable Stress:</strong> Don’t use “You’re the only one who can do this” as a management tactic for poor planning.</li></ul><h3>Episode 4: The Inclusion Gap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9pW0XfJMEHO7X7yS96MjFw.png" /><figcaption>The Inclusion Gap</figcaption></figure><p><strong>The Scene:</strong> A brainstorming session. Mike only looks at Stella for the “right” answer. The other three engineers have stopped trying to speak.</p><p><strong>The Pitfall:</strong> Creating a “Two-Tier” team. If only one person is expected to be brilliant, the others stop trying to contribute.</p><p><strong>The Solution: </strong>Shift from being a fan of an individual to being a facilitator of a collective.</p><ul><li><strong>The “Round Robin” Expectation:</strong> Start meetings by asking for input from the person with the <em>least</em> tenure first.</li><li><strong>Assume Collective Intelligence:</strong> Move from “Stella is the expert” to “This team is an expert unit.”</li></ul><h3>EM Desk Reference: Navigating the Golem and Pygmalion Effects</h3><h3>💡 Quick Audit for Your Next 1:1</h3><p>If you aren’t sure where a team member is positioned, ask <strong>yourself</strong> these three questions:</p><ol><li><strong>For Golem Check:</strong> <em>“What is one complex task I am currently withholding from this person because I’m afraid they’ll fail?”</em></li><li><strong>For Pygmalion Check:</strong> <em>“If this person left tomorrow, would the team collapse because I haven’t let anyone else learn their ‘special’ domain?”</em></li><li><strong>The Neutralizer:</strong> <em>“Am I holding this person to a standard of excellence, or am I holding them to my personal opinion of them?”</em></li></ol><p><strong><em>Credits:</em></strong></p><ol><li>Image — Google Nano Banana</li><li>Blogpost Structure — Google Gemini PRO</li></ol><p><strong>P.S:</strong> This blogpost is part of the same series where I discuss the common pitfalls to avoid as an engineering manager. If you are interested in reading further, discover <a href="https://medium.com/doctolib/growth-debt-a-trap-to-avoid-as-an-engineering-manager-24546913faf4">this</a> blogpost on Doctolib Medium account where I talked about Growth Debt.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4160360933c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doctolib/golem-and-pygmalion-effects-traps-to-avoid-as-an-engineering-manager-4160360933c3">Golem and Pygmalion effects — traps to avoid as an Engineering Manager</a> was originally published in <a href="https://medium.com/doctolib">Doctolib</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Growth Debt — a trap to avoid as an engineering manager]]></title>
            <link>https://medium.com/doctolib/growth-debt-a-trap-to-avoid-as-an-engineering-manager-24546913faf4?source=rss-bf9bca3c14b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/24546913faf4</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[team-development]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Tuhin]]></dc:creator>
            <pubDate>Tue, 11 Mar 2025 08:35:01 GMT</pubDate>
            <atom:updated>2025-03-11T10:00:52.864Z</atom:updated>
            <content:encoded><![CDATA[<h3>Growth Debt — a trap to avoid as an engineering manager</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/0*fNVC3b0dISce2BB7.jpg" /><figcaption>Team Growth</figcaption></figure><p>As an Engineering Manager, I often need to decide whether I solve a task on my own or delegate it to the team. My go-to decision mechanism for that is the <a href="https://asana.com/resources/eisenhower-matrix">Eisenhower matrix</a>. I would like to discuss the hidden cost, Growth Debt, of <strong>doing and not delegating</strong> in this blog post.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-M1BJJ4OydJEkNMC-s5N9Q.png" /><figcaption>Eisenhower matrix</figcaption></figure><p><strong>When I decide not to delegate a task, I deprive a team member of an opportunity to grow and learn.</strong> Over time, the <strong>growth debt compounds</strong>; the engineers struggle to think and always rely on me for urgent and important work, and their professional growth crawls.</p><p><strong>How do I tackle the Growth debt?</strong></p><p>Before jumping into the solution mode, I do the following :</p><ul><li><strong>Shift right and collaborate:</strong> Introspect more, especially the urgency aspect. If it’s important but not urgent, I shift the task right, from <strong>Do</strong> to <strong>Schedule</strong> for later.<br>When I do work on tasks that I scheduled for later, I pair with a team member so that my team member can learn from me and next time can work solo on a similar task.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jduWJVEGLA3yll0MZyEo-g.png" /><figcaption><strong>Shift right, schedule</strong> for later, and <strong>collaborate</strong></figcaption></figure><ul><li><strong>Shift down and set expectations:</strong> Introspect more, especially the importance aspect. If it is urgent but not important, I set expectations and delegate the task to a competent team member.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*ZI447UrB0nqhjv8666H2Pw.png" /><figcaption><strong>Shift down</strong> and <strong>set</strong> <strong>expectations</strong></figcaption></figure><ul><li><strong>Do it and share the learnings:</strong> For <strong>absolutely important and time-critical tasks</strong>, I go solo but do a debrief with the team and share my learnings.</li></ul><p>For example, a few weeks ago, I was working on setting up a Datadog dashboard to reflect our API response times and error rates. My team was new to Observability and Datadog so it was an opportunity for them to learn while doing the work. It was both urgent and important work, so I went solo to implement it quickly. Once I implemented it, I organized a hands-on knowledge transfer session and shared my learnings with the team.</p><p>Lastly, it’s important to create a balance between doing and delegating; a wrong assessment on either side can have negative effects on the team members and/or slow the completion of urgent work. But as a leader of the team, I am responsible for the culture I create within the team. Hence, it is my job to avoid the Growth Debt and create ample opportunities for the team to learn and grow while working on tasks with a high stake.</p><p><em>Image Credits:</em></p><p>The team Growth image is from <a href="https://zalopay-oss.github.io/">Zalopay-Oss</a></p><p>The Eisenhower Matrix image is from <a href="https://asana.com/resources/eisenhower-matrix">Asana</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24546913faf4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doctolib/growth-debt-a-trap-to-avoid-as-an-engineering-manager-24546913faf4">Growth Debt — a trap to avoid as an engineering manager</a> was originally published in <a href="https://medium.com/doctolib">Doctolib</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does time (only) solve a problem at work?]]></title>
            <link>https://medium.com/@tuhinsubhramitra/does-time-only-solve-a-problem-at-work-f32c807c23c7?source=rss-bf9bca3c14b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f32c807c23c7</guid>
            <category><![CDATA[worklife]]></category>
            <category><![CDATA[culture-change]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Tuhin]]></dc:creator>
            <pubDate>Tue, 10 Aug 2021 14:46:57 GMT</pubDate>
            <atom:updated>2021-08-10T14:46:57.017Z</atom:updated>
            <content:encoded><![CDATA[<p>No, time itself doesn’t solve a problem at work. I believe time itself doesn’t solve a problem anywhere — be it at the workplace or at personal space. Let’s park the personal side of things for another writing; today I would like to talk about problems at the workplace.</p><blockquote>Inaction — lack of action where some are expected or appropriate.</blockquote><blockquote>“future generations will condemn us for inaction”</blockquote><p>When you park a problem with the hope that time will solve it is called inaction. It has different consequences -</p><ul><li>Your current employees will be frustrated if not all but some. I will explain <strong>later </strong>why everyone will not be bothered by the problem.</li><li>As said in the example above “future generations will condemn us for inaction”</li><li>There will be plenty of confusion on the floor and no one would know how to deal with the problem; different teams will deal with the problem differently</li><li>It would result in waste from the organization’s perspective — money, reputation, employee happiness, etc.</li></ul><h3>What you can do to avoid inaction? (act)</h3><ul><li>Acknowledge that there is a problem and try to achieve a consensus across the organization among key stakeholders. Now, it’s time to explain why some people are okay with the problem because they don’t acknowledge the problem. Some fail to acknowledge the problem not because they want to but because either they lived with the problem for so long that they developed hacks around it, from their position they have zero to minimal effect by the problem, acknowledging the problem create more work for them, their plates are already full with other higher pressing problems.</li><li>Assign a priority to the problem and some realistic deadlines (if possible in weeks and months, please not in years)</li><li>Create a workgroup who will work on the problem — work in adjacent possible solutions instead of solving it big bang</li><li>Provide periodic updates to the bigger audience who are affected by the problem</li><li>If the workgroup comes up with solutions, in theory, practice it over one or a few teams and include those teams’ journey as a testimonial to the solution</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f32c807c23c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I do during my return trip to home after work?]]></title>
            <link>https://medium.com/@tuhinsubhramitra/what-i-do-during-my-return-trip-to-home-after-work-c435b8d421b9?source=rss-bf9bca3c14b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c435b8d421b9</guid>
            <category><![CDATA[conflict]]></category>
            <category><![CDATA[thinking]]></category>
            <category><![CDATA[food]]></category>
            <category><![CDATA[family]]></category>
            <dc:creator><![CDATA[Tuhin]]></dc:creator>
            <pubDate>Tue, 01 Oct 2019 08:54:04 GMT</pubDate>
            <atom:updated>2019-10-02T08:30:05.263Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GuP05S2e_fNaouE7ZGrtpw.jpeg" /><figcaption>Shrimp noodles with a poached egg — made and clicked by me</figcaption></figure><p><strong>What I do during my return trip to home after work?</strong></p><p>Besides reading and occasional music listening I think; I think hard.</p><p><strong>What?</strong></p><p>I mostly think about what to cook.</p><p>I enjoy eating and cooking! Fortunately the lady of my life is equally passionate about food and cooking — she has some amazing baking skills! The moment I walk out of office; I start thinking about our dinner. Like today (21st August, 2019) I am thinking whether to prepare pork or shrimp noodles; pork noodles we didn’t eat for a while! But the weather is getting warmer and I don’t prefer pork in warmer weather. I don’t like this part of mine that I thought “I don’t prefer pork…” and about to decide to not prepare it.</p><p>On weekends, food is one of the major topics of our discussion — we fancy about it, we cherish the discussions and stories attached to it, we happily do groceries, and eventually cook and eat the result with love. But during weekdays, I decide myself what to cook, I definitely do check with my wife whether that’s fine with her. My wife never objects my cooking choices (she requests for certain dishes which I gladly prepare); but I am afraid if she does how I will deal with it! Will I bring the best convincing version of mine to give her data why not pork or will I just say I decided pork, so it’s pork? I want to be reasonable with my arguments and don’t want to sound like a dictator — but I don’t like to argue/debate over trivial issues; I believe in giving up if I face resistance in this kind of issues in daily life. I will simply say — let’s have shrimp noodles today if that’s what you prefer, we will eat pork version some other time. I agree because I don’t want to invest the energy and time in debating about it, not because I am fully convinced! It’s not that I will not like the meal if it was not my initial choice; but somehow it mildly bothers me<strong> how I agree to do something that is not my preference.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c435b8d421b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[That moment of uncertainty]]></title>
            <link>https://medium.com/@tuhinsubhramitra/that-moment-of-uncertainty-edd6cbfc7212?source=rss-bf9bca3c14b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/edd6cbfc7212</guid>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Tuhin]]></dc:creator>
            <pubDate>Mon, 05 Aug 2019 15:10:04 GMT</pubDate>
            <atom:updated>2021-09-21T14:31:44.282Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WEzf4b8Vqa29hNhB" /><figcaption>Photo by <a href="https://unsplash.com/@paul_nic?utm_source=medium&amp;utm_medium=referral">Paolo Nicolello</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>That moment of uncertainty</strong></p><p>I am 31 years old (in the year 2019). For the first 5 years of my life, I was unaware of the concept called “uncertainty”; some of you may argue with proper scientific evidence that for human beings “uncertainty” is a phenomenon even at a later stage of life. The specific age is trivial here. During those initial days when I was uncertain, I felt helpless — did not know whether to choose option A or B. There was inner call; sometimes I chose A and sometimes B; with varied success. Every time I failed to choose the more favorable option I was angry with myself that what made me choose the least favorable one!</p><p>Then there was a time, I started to hear an inner voice of mine during those uncertainties to choose a certain option among the available ones. I argued with it and asked for reasons which it did not provide but said something like — “Believe me just go ahead with Option A”. I somehow ignored that inner voice and almost always chose the other ones which again led to similar least favorable outcomes.</p><p>Since the last 5–7 years I started to listen to that inner voice and chose the option the voice suggested. The outcomes were more favorable to me or at least I did not repent that choice. In the very few cases, I chose a different option than the suggested one, I paid from a heavy to a moderate price. These uncertain situations are quite well spread in my life — personal and professional; starting from whether to cook paneer or shrimp on a weekend dinner for friends, going on a second date with someone, half-guessing a question in driving theory exam, to guessing the amount of work a particular software functionality needs to be delivered to user. I am not usually uncertain; rather the opposite is true — I like to know things, hence most of my life decisions are made with certainty. If that sounds I did not make wrong choices in my life that’s not true; what I mean is most of the time I choose with certainty. But as I am spending more time on this planet earth and not just participating in life but enjoying it, making choices during uncertainty is becoming easier; I just listen to my core which mostly knows what I will like. I will continue this path of learning more about myself and choosing things wisely, but when uncertainty kicks in I will fall back to the cushion of my inner self which will comfort me with a more favorable choice.</p><p>I do not repent of those least favorable choices I made, that frustration was momentary. To know ourselves better, we should allow ourselves to make mistakes /make wrong choices; just erase the mistake, note down the learning, and move on with a smile.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edd6cbfc7212" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The tale of two selves]]></title>
            <link>https://medium.com/@tuhinsubhramitra/the-tale-of-two-selves-c2ccd19a41bf?source=rss-bf9bca3c14b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2ccd19a41bf</guid>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[memories]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Tuhin]]></dc:creator>
            <pubDate>Sat, 06 Jul 2019 08:21:57 GMT</pubDate>
            <atom:updated>2019-07-06T08:21:57.697Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LFsApcIQtJyFqBJX" /><figcaption>Photo by <a href="https://unsplash.com/@andrewruiz?utm_source=medium&amp;utm_medium=referral">Andrew Ruiz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The tale of two selves</p><p>Last year, I was on a two weeks long holiday in an island resort where the things I enjoyed are my book, mouth-watering cocktails, sandy beaches, delicious food. It was a break I needed — both my body and my mind were properly rested post that trip.</p><p>In that same year, I went to another holiday (more like a city trip) for 3 days; it was way more active with plenty of walking, museum visits, eating at various places (I am a foodie, so you will hear about food a lot from me), listening to nice jazz music. I enjoyed this trip too.</p><p>Now when I talk to my friends and colleagues about these two trips — I remember the shorter duration city trip clearer than the longer one on the island. I used to wonder about the reason; but after reading <a href="https://www.goodreads.com/book/show/11468377-thinking-fast-and-slow">Thinking, Fast and Slow</a> I know the answer.</p><p>We have two selves — an experiencing one and a memorizing one. The experiencing one log experiences and the memorizing one log the peaks among those experiences. If we had more peaks of joy (or sorrow or pain or relief) over a shorter period of time the impact of the experience in our memory is stronger than an experience that lasted longer but with less wow moments! In our memory, the duration of the experience plays a trivial role. We are fooled by the memorizing self which ignores the duration of experience but checks for the peaks in it to make us laugh or cry — the similar reason a couple who were happily married for 20 long years but divorced recently talk less about the 20 years of peaceful life they had together and often get reminiscent about the troublesome period in their married life.</p><p>Tastes and decisions are shaped by memories, and the memories can be wrong. Inconsistency is built into the design of our mind. We have strong preferences about the duration of pleasure and pain — we want the former to last longer and the later to be brief! But our memory neglects duration and represent the most intense moment of pain or pleasure. Hence, seeking longer pleasure and brief pain may feel momentarily good but in the long run, we would vividly remember the pain if it were more intense than the pleasure that lasted longer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2ccd19a41bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>