<?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 Nithiya Nanmaran on Medium]]></title>
        <description><![CDATA[Stories by Nithiya Nanmaran on Medium]]></description>
        <link>https://medium.com/@nithiyananu.94?source=rss-b6da710eb55b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uRRaepFuxxTbo32SKCt6JA.png</url>
            <title>Stories by Nithiya Nanmaran on Medium</title>
            <link>https://medium.com/@nithiyananu.94?source=rss-b6da710eb55b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:34:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nithiyananu.94/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[The Importance of Having a Holistic View]]></title>
            <link>https://medium.com/@nithiyananu.94/the-importance-of-having-a-holistic-view-2fcc834b1182?source=rss-b6da710eb55b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fcc834b1182</guid>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[insight-data-engineering]]></category>
            <dc:creator><![CDATA[Nithiya Nanmaran]]></dc:creator>
            <pubDate>Sun, 13 Sep 2026 14:20:45 GMT</pubDate>
            <atom:updated>2026-09-13T14:20:45.869Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bBsVpKawfgilXKafYuOsng.png" /><figcaption>Understand what you are building</figcaption></figure><p>When I started my career in data more than a decade ago, what excited me most wasn’t the technology itself. It was the opportunity to understand how businesses work.</p><p>I was fascinated by the idea that behind every dashboard, report, recommendation engine, or machine learning model was a business problem waiting to be solved. Data was simply the lens through which I could understand the bigger picture.</p><p>Over the years, one lesson has consistently shaped my growth as a Data Engineer and Data Scientist:</p><blockquote><strong><em>Always understand the bigger picture before diving into the details.</em></strong></blockquote><h3>The Trap of Focusing Only on the Task</h3><p>As engineers, we spend much of our time solving highly specific problems.</p><p>A bug in an ETL pipeline.</p><p>A performance issue in a database query.</p><p>A schema change in a source system.</p><p>A failing data quality test.</p><p>On the surface, these may appear to be small, isolated tasks. In reality, each of them can involve hundreds of lines of code spread across multiple repositories, services, and environments.</p><p>The challenge is that when we become deeply focused on a single file, function, or ticket, it becomes easy to lose sight of what we are actually trying to achieve.</p><p>I’ve seen this happen many times throughout my career, including in my own work. We become so focused on solving the immediate technical problem that we forget to ask a simple but important question:</p><blockquote><strong><em>Why does this system exist in the first place?</em></strong></blockquote><h3>Looking Beyond the Code</h3><p>One of the most valuable lessons I learned from my mentors early in my career was to understand how my work fit into the larger ecosystem.</p><p>At the time, I believed success meant writing clean code, meeting deadlines, and closing tickets efficiently.</p><p>While those things are important, I eventually realized that impactful engineering requires much more than technical competence.</p><p>To make meaningful contributions, we need to understand:</p><ul><li>The business problem being solved</li><li>The users consuming the product</li><li>The upstream systems providing data</li><li>The downstream systems depending on our output</li><li>The risks associated with every change</li></ul><p>Once you start viewing your work through this broader lens, your decision-making changes dramatically.</p><h3>The Difference a Holistic View Makes</h3><p>Understanding the business context helps us make better technical decisions.</p><p>When we understand how a product creates value, we become better at anticipating issues before they occur. We gain awareness of dependencies, side effects, operational risks, and long-term implications.</p><p>A successful solution is not simply one that fixes today’s problem.</p><p>It’s one that solves today’s problem without creating tomorrow’s.</p><p>I’ve often noticed that the most experienced engineers spend less time thinking about code and more time thinking about consequences.</p><p>They ask questions such as:</p><ul><li>Who consumes this data?</li><li>What happens if this process fails?</li><li>Which reports or applications depend on this output?</li><li>How will this affect the customer experience?</li><li>What are the downstream implications of this change?</li></ul><p>More often than not, these questions matter as much as the code itself.</p><h3>What Mentoring Has Taught Me</h3><p>Over the years, I’ve conducted more than a hundred interviews and mentored several associates.</p><p>One pattern appears repeatedly.</p><p>Many professionals possess strong technical and programming skills. They can learn new technologies quickly, write efficient code, and solve complex problems.</p><p>However, many struggle to understand how their code fits into the larger ecosystem.</p><p>They know how to build something.</p><p>But they don’t always understand why they are building it.</p><p>Whenever I mentor, I encourage them to start with the business before the technology.</p><p>I ask them to understand:</p><ul><li>What problem does this product solve?</li><li>Who are the end users?</li><li>How does the business define success?</li><li>What value does this solution create?</li><li>How does data flow across the ecosystem?</li></ul><p>Once these questions are answered, technical decisions become easier.</p><p>The architecture makes more sense.</p><p>The data becomes more meaningful.</p><p>The trade-offs become clearer.</p><p>And the solutions become significantly better.</p><h3>Better Engineers Think in Systems</h3><p>One of the biggest shifts in my career happened when I stopped viewing systems as individual components and started viewing them as interconnected ecosystems.</p><p>A seemingly small schema change can impact:</p><ul><li>Data pipelines</li><li>Data warehouses</li><li>Business reports</li><li>Machine learning models</li><li>Customer-facing applications</li></ul><p>Similarly, what appears to be a harmless optimization can create unintended consequences elsewhere.</p><p>Reducing processing time might increase infrastructure costs.</p><p>Improving performance might reduce maintainability.</p><p>Adding flexibility might increase complexity.</p><p>Engineering is rarely about finding the perfect solution.</p><p>More often, it’s about finding the right balance between performance, cost, scalability, maintainability, and business value.</p><p>Without understanding the larger system, making those trade-offs becomes extremely difficult.</p><h3>Why This Matters Even More in the Age of AI</h3><p>Today, AI can generate code, recommend solutions, explain concepts, and significantly accelerate development.</p><p>There’s no doubt that this is a remarkable advantage.</p><p>At the same time, it introduces a new challenge.</p><p>AI can provide answers.</p><p>But it cannot fully understand your business context unless it has been specifically trained or provided with that context.</p><p>It does not inherently know the history behind architectural decisions. It does not understand organizational constraints, regulatory requirements, customer expectations, budget considerations, or long-term product strategy.</p><p>As engineers, our responsibility is no longer limited to writing code.</p><p>Our responsibility is to determine whether a proposed solution is the <em>right</em> solution.</p><p>In many ways, AI makes holistic thinking even more valuable.</p><p>As code generation becomes increasingly commoditized, the ability to understand context, assess impact, evaluate trade-offs, and connect technology decisions to business outcomes becomes a key differentiator.</p><h3>From Developer to Lead</h3><p>Looking back, I’ve realized that career growth often follows an interesting progression.</p><p>Early in our careers, we learn how to write code.</p><p>As we mature, we learn how systems work.</p><p>Eventually, we learn why those systems exist.</p><p>That final stage is where true leadership begins.</p><p>The professionals who create the greatest impact are not necessarily those who know the most programming languages, frameworks, or tools.</p><p>They are the people who understand how technology, business, and people come together to create value.</p><p>They know when to zoom into the details and when to zoom out to see the bigger picture.</p><p>That, to me, is the essence of having a holistic view.</p><p>And in a world where technology continues to evolve at an unprecedented pace, the ability to see beyond the code may be one of the most valuable skills an engineer can develop.</p><h3>What about you?</h3><p>Have you ever solved a technical problem only to realize later that the real challenge wasn’t technical at all, but understanding the business context behind it?</p><p>I’d love to hear your experiences and lessons learned.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fcc834b1182" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Countdown That Changes Everything]]></title>
            <link>https://medium.com/@nithiyananu.94/the-countdown-that-changes-everything-a7c7b48f4ae2?source=rss-b6da710eb55b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7c7b48f4ae2</guid>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[the-5-second-rule]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[mindset]]></category>
            <dc:creator><![CDATA[Nithiya Nanmaran]]></dc:creator>
            <pubDate>Fri, 17 Apr 2026 14:27:55 GMT</pubDate>
            <atom:updated>2026-04-17T14:35:32.932Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Book</em>: The 5-second Rule by Mel Robbins</p><blockquote>“To begin, begin.”<em><br> — </em><strong><em>William Wordsworth</em></strong></blockquote><p>These words by William Wordsworth inspired me to finally write my first article. In many ways, <em>The 5 Second Rule</em> is inspired by the same idea.</p><p>Each of us has a dream we want to achieve. Yet we hesitate.<br> We fear failure.<br> We worry about what others will think or say.<br> We question whether we are good enough.</p><p>Because of these doubts, we often don’t take the first step toward our dreams.</p><blockquote>“The cave you fear to enter holds the treasure you seek.”<em><br> — </em><strong><em>Joseph Campbell</em></strong></blockquote><p>Mel Robbins’ <em>5 Second Rule</em> is a simple yet powerful response to this fear. The rule is straightforward:</p><p><strong>5–4–3–2–1 and DO.</strong></p><p>The moment you have an instinct to act, count backward from five and act, before your mind talks you out of it. This single step can open new doors. Over time, it builds confidence and creates momentum — both of which can have a profound impact on your future.</p><blockquote>“Rule your mind, or it will rule you.”<em><br> — </em><strong><em>Horace</em></strong></blockquote><p>At its core, <em>The 5 Second Rule</em> is about learning to rule your mind instead of being controlled by it. It helps you push past hesitation and achieve more than you are currently achieving.</p><p>I have started implementing this rule in my own life. As Mel Robbins mentions in the book, consistency is the hardest part. Some days are easier than others. But even with small efforts, I can already see how powerful this technique can be.</p><p>The journey ahead is long, but the results are promising.</p><p>And this very article is proof of the rule in action.</p><p><strong>5–4–3–2–1 and DO.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7c7b48f4ae2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>