<story><title>A Heisenbug lurking in async Python</title><url>https://textual.textualize.io/blog/2023/02/11/the-heisenbug-lurking-in-your-async-code/</url></story><parent_chain><item><author>bialpio</author><text>Off-topic but the life story is there to make them eligible to be protected by copyright. IANAL.&lt;p&gt;Source: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;copyrightalliance.org&amp;#x2F;are-recipes-cookbooks-protected-by-copyright&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;copyrightalliance.org&amp;#x2F;are-recipes-cookbooks-protecte...&lt;/a&gt;</text></item><item><author>nickjj</author><text>&amp;gt; I&amp;#x27;d have loved to first read six paragraphs about how the author&amp;#x27;s grandmother raised them on home grown threads and greenlets.&lt;p&gt;With recipes, often times your problem is you want to learn how to make something where having the steps listed out is the most important thing. The story behind the recipe isn&amp;#x27;t important to solve your problem but for tech the story around the choice is important. Often times the &amp;quot;why&amp;quot; is really important and I really like hearing about what led someone to use something first. Often times that&amp;#x27;s more important or equally as important as the implementation details.&lt;p&gt;It wouldn&amp;#x27;t make sense for this post given its title but if someone were making a post about why they chose to use async in Python I&amp;#x27;d expect and hope that half of the post goes into the gory details of how they tried alternatives and what their shortcomings were for their specific use cases. That would help me as the reader generalize their post to my specific use cases and see if it applies.</text></item><item><author>isoprophlex</author><text>Well, I don&amp;#x27;t know, I kinda miss the human angle. I&amp;#x27;d have loved to first read six paragraphs about how the author&amp;#x27;s grandmother raised them on home grown threads and greenlets :^)</text></item><item><author>edfletcher_t137</author><text>This is a great blog post. Concise, lacking fluff or extraneous prose, it gets right to the point, presents the primary-source reference and then gets right to the solution. A bit of editorializing in the middle but that&amp;#x27;s completely allowed when writing this tightly. Well damn done, OP.&lt;p&gt;And also it&amp;#x27;s &lt;i&gt;great&lt;/i&gt; information that I - like I&amp;#x27;m sure many of you - also never noticed. THANK YOU!</text></item></parent_chain><comment><author>iudqnolq</author><text>For some reason whenever this comes up there&amp;#x27;ll be one person saying &amp;quot;I bet you didn&amp;#x27;t know it&amp;#x27;s for copyright&amp;quot; and another saying &amp;quot;I bet you didn&amp;#x27;t know it&amp;#x27;s for SEO&amp;quot;. I&amp;#x27;ve yet to see either prove anything beyond that it&amp;#x27;s a plausible explanation that could fit the minimal known facts.</text></comment>
<story><title>A Heisenbug lurking in async Python</title><url>https://textual.textualize.io/blog/2023/02/11/the-heisenbug-lurking-in-your-async-code/</url></story><parent_chain><item><author>bialpio</author><text>Off-topic but the life story is there to make them eligible to be protected by copyright. IANAL.&lt;p&gt;Source: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;copyrightalliance.org&amp;#x2F;are-recipes-cookbooks-protected-by-copyright&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;copyrightalliance.org&amp;#x2F;are-recipes-cookbooks-protecte...&lt;/a&gt;</text></item><item><author>nickjj</author><text>&amp;gt; I&amp;#x27;d have loved to first read six paragraphs about how the author&amp;#x27;s grandmother raised them on home grown threads and greenlets.&lt;p&gt;With recipes, often times your problem is you want to learn how to make something where having the steps listed out is the most important thing. The story behind the recipe isn&amp;#x27;t important to solve your problem but for tech the story around the choice is important. Often times the &amp;quot;why&amp;quot; is really important and I really like hearing about what led someone to use something first. Often times that&amp;#x27;s more important or equally as important as the implementation details.&lt;p&gt;It wouldn&amp;#x27;t make sense for this post given its title but if someone were making a post about why they chose to use async in Python I&amp;#x27;d expect and hope that half of the post goes into the gory details of how they tried alternatives and what their shortcomings were for their specific use cases. That would help me as the reader generalize their post to my specific use cases and see if it applies.</text></item><item><author>isoprophlex</author><text>Well, I don&amp;#x27;t know, I kinda miss the human angle. I&amp;#x27;d have loved to first read six paragraphs about how the author&amp;#x27;s grandmother raised them on home grown threads and greenlets :^)</text></item><item><author>edfletcher_t137</author><text>This is a great blog post. Concise, lacking fluff or extraneous prose, it gets right to the point, presents the primary-source reference and then gets right to the solution. A bit of editorializing in the middle but that&amp;#x27;s completely allowed when writing this tightly. Well damn done, OP.&lt;p&gt;And also it&amp;#x27;s &lt;i&gt;great&lt;/i&gt; information that I - like I&amp;#x27;m sure many of you - also never noticed. THANK YOU!</text></item></parent_chain><comment><author>yunohn</author><text>When is the last time you heard of online recipe blogs enforcing copyright claims on other blogspam? Ridiculous.&lt;p&gt;The real reason is simple, people who write recipes aren’t robots - they’re expressing their stories and emotions, while explaining how to make food that’s dear to them..</text></comment>