<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>waych</author><text>When doing this email trick I&amp;#x27;d often broadcast the fact as I was &amp;quot;declaring email bankruptcy&amp;quot; to let others know I did this and may have missed their email.&lt;p&gt;I&amp;#x27;ve also lead many mass bug closures. Most stale bugs just need a ping or a friendly closure message. The cost to reverse a wrongly closed bug from a bug cleanup sweep is zero, and in the off chance it ignites interest in some other party still paying attention it at least signals intent and starts a conversation.</text><parent_chain><item><author>H8crilA</author><text>If you work for a corporation and feel overwhelmed try what the emacs people did, example for email: 1) select everything in your inbox, 2) mark as read, 3) archive. For bugs it would be unassign everything from yourself, or just close them without fixing.&lt;p&gt;I&amp;#x27;ve done this several times and it&amp;#x27;s magical how you end up losing almost nothing important in the end. I think it works because if something is important enough you&amp;#x27;ll either remember it yourself or it will be communicated to you again, perhaps even via a &amp;quot;higher priority channel&amp;quot; such as the management chain.&lt;p&gt;And if you think I&amp;#x27;m being extreme then yes, maybe, but maybe you haven&amp;#x27;t yet drowned in the never ending stream of problems for a long time.</text></item></parent_chain></comment><story><title>Closing 45% of the open Emacs bugs</title><url>https://lars.ingebrigtsen.no/2021/08/14/10x10/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>colechristensen</author><text>This is definitely a real phenomenon, there is a lot of &amp;quot;work&amp;quot; that if ignored long enough turns out didn&amp;#x27;t need to be done at all.  Lots of things get done which don&amp;#x27;t need to, knowing which is which is a really valuable skill.</text><parent_chain><item><author>H8crilA</author><text>If you work for a corporation and feel overwhelmed try what the emacs people did, example for email: 1) select everything in your inbox, 2) mark as read, 3) archive. For bugs it would be unassign everything from yourself, or just close them without fixing.&lt;p&gt;I&amp;#x27;ve done this several times and it&amp;#x27;s magical how you end up losing almost nothing important in the end. I think it works because if something is important enough you&amp;#x27;ll either remember it yourself or it will be communicated to you again, perhaps even via a &amp;quot;higher priority channel&amp;quot; such as the management chain.&lt;p&gt;And if you think I&amp;#x27;m being extreme then yes, maybe, but maybe you haven&amp;#x27;t yet drowned in the never ending stream of problems for a long time.</text></item></parent_chain></comment><story><title>Closing 45% of the open Emacs bugs</title><url>https://lars.ingebrigtsen.no/2021/08/14/10x10/</url></story>