<?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 mohan raj on Medium]]></title>
        <description><![CDATA[Stories by mohan raj on Medium]]></description>
        <link>https://medium.com/@mohanrd.raj?source=rss-d7d96487e623------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*L8CCLz79br9mHJ3WSpgLCg.png</url>
            <title>Stories by mohan raj on Medium</title>
            <link>https://medium.com/@mohanrd.raj?source=rss-d7d96487e623------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:54:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mohanrd.raj/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[Ownership vs Control: What Actually Builds a Software Career]]></title>
            <link>https://medium.com/@mohanrd.raj/ownership-vs-control-what-actually-builds-a-software-career-f3e6a83b3000?source=rss-d7d96487e623------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3e6a83b3000</guid>
            <dc:creator><![CDATA[mohan raj]]></dc:creator>
            <pubDate>Tue, 03 Feb 2026 07:43:11 GMT</pubDate>
            <atom:updated>2026-02-03T07:43:11.140Z</atom:updated>
            <content:encoded><![CDATA[<p>As software developers, we often hear a simple phrase:</p><blockquote>“You should own something.”</blockquote><p>On the surface, it sounds healthy. Ownership implies responsibility, accountability, and pride in one’s work. But in real teams, the idea of ownership sometimes quietly drifts into something else — control.</p><p>This isn’t about blaming individuals or calling out behaviors. It’s about understanding a mindset shift that can make or break a career in the long run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/0*MWQ0j-1721UC9fv-" /></figure><h3>The Different Faces of Ownership</h3><p>In most engineering teams, ownership shows up in three distinct forms.</p><h3>1. Ownership of Work</h3><p>This is the most visible kind:</p><ul><li>Owning a module or feature</li><li>Ensuring delivery and quality</li><li>Taking responsibility when things break</li></ul><p>This type of ownership is essential. Teams don’t function without it.</p><h3>2. Ownership of Knowledge</h3><p>This is deeper and often undervalued:</p><ul><li>Being the go-to person for a system</li><li>Understanding edge cases and trade-offs</li><li>Sharing context and mentoring others</li></ul><p>Knowledge ownership strengthens teams. It builds resilience and trust.</p><h3>3. Ownership of Control</h3><p>This one is subtle:</p><ul><li>“Only I should touch this code.”</li><li>“Everything needs my approval.”</li><li>“If I step away, things will fall apart.”</li></ul><p>From the outside, this can look like commitment. But internally, it creates bottlenecks and silent tension.</p><p>All three look similar at first glance. Their long-term impact, however, is very different.</p><h3>A Simple Story</h3><p>Imagine two developers working on equally critical systems.</p><p><strong>Developer A</strong> tightly controls their module. Documentation is minimal. Decisions funnel through them. For a while, they feel indispensable.</p><p><strong>Developer B</strong> focuses on clarity. They document, review openly, and encourage others to contribute. They build backups for themselves.</p><p>After a year or two, something interesting happens.</p><p>Developer A becomes a risk point. Any absence slows the team down.<br> Developer B becomes a multiplier. The team moves faster, even when they’re not around.</p><p>Both “owned” something — but only one created sustainable value.</p><h3>A Hard Truth About Engineering Careers</h3><p>Here’s a reality many of us learn late:</p><blockquote><em>Organizations don’t reward irreplaceability.<br>They reward scalability and reduced risk.</em></blockquote><p>If a system fails when one person is unavailable, the organization doesn’t see strength — it sees fragility.</p><p>True ownership doesn’t increase dependency. It increases confidence.</p><h3>Redefining What It Means to “Own” Something</h3><p>Ownership isn’t about control. It’s about stewardship.</p><p>Real ownership means:</p><ul><li>Leaving systems better than you found them</li><li>Making knowledge accessible</li><li>Enabling others to succeed</li></ul><p>Ironically, the more replaceable you make yourself, the more valuable you become.</p><h3>A Quiet Self-Check</h3><p>Without judgment, it’s worth asking ourselves:</p><ul><li>Am I owning outcomes or guarding territory?</li><li>Do people depend on me — or grow because of me?</li><li>If I step away for a week, does the team slow down or stay strong?</li></ul><p>These questions aren’t accusations. They’re mirrors.</p><h3>Closing Thought</h3><p>Politics exist in every organization. They always will.</p><p>But impact outlives politics.</p><p>The strongest engineers don’t fight to own systems. They earn influence by enabling others. That kind of ownership survives reorganizations, role changes, and even company exits.</p><p>And in the long run, it’s the kind that builds both great teams and lasting careers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3e6a83b3000" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>