<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>async | Hugo Ferreira</title>
    <link>https://hugo.ferreira.cc/tags/async/</link>
    <description>Recent content in Async by Hugo Ferreira</description>
    
    <image>
      
      <title>async | Hugo Ferreira</title>
      <url>https://hugo.ferreira.cc/hf-bw.jpg</url>
      <link>https://hugo.ferreira.cc/tags/async/</link>
      
    </image>
    <generator>Hugo</generator>
    <language>en-GB</language>
    
    <copyright>2000–2024 by Hugo Ferreira · CC BY 4.0</copyright>
    
    <lastBuildDate>Wed, 18 Dec 2024 01:30:27 +0000</lastBuildDate>
    <atom:link href="https://hugo.ferreira.cc/tags/async/index.xml" rel="self" type="application/rss+xml" />
    <item>
      
      <title>🔗 Warm Handoffs :: Luckymike&#39;s Tech Notes</title>
      <link>https://hugo.ferreira.cc/warm-handoffs/</link>
      
      <pubDate>Wed, 18 Dec 2024 01:30:27 +0000</pubDate>
      <guid>https://hugo.ferreira.cc/warm-handoffs/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://luckymike.dev/posts/warm-handoffs/&#34;&gt;Warm Handoffs :: Luckymike&amp;rsquo;s Tech Notes&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;… generally the guidelines are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;If someone asks a question in the wrong channel, and you know the right channel, link their question in the right channel, tagging them, and explain why you’re making the handoff, along with any additional context you have.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;If someone asks a question in the wrong channel, and you’re not sure where it should go, link their question in a shared channel asking who can help, along with any additional context you have.&lt;/p&gt;</description>

      
      
      <content:encoded><![CDATA[<p><a href="https://luckymike.dev/posts/warm-handoffs/">Warm Handoffs :: Luckymike&rsquo;s Tech Notes</a></p>
<blockquote>
<p>… generally the guidelines are:</p>
<ul>
<li>
<p>If someone asks a question in the wrong channel, and you know the right channel, link their question in the right channel, tagging them, and explain why you’re making the handoff, along with any additional context you have.</p>
</li>
<li>
<p>If someone asks a question in the wrong channel, and you’re not sure where it should go, link their question in a shared channel asking who can help, along with any additional context you have.</p>
</li>
</ul>
<p>That’s it!</p>
</blockquote>
<hr>
<blockquote>
<p>You can’t just <em>recommend</em> them, you have to <em>encourage</em> and <em>reinforce</em> them. They are premised on two values:</p>
<ol>
<li>most people want to help their peers, and</li>
<li>most people want to get their own work done.</li>
</ol>
<p>When inter-team support requests create a conflict between these two values, folks tend to resort to the quickest solution that meets both needs, the Cold Redirect. To break this tendency, you need to establish that a Warm Handoff is expected in lieu of a Cold Redirect, not just preferred.</p>
</blockquote>
<hr>
<p>See also, from <a href="https://luckymike.dev/posts/warm-handoffs-redux/">Warm Handoffs Redux</a>:</p>
<ul>
<li><a href="https://lethain.com/no-wrong-doors/">No Wrong Doors. | Irrational Exuberance</a></li>
<li><a href="/postels-law">Postel’s Law</a> “as sort of an overarching philosophy supporting Warm Handoffs and No Wrong Doors.”</li>
</ul>
]]></content:encoded>
    </item>
  </channel>
</rss>
