<?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 Mohammed Kanchwala on Medium]]></title>
        <description><![CDATA[Stories by Mohammed Kanchwala on Medium]]></description>
        <link>https://medium.com/@mohammedkanchwala_15827?source=rss-a08f2c003648------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OpwkkregGg8XnXmDmHKMoA.png</url>
            <title>Stories by Mohammed Kanchwala on Medium</title>
            <link>https://medium.com/@mohammedkanchwala_15827?source=rss-a08f2c003648------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:38:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mohammedkanchwala_15827/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 Tech Lead’s Real Job Isn’t to Write the Best Code]]></title>
            <link>https://medium.com/@mohammedkanchwala_15827/the-tech-leads-real-job-isn-t-to-write-the-best-code-89d9b8ef62e9?source=rss-a08f2c003648------2</link>
            <guid isPermaLink="false">https://medium.com/p/89d9b8ef62e9</guid>
            <dc:creator><![CDATA[Mohammed Kanchwala]]></dc:creator>
            <pubDate>Tue, 25 Aug 2026 10:15:27 GMT</pubDate>
            <atom:updated>2026-08-25T10:15:27.940Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Optimising for your own output is the trap. Raising the baseline for the whole team is the lever.</em></p><p>There’s a version of tech lead everyone can picture: the senior engineer who writes the hardest code, reviews every PR, unblocks the team on demand and answers questions at all hours. The one who, when they finally take a week off, is the reason everything visibly slows down. Every one of those skills is legitimate — which is exactly what makes this such an easy trap to walk into.</p><p>The skills aren’t the problem. The strategy is. All that effort optimises for your own ceiling, when the thing that actually compounds is the team’s floor. And over anything longer than a sprint, that’s the slower path — for the team and for you.</p><h3>The ceiling trap</h3><p>The ceiling is easy to see. Solve a hard architectural problem and people notice. Rescue a debugging session that had the team stuck for hours, and they notice that too. Ceiling work feels like progress, and it gets rewarded like progress.</p><p>The floor is the opposite. A junior resolves an incident on their own because you wrote a clear runbook six months ago, and nobody celebrates that. A PR sails through without three rounds of correction because you’d already set the standards, and the friction that never happened goes completely unnoticed. Good floor work erases its own evidence.</p><p>That’s why most new tech leads drift towards the ceiling. It’s familiar territory, it’s what got them promoted, and the feedback loop is immediate. But the asymmetry underneath is the whole point. Ceiling work scales with your time and attention, and nothing else. Floor work scales with the entire team — and keeps scaling long after you’ve moved on.</p><h3>What “raising the floor” actually means</h3><p>In practice, it means a few concrete things. The next developer to touch the code doesn’t need three years of context in their head to change it safely. A review doesn’t hinge on which reviewer happened to pick it up. A new joiner can be genuinely productive in their first fortnight, without hunting down the one person who remembers how it all works. It tends to show up in three places.</p><p><strong>Documentation written for the person who comes after you.</strong> Most engineering docs are written for the person who wrote them. They already hold all the context, so the words on the page make perfect sense to them. The reader arriving cold — no background, no history, just the page — is exactly the person who gets forgotten.</p><p>The test I use for any runbook is simple. Could someone debug this alone, at 2am, having never seen the service before? If the honest answer is “they’d have to ask someone”, the floor is still too low. So write it for that person, not for yourself.</p><p><strong>Code review as teaching, not gatekeeping.</strong> You can leave a review comment two ways. One just says what’s wrong. The other says what’s wrong, why it matters, and what a better approach looks like — with enough reasoning that the author could get there on their own next time.</p><p>The first takes thirty seconds and produces a correction. The second takes two minutes and raises the floor. A tech lead who only ever corrects will spend the next year catching the same class of mistake, while one who explains the reasoning lifts the bar across the whole team. That comment was never really about this PR — it was about the next six.</p><p><strong>Making the “obvious” things findable.</strong> Every team carries knowledge that feels obvious to whoever has been there longest: how to stand up the dev environment properly, which service owns which domain, what to check first when a particular test starts flaking, the config detail that tripped up three people last year. That knowledge lives in your most senior heads, and it stays silent right up until someone needs it and the person who holds it is on a plane.</p><p>Raising the floor here means treating your own hard-won context as a liability to get out of your head. Write the runbook before you need it. Build the script. Put the architecture notes somewhere people will actually find them — not buried in a slide deck from eighteen months ago that nobody remembers exists.</p><p>The goal is a team where the absence of any one person doesn’t turn into a crisis. That’s not disloyalty to your own expertise. It’s the thing a senior engineer is actually there to build.</p><h3>Why this is the career lever</h3><p>Here’s the part that catches people out. If you’re aiming for Staff or Principal, the floor matters more than the ceiling — because engineers at that level are judged on impact that reaches beyond their own hands. The question stops being “what did this person build?” and becomes “how did this person change the way the team builds?” And that’s a floor question through and through.</p><p>The engineers who make that jump usually aren’t the highest individual throughput on the team. They’re the ones who left it measurably better than they found it — quicker to onboard, more consistent, less dependent on any one person’s heroics. You can’t manufacture that in a performance review. But you can point at the runbooks that got used, the standards that took hold, the new engineer who was independent in week two instead of week eight. Ceiling work looks good this quarter. Floor work is what compounds over years.</p><h3>The honest version</h3><p>There’s a real tension here worth naming. Floor work takes longer to feel like progress, and it rarely earns the same applause as solving the problem everyone was stuck on. Most of the incentives we work under — sprint velocity, ticket counts, PR throughput — quietly measure the ceiling. So the short-term pull towards it is completely rational. Most people optimise for what gets noticed, and floor work is almost unnoticeable by design.</p><p>The tech leads who build genuine leverage are the ones who get comfortable with that — who find real satisfaction in the problems that never happened, not just the fires they personally put out. And if you find yourself always being the one who unblocks, always the one everyone waits for, always the one the team can’t function without, that isn’t the success it’s dressed up as. It’s the ceiling trap wearing a senior title.</p><p>The job is to make the team not need you for the basics. That’s exactly when you’re free to go deep on the ceiling-level work only you can do — and when that work actually moves things forward, instead of just holding the floor up from underneath.</p><p><em>If this resonated, follow me here for more on engineering craft and the IC leadership track. I publish roughly weekly.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89d9b8ef62e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>