<?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 Borhan Safa on Medium]]></title>
        <description><![CDATA[Stories by Borhan Safa on Medium]]></description>
        <link>https://medium.com/@borhansafa?source=rss-1d10397068ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*1Pq1NEdhl90Nt7Sj</url>
            <title>Stories by Borhan Safa on Medium</title>
            <link>https://medium.com/@borhansafa?source=rss-1d10397068ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 04:15:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@borhansafa/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[Slow Productivity: Book Notes No. 1]]></title>
            <link>https://medium.com/@borhansafa/slow-productivity-book-notes-no-1-68e9263a4e5b?source=rss-1d10397068ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/68e9263a4e5b</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[cal-newport]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Borhan Safa]]></dc:creator>
            <pubDate>Fri, 21 Aug 2026 19:51:07 GMT</pubDate>
            <atom:updated>2026-08-21T19:51:07.158Z</atom:updated>
            <content:encoded><![CDATA[<h4>What Cal Newport’s three rules taught me about doing fewer things, better</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AbGEp39gMgK6yKLWezqWVQ.png" /></figure><p>I don’t read as much as I’d like to. Between a three-hour daily commute, a full-time job, and a handful of side projects competing for whatever’s left, books tend to lose. Writing about what I read — or in this case, watch — is my way of forcing the habit — if I know I have to turn it into something, I actually finish it instead of letting it stall halfway.</p><p>First one up: Cal Newport’s <em>Slow Productivity</em>, by way of his MasterClass <em>Rebuild Your Focus &amp; Reclaim Your Time</em>, which walks through the same three principles as the book.</p><h3>The Short Version</h3><blockquote><em>Busyness isn’t the same as output. Newport’s fix is three rules: do fewer things, work at a pace your brain can actually sustain, and get obsessive about the quality of what’s left. None of it is about working less — it’s about making the hours you spend count.</em></blockquote><h3>What It’s Actually About</h3><p>Newport calls the default mode of most knowledge work <strong>pseudo-productivity</strong> — using visible activity (packed calendars, instant replies, a full inbox) as a stand-in for real output, because output is hard to measure and busyness is easy to see. It has no ceiling — you can always look busier — which is exactly why it burns people out. <em>Slow Productivity</em> is his attempt at a replacement operating system, built on three principles.</p><h3>The Three Principles</h3><h3>1. Do Fewer Things</h3><p>Every yes you give away is attention you can’t spend on the thing that actually matters. Newport’s fix is blunt: list everything on your plate, cut the least essential, rank what survives, and commit to the top three.</p><p>I had a handful of personal projects competing for the same limited hours. All of them inched forward until I picked one — <a href="https://verifiedislam.com/">verifiedislam.com</a> — and let the rest wait their turn. The uncomfortable fix wasn’t “manage time better” — it was cutting scope.</p><h3>2. Work at a Natural Pace</h3><p>Cognitive effort isn’t a tap you leave running at full pressure — it has a rhythm, and fighting it just produces exhaustion dressed up as commitment. Newport’s advice: double your time estimates, train focus in short deliberate blocks, and match intensity to the task instead of running everything at maximum.</p><p>This one clicked for me through the gym. I train three times a week, and no serious program has you lifting at max intensity every single session — you cycle a heavy day with a lighter one, because that’s what actually builds strength over months. A few months back my body needed more than a lighter day — I took a full week off, ate more, and let myself properly recover. I came back stronger for it. Work rarely gets the same courtesy. We schedule every day like it’s a max-effort day and then wonder why week six feels like collapse.</p><h3>3. Obsess Over Quality</h3><p>Fewer things, done well, beats many things done adequately — but only if you actually protect the time to do them well. Newport’s angle: ship the 80% version instead of chasing an imaginary perfect one, and trust that practice — not perfectionism — is what improves the next attempt.</p><p>As a developer, I feel this one directly. Code I rushed out the door costs me double later, in bugs and confusion I have to untangle under pressure. Code I actually took the time to design properly — even if it meant shipping a day later — almost always needs less babysitting afterward. A lot of that pressure comes from outside, too — constant urgency from clients has a way of pushing “fast” ahead of “right,” even when everyone involved would rather have gotten it correct the first time. Quality isn’t the enemy of speed. Rushing usually is.</p><h3>📚 For the Curious (skip down to the summary image below if you’re short on time ↓)</h3><p>A few ideas from the book that didn’t fit cleanly into the three principles above, but are worth sitting with if you want more than the summary.</p><p><strong>Pseudo-productivity has a history.</strong> Newport traces it back to the shift from factory work — where output was countable, a finished widget on a line — to knowledge work, where output is much fuzzier. When you can’t easily measure whether someone produced anything valuable, visible effort becomes the substitute metric. It’s not that managers (or we ourselves) are being lazy about measurement — it’s that the actual output of thinking is genuinely hard to see from the outside, so busyness fills the gap.</p><p><strong>Seasonality operates at more than one scale.</strong> The book pushes this idea across four levels at once: seasonal (a hard quarter followed by a lighter one), weekly (a hard Monday, an easing-off Friday), daily (a demanding morning, a real recovery block in the afternoon), and occasional (an unplanned afternoon off now and then, with no guilt attached). The point isn’t that any single day needs to be balanced — it’s that balance is something you can engineer across a longer horizon, the same way a training plan spreads hard and easy weeks across a full season instead of demanding every day be identical.</p><p><strong>Time-blocking beats reactive lists — but only if you revise it.</strong> Newport is fairly dismissive of the classic to-do list as a daily driver, arguing that reacting to whatever’s loudest is a worse strategy than deciding your day in advance. His caveat, which I think gets missed: the block plan is meant to be rewritten mid-day when reality doesn’t cooperate. It’s a starting position, not a contract.</p><p><strong>A fair pushback worth naming:</strong> this book assumes you actually control your own schedule — and a lot of people don’t. Advice like “turn down the promotion” or “double your time estimates” is easy to follow when you set your own calendar. It’s much harder when your deadlines come from someone else, or your job is reactive by nature — support, ops, anything client-facing. Newport is writing from the world of knowledge workers and academics, where that kind of control is normal. His principles still help with the parts of your day you <em>do</em> control. They just won’t fix a job where you control very little of it.</p><p><strong>Where this idea can lead, taken all the way.</strong> Newport’s most striking illustration of “obsess over quality” isn’t a productivity tip at all — it’s the mathematician Andrew Wiles, who spent roughly seven years, from 1986 to 1993, working almost entirely alone and in near-total secrecy to prove Fermat’s Last Theorem. He could have spread that time across a dozen smaller, safer results instead — plenty of mathematicians do exactly that — but he’d decided this one problem mattered more than all of those combined, and he was willing to bet years on it. Most of us will never take it that far, and don’t need to. A far more everyday version of the same idea: actually finishing the one course, book, or project you’re learning from, instead of quietly collecting bookmarks across a dozen you never return to.</p><h3>One Image, Three Principles</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*BQbl6ZLSW6etrNpyQEDlsw.png" /><figcaption>Slow Productivity’s three principles, at a glance.</figcaption></figure><h3>The Experiment</h3><p>Not an extreme overhaul — just one constrained bet per principle, with a deadline attached so it doesn’t quietly become a permanent new obligation:</p><ul><li><strong>Do Fewer Things</strong> — Pick one thing on your plate this week that doesn’t need to be there, and drop it.</li><li><strong>Natural Pace</strong> — Run a real 20-minute focus block, no phone, once a day, for five days.</li><li><strong>Obsess Over Quality</strong> — Take one thing you’d normally rush, and give it the extra hour it actually needs.</li></ul><p>I’m doing the same three, starting this week — I’ll report back on what actually stuck.</p><h3>Before You Go</h3><p>No promises about a regular series here — just an attempt to make reading and writing part of the same habit instead of two things competing for the same free time. If this one was useful, there’ll probably be another.</p><p>If you made it this far, I’d love to know: how did you find this one, and did anything here actually land for you? Drop a note below — it helps me figure out what’s worth continuing.</p><blockquote>A Bit About Me</blockquote><blockquote>I’m a full-stack dev in Germany, currently deep in an AI-engineering pivot. More of these coming — find me on <a href="https://www.linkedin.com/in/md-borhan-safa-1bb35265/">LinkedIn</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68e9263a4e5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>