<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Disruptive Empathy]]></title><description><![CDATA[For IT and security leaders who know the real vulnerability in their organization isn't technical.]]></description><link>https://www.disruptive-empathy.com</link><image><url>https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png</url><title>Disruptive Empathy</title><link>https://www.disruptive-empathy.com</link></image><generator>Substack</generator><lastBuildDate>Fri, 18 Sep 2026 20:19:57 GMT</lastBuildDate><atom:link href="https://www.disruptive-empathy.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Eric Near]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[ericnear@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[ericnear@substack.com]]></itunes:email><itunes:name><![CDATA[Eric Near]]></itunes:name></itunes:owner><itunes:author><![CDATA[Eric Near]]></itunes:author><googleplay:owner><![CDATA[ericnear@substack.com]]></googleplay:owner><googleplay:email><![CDATA[ericnear@substack.com]]></googleplay:email><googleplay:author><![CDATA[Eric Near]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[The Feedback They Almost Didn't Give You]]></title><description><![CDATA[Why the good news rarely comes first, and almost never comes unprompted]]></description><link>https://www.disruptive-empathy.com/p/the-feedback-they-almost-didnt-give</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/the-feedback-they-almost-didnt-give</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Thu, 06 Aug 2026 16:00:31 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>There is a habit I picked up somewhere in the middle of my career, small enough that I almost don&#8217;t think of it as a habit. At the end of any feedback conversation, once my supervisor has said what they came to say, I ask if there&#8217;s anything else. The answer is almost never no.</p><p>Most feedback conversations are built around correction, because correction is what feels urgent and actionable to prepare in advance. A manager sitting down to plan what to tell you runs through the list of things that need to change, sequences them, maybe softens the language a little, and walks in with that list ready. Whatever positive observations exist tend to travel separately, if they travel at all: mentioned in passing, tacked on at the start as a warm-up, or quietly dropped when the meeting runs long and the corrective items feel like the part that actually has to get said. You leave with a snapshot that&#8217;s technically accurate and still somehow lopsided, because the version of you that got written down is the version that had problems attached to it.</p><p>There&#8217;s a second layer under that one, and it&#8217;s the part I find more interesting: good performance is often invisible by design. Nothing went wrong, so nothing registered as worth mentioning. A deviation from expectation is memorable precisely because it deviates. Meeting the expectation, even meeting it well, just looks like the absence of a problem, and the absence of a problem doesn&#8217;t generate a note in anyone&#8217;s head unless someone goes looking for it.</p><p>Asking is the going-looking. When I ask if there&#8217;s anything else, I&#8217;m not fishing for compliments (though I won&#8217;t pretend it doesn&#8217;t feel nice when one shows up). I&#8217;m asking because I&#8217;ve learned, across enough of these conversations to trust the pattern, that there&#8217;s something positive sitting in there that didn&#8217;t make the first round, not because it wasn&#8217;t true, but because nobody had built it into the plan.</p><p>I&#8217;ve written before that advice is autobiographical: a story about someone else&#8217;s context, offered to you as though it were built for yours. Feedback has a cousin version of that problem. It isn&#8217;t a complete account of your performance. It&#8217;s an account of whatever was salient enough in your supervisor&#8217;s head that week to write down, and salience is not the same thing as significance. The good work you did competently and without drama is real. It just doesn&#8217;t announce itself the way a missed deadline does.</p><p>The part I actually want to talk about, though, is the ambush. Unprompted feedback, even well-intentioned feedback, has a way of landing on you rather than with you. You sit there absorbing whatever arrives, with no say in its pacing or its scope, bracing for whatever comes next because you don&#8217;t yet know how much more there is (a bracing that costs more than people realize if uncertainty is already expensive for your particular nervous system). The moment I ask if there&#8217;s anything else, the dynamic changes, even though nothing about the substance has changed. The request came from me. I opened the door. Whatever walks through it now is something I invited rather than something that happened to me, and that single shift in authorship is most of the difference between a review and an ambush.</p><p>It costs about thirty seconds. It&#8217;s one sentence, asked at the end of a conversation that&#8217;s already happening anyway. And more often than not, it turns up something true and kind that was never going to make it into the room on its own.</p>]]></content:encoded></item><item><title><![CDATA[Most Advice is a Memoir, Part II]]></title><description><![CDATA[What happens when the storyteller has something to sell you]]></description><link>https://www.disruptive-empathy.com/p/most-advice-is-a-memoir-part-ii</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/most-advice-is-a-memoir-part-ii</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Tue, 04 Aug 2026 16:03:17 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Last time I wrote that advice is autobiographical: a story about someone else&#8217;s context, offered to you as if it were a set of instructions for yours. What I didn&#8217;t get into, because it deserved its own space, is what happens when the storyteller has a product to sell you at the end of the story. That changes the transaction completely, and it is happening right now, at scale, to a very specific and very vulnerable audience: people who just lost their jobs.</p><p>Job search advice has the same context problem as any other advice. Someone got hired because of a referral they had, a market that was hiring, a specific gap in their resume that happened to match a specific gap on a hiring manager&#8217;s whiteboard that week. They tell the story afterward as a method (five things I did to land my dream job), because a method is more shareable than a shrug, and because most people, in good faith, misattribute their own outcomes to the parts of the process they controlled rather than the parts they didn&#8217;t. That&#8217;s the ordinary version of the problem, and it was the whole subject of the first post.</p><p>The job search version has an extra layer, and the extra layer is money. Losing a job is one of the more acute forms of vulnerability a person can experience in professional life. Your income is gone or going. Your identity, if you&#8217;re anything like most people in tech, is tangled up with your title in ways you don&#8217;t notice until the title disappears. You are anxious, you are scrolling more than usual, and you are, for a window of time, unusually open to anyone who sounds certain about a way out. That is precisely the emotional state an entire content industry has learned to target, and it targets it with a specific, recursive product: financial freedom, sold to you in the form of a $47 PDF that teaches you how to sell $47 PDFs.</p><p>I want to be precise about what that actually is, because the packaging is designed to obscure it. It is not a skill. It is not an asset. It is a replica of the sales funnel itself, handed to you as though it were the destination, when it is actually just another copy of the machine you already stepped into by watching the video. You buy the map, and the only landmark on the map is the gift shop where they sell the maps. It is a beautifully drawn map. It is laminated. It has testimonials. It was made by someone who has, in a meaningful number of cases, never actually been anywhere except the gift shop.</p><p>This is not a new scheme. It is one of the oldest ones there is, wearing a hoodie and calling itself a personal brand. What&#8217;s new is the delivery mechanism: an algorithm that has learned, with some precision, exactly which faces to put in front of you the week your employment status changes on a professional network. It doesn&#8217;t need to know you lost your job. It only needs to know you started looking at job postings, and searching &#8220;how to negotiate severance,&#8221; and pausing a half-second longer than usual on a video with a rented car and the word &#8220;freedom&#8221; in the caption. The targeting is the product. The PDF is just the receipt.</p><p>I said something like this in a comment a while ago, on someone else&#8217;s post about being laid off and not looking: if I have to choose between interviewing and grifting, interviewing seems a little better. I still believe that, and I want to be honest that I also went and built something in the space between those two options. I started a consulting business, not because I had cracked a formula, but because I had a specific set of skills and a specific set of people who needed them, and that combination happened to be enough to keep the bottom from totally dropping out. I am aware of how close that description sits to the thing I am criticizing. The difference, and it is the whole difference, is that nobody is buying a story from me about how I did it. They are buying the work.</p><p>That is the test, and it is the same test from the first post, just aimed at a sharper target. Ask what the person is actually selling, not what they say they&#8217;re selling. If the answer is a service, or a skill, or a thing that exists independent of whether you go on to sell it to someone else, you are looking at ordinary commerce, and ordinary commerce is fine. If the answer is a copy of the pitch you just watched, dressed up as a shortcut to the freedom the pitch itself promised, you are not looking at advice, and you are not looking at a business. You are looking at a chain letter with a landing page.</p><p>During a job search, this type of non-advice can cost you more than the forty-seven dollars.</p>]]></content:encoded></item><item><title><![CDATA[More writing this week...]]></title><description><![CDATA[Saturday preview (took a tiny break this week, the good kind, not the ominous kind).]]></description><link>https://www.disruptive-empathy.com/p/more-writing-this-week</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/more-writing-this-week</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Sat, 01 Aug 2026 16:02:23 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Saturday preview (took a tiny break this week, the good kind, not the ominous kind). Two posts landing soon.</p><p>The first is part two of &#8220;Most Advice Is a Memoir&#8221; (this one&#8217;s about job searching, and the very specific grift of being sold financial freedom in exchange for a $47 PDF that teaches you how to sell $47 PDFs).</p><p>The second is about feedback from supervisors (specifically, the one question I ask at the end of every review that turns an ambush into a conversation, and what usually shows up once I ask it).</p><p>Back to a normal schedule next week (probably).</p>]]></content:encoded></item><item><title><![CDATA[Most Advice Is a Memoir]]></title><description><![CDATA[What other people's experience can and cannot tell you about your own]]></description><link>https://www.disruptive-empathy.com/p/most-advice-is-a-memoir</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/most-advice-is-a-memoir</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Tue, 21 Jul 2026 16:01:20 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The most useful thing I learned about advice I learned too late, and the way I learned it was expensive. So here it is for free.</p><p>Advice is autobiographical. Every piece of it. The person giving it to you is telling you what happened to them, what they concluded from it, and what they would do again. They are not, and cannot be, telling you what will happen to you. That gap is not a flaw in the advice. It is the nature of advice. The problem is that it gets delivered in the second person, as if it were meant for you specifically, and received in the second person, as if the recipient&#8217;s job is to apply it directly. And almost nobody says out loud: this is a story about me, filtered through my conclusions, offered to you as a suggestion. Try it on. It might not fit.</p><p>There is a difference between taking advice and listening to it. Taking advice means importing someone else&#8217;s conclusion without their context. Listening to advice means trying to understand what they learned and why they learned it, and then asking separately whether any of it applies to your situation. The first is a shortcut. The second is the actual skill. And the reason most people are better at the first than the second is that it&#8217;s much faster, and the person giving the advice usually seems pretty confident, and confidence is contagious in the specific way that other people&#8217;s certainty about your situation can temporarily feel like your own.</p><p>I have been given a lot of advice in my career. Most of it was well-intentioned. Some of it was genuinely good. A meaningful amount of it was, in retrospect, correct for the person who gave it and actively wrong for me, and I spent years trying to figure out why I couldn&#8217;t make it work before I understood that the advice had been generated from a different dataset than the one I was running on.</p><p>I am autistic. I have ADHD. I did not know either of those things for most of the time I was receiving the advice. The people giving it to me did not know either. So the advice was calibrated for a neurotypical person navigating a mostly neurotypical professional world, and I was applying it as if it had been calibrated for me, and then privately wondering what was wrong with me when it didn&#8217;t produce the expected results. &#8220;Be more visible in meetings&#8221; is solid advice if the reason you&#8217;re not visible is that you haven&#8217;t tried. It is not particularly useful advice if the reason you&#8217;re not visible is that you&#8217;re spending all of your available cognitive bandwidth processing the sensory environment and can&#8217;t simultaneously do that and perform spontaneous insight for an audience. Same advice. Completely different applicability.</p><p>This is the sharpest version of the problem, but it is not an unusual one. You do not have to be neurodivergent to receive advice that was generated from a different context than yours. The person giving it might have had resources you don&#8217;t have, or constraints you don&#8217;t have, or a network that made a particular move available to them that isn&#8217;t available to you. They might have operated in a different market, a different era, a different size of company, a different set of relationships with power. The advice might have worked for them because of something they are that you are not, and they may have no idea that&#8217;s why it worked, because most of us are not great at identifying which variables actually drove our outcomes.</p><p>Listening to advice, rather than taking it, means holding the conclusion loosely and asking about the conditions. Not in a dismissive way. Not in the way of someone who has already decided the advice doesn&#8217;t apply. More like: what was true for you when this worked? What would have to be true for me? Where does my situation match yours, and where does it diverge, and how much does that divergence matter? This is a richer conversation than the one most advice gives you access to, and it requires treating the advisor as someone whose experience is genuinely interesting rather than someone whose conclusions you are supposed to download.</p><p>The social dimension of this is complicated in a way I want to name. Advice often comes with an implicit expectation that it will be followed, and visibly not following it can feel like rejection. In mentor-mentee dynamics especially, in startup culture especially, there is a kind of performance of learning where you receive the advice, express gratitude, and then produce a future version of yourself that validates the advice. The alternative, which is receiving the advice, genuinely considering it, and then deciding it doesn&#8217;t apply to your situation, can come across as arrogance or stubbornness or ingratitude, even when it is none of those things. It is just an honest assessment of fit.</p><p>What I have tried to start doing, when advice is offered that I&#8217;m not sure applies, is saying something that is true: &#8220;That&#8217;s useful context. I want to think about how it translates to my situation.&#8221; This is not a polite brush-off. It is an accurate description of what I&#8217;m actually doing with it. I am listening. I am not automatically taking. And I have found that the advisors who are actually worth listening to tend to appreciate this, because they understand that their experience is one data point and not a prescription, and they were offering it as the former and hoping you wouldn&#8217;t mistake it for the latter.</p><p>The people who are least worth listening to are the ones who need you to follow the advice in order for the advice to matter. That is not advice. That is something else. The right trusted advisor won&#8217;t ask you to become smaller.</p>]]></content:encoded></item><item><title><![CDATA[Your Strengths Outlast the Mission Statement]]></title><description><![CDATA[The career cost of writing like you're being watched]]></description><link>https://www.disruptive-empathy.com/p/your-strengths-outlast-the-mission</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/your-strengths-outlast-the-mission</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Thu, 16 Jul 2026 16:01:26 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I used to post like I was in a hostage video.</p><p>Not literally. (The lighting was fine.) But if you went back through my LinkedIn content from my startup years, you would find a person who was enthusiastic in a way that had no texture, supportive in a way that had no specificity, and aligned in a way that, now that I am outside of it and can see it clearly,&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/your-strengths-outlast-the-mission">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[The Block Button Is Not a Career Decision]]></title><description><![CDATA[Reputation and risk]]></description><link>https://www.disruptive-empathy.com/p/the-block-button-is-not-a-career</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/the-block-button-is-not-a-career</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Tue, 14 Jul 2026 16:01:17 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I want to talk about the six weeks I didn&#8217;t block someone, because I think that interval is more instructive than the block itself.</p><p>The situation was not complicated. Someone had been leaving comments on my posts that were designed, with some precision, to make me look like I was out of my depth. Not hostile comments (those are actually easier to deal wi&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/the-block-button-is-not-a-career">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[The Perfect Solution That Never Ships]]></title><description><![CDATA[Why the imaginary option is always the most expensive one in the room]]></description><link>https://www.disruptive-empathy.com/p/the-perfect-solution-that-never-ships</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/the-perfect-solution-that-never-ships</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Thu, 09 Jul 2026 16:02:04 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The best argument against doing the imperfect thing in front of you is that it isn&#8217;t perfect. I have watched entire organizations lose years to this argument, and I want to talk about what that actually looks like from the inside, because from the inside it doesn&#8217;t feel like paralysis. It feels like rigor.</p><p>There is a name for what I&#8217;m describing. The nir&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/the-perfect-solution-that-never-ships">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Stepping-Aside-As-A-Service]]></title><description><![CDATA[What a half-second of small talk taught me about my own factory settings]]></description><link>https://www.disruptive-empathy.com/p/stepping-aside-as-a-service</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/stepping-aside-as-a-service</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Tue, 07 Jul 2026 16:01:52 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A few weeks ago I was at a business networking event, doing the thing you do after the formal part ends, which is stand near the coffee and make small talk with strangers while deciding whether your social battery has one more conversation in it. Mine did, as it turned out, and the conversation was a good one. I struck up a chat with a woman who had bui&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/stepping-aside-as-a-service">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[The Kindest Leader in the Room Can Still Build a Cult]]></title><description><![CDATA[The most popular lightning in a bottle isn't always something you can pour out]]></description><link>https://www.disruptive-empathy.com/p/the-kindest-leader-in-the-room-can</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/the-kindest-leader-in-the-room-can</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Thu, 02 Jul 2026 16:01:42 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I want to be careful here, because the person I&#8217;m describing does not exist as a villain in this story. That is exactly what makes this worth writing about.</p><p>Picture a leader who is, by any reasonable measure, the real thing. Not the LinkedIn version of empathic (which is to say: someone who posts about vulnerability and gives TED-style talks about psycho&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/the-kindest-leader-in-the-room-can">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Disruptive Empathy]]></title><description><![CDATA[On Caring in an Industry That Forgot How]]></description><link>https://www.disruptive-empathy.com/p/disruptive-empathy</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/disruptive-empathy</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Sat, 30 May 2026 16:02:12 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>For the past few years, I've been writing about the things that shaped how I think about work (and people, and technology, and the strange overlap between all three). Those posts are turning into a book. <a href="https://nearestsolutions.com/disruptive-empathy/about.html">Disruptive Empathy</a> is about what happens when you bring genuine emotional intelligence into spaces that have historically treated it as a liability (st&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/disruptive-empathy">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[What We Gave Up When We Got Infinite Scale]]></title><description><![CDATA[Server fans and project plans]]></description><link>https://www.disruptive-empathy.com/p/what-we-gave-up-when-we-got-infinite</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/what-we-gave-up-when-we-got-infinite</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Tue, 26 May 2026 16:01:24 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I remember the hum of the server room in the early 2000s. It was a physical, vibrating thing (a literal heartbeat for the company) that required us to care for it with a level of intimacy that seems absurd now. If we wanted to grow, we had to go buy a <a href="https://www.google.com/search?q=https://www.pcmag.com/reviews/dell-poweredge-r750">Dell PowerEdge</a> and physically bolt it into a rack. We were limited by the length of the cables and the &#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/what-we-gave-up-when-we-got-infinite">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[The Wiring Beneath: Autistic In The Room]]></title><description><![CDATA[Vibes are on/off]]></description><link>https://www.disruptive-empathy.com/p/the-wiring-beneath-autistic-in-the</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/the-wiring-beneath-autistic-in-the</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Thu, 21 May 2026 16:01:39 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I remember the first time I realized that my <a href="https://www.cisco.com/c/en/us/products/switches/index.html">Cisco</a> switches and I shared a common language. They required a specific sequence of commands, a precise syntax, and they didn&#8217;t care about my tone of voice. In the quiet of a <a href="https://en.wikipedia.org/wiki/Server_room">server room</a>, the world made sense. There was a protocol for everything.</p><p>But the boardrooms and the &#8220;huddle spaces&#8221; of the startup world &#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/the-wiring-beneath-autistic-in-the">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Why We Starve the Human Firewall]]></title><description><![CDATA[Investing in technical armor while neglecting the people wearing it]]></description><link>https://www.disruptive-empathy.com/p/why-we-starve-the-human-firewall</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/why-we-starve-the-human-firewall</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Tue, 19 May 2026 16:01:55 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I was sitting at my desk recently, looking at a stack of compliance reports, and I felt that familiar, buzzing hum in my brain that comes when I&#8217;ve been staring at a problem for twenty years. It is a specific kind of frustration (one that my ADHD-i brain likes to fixate on) where the solution is obvious but the budget is nonexistent.</p><p>We talk a lot about &#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/why-we-starve-the-human-firewall">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[The Wiring Beneath: The ADHD Tax]]></title><description><![CDATA[Keeping meaningful work meaningful]]></description><link>https://www.disruptive-empathy.com/p/the-wiring-beneath-the-adhd-tax</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/the-wiring-beneath-the-adhd-tax</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Thu, 14 May 2026 16:01:39 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I used to think that my brain was just a series of poorly labeled <a href="https://en.wikipedia.org/wiki/Patch_panel">patch panels</a>. In the early days of my career (back when we were still crimping our own <a href="https://www.belden.com/products/cable/ethernet-cable/category-5e-cable">Cat5 cables</a>), I assumed that if I just found the right cable management strategy, I could finally stop the signal interference. I thought that if I bought enough <a href="https://www.google.com/search?q=https://www.computerhistory.org/collections/catalog/102633008">PalmPilots</a> or organized my FileMaker Pro&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/the-wiring-beneath-the-adhd-tax">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Need-to-Know Basis: On Hiring Capable Women and Then Making Them Beg for Context]]></title><description><![CDATA[(Part 2 of Read-Only Mode)]]></description><link>https://www.disruptive-empathy.com/p/need-to-know-basis-on-hiring-capable</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/need-to-know-basis-on-hiring-capable</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Tue, 12 May 2026 16:01:25 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>There is a particular kind of hire that happens regularly in tech companies, usually when something has gone sideways. A team is failing to execute. A product is stalling. A function needs to be stood up from scratch, or a relationship has been mishandled, or the company has grown faster than its systems and now things are quietly on fire. Leadership lo&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/need-to-know-basis-on-hiring-capable">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Context Not Included]]></title><description><![CDATA[The accidental clarity of early text chat]]></description><link>https://www.disruptive-empathy.com/p/context-not-included</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/context-not-included</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Fri, 08 May 2026 15:01:27 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>If you&#8217;re of a certain vintage (the vintage that spent considerable time staring at CRT monitors, that is), you probably remember that specific, jarring sound of a computer connecting to the internet via a phone line. That digital screech was the gateway to another world: a world built almost entirely out of words.</p><p>Before the era of sleek smartphone inte&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/context-not-included">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Read-Only Mode: On Working Alongside People Who Are Rebuilding Their Own Authority]]></title><description><![CDATA[There is a particular way some people hold their breath before they speak in meetings.]]></description><link>https://www.disruptive-empathy.com/p/read-only-mode-on-working-alongside</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/read-only-mode-on-working-alongside</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Tue, 05 May 2026 16:03:02 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>There is a particular way some people hold their breath before they speak in meetings. Not the ordinary pause of someone collecting their thoughts. Something else. A scan. They are reading the room for permission, checking the faces of the people with authority before they commit to having an opinion. I noticed it for years, this pre-speech surveillance&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/read-only-mode-on-working-alongside">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Why You’re Depressed After 5 Minutes on LinkedIn]]></title><description><![CDATA[There&#8217;s a specific kind of low-grade misery that settles in around the third or fourth scroll.]]></description><link>https://www.disruptive-empathy.com/p/why-youre-depressed-after-5-minutes</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/why-youre-depressed-after-5-minutes</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Wed, 29 Apr 2026 16:02:39 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>There&#8217;s a specific kind of low-grade misery that settles in around the third or fourth scroll. You weren&#8217;t even feeling bad before you opened the app. You were fine. Maybe a little bored. But then you did it anyway, and now you&#8217;re sitting there wondering why your career feels like a participation trophy while everyone else is apparently disrupting indus&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/why-youre-depressed-after-5-minutes">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Engineering Empathy in Post-Growth Startups]]></title><description><![CDATA[The "service discovery" of human connection]]></description><link>https://www.disruptive-empathy.com/p/engineering-empathy-in-post-growth</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/engineering-empathy-in-post-growth</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Tue, 28 Apr 2026 16:00:27 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The first time I watched a senior engineer give their notice, I was sitting in an open-plan office surrounded by monitors. Half of them were displaying dashboards: service uptime, error rates, p99 latency, memory consumption across a dozen microservices. We knew, at any given moment, the precise health of every system we had built. We had alerts configu&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/engineering-empathy-in-post-growth">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[Efficiency Vs. Busyness Theater]]></title><description><![CDATA[The allure of appearing busy]]></description><link>https://www.disruptive-empathy.com/p/efficiency-vs-busyness-theater</link><guid isPermaLink="false">https://www.disruptive-empathy.com/p/efficiency-vs-busyness-theater</guid><dc:creator><![CDATA[Eric Near]]></dc:creator><pubDate>Tue, 21 Apr 2026 16:01:02 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7JDa!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5a2fc2a4-333a-4239-96b5-a638e0e29b6f_563x563.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>At some point in my mid-twenties I developed a very specific habit: whenever I felt uncertain about whether I was doing enough work, I would open my email client. Not to read anything in particular. Not to respond to anything that required a response. Just to open it, scroll through it, and let the act of checking feel like the act of working. The uncer&#8230;</p>
      <p>
          <a href="https://www.disruptive-empathy.com/p/efficiency-vs-busyness-theater">
              Read more
          </a>
      </p>
   ]]></content:encoded></item></channel></rss>