<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>tayo42</author><text>&amp;gt; I would add: &amp;quot;If you see a big name company give a talk about some cool thing they made, it&amp;#x27;s probably already been abandoned by that company.&amp;quot;&lt;p&gt;Watching this happen was insane. Some team kept giving talks about how great their thing is that no one in the company was using. Major conferences immediately lost credibility seeing that happen. Sometimes it feels like everybody is just bullshitting, maybe because it really is like that.</text><parent_chain><item><author>0xbadcafebee</author><text>&lt;i&gt;If a post-mortem follow-up task is not picked up within a week, it&amp;#x27;s unlikely to be completed at all.&lt;/i&gt;&lt;p&gt;This one is literally a law of physics.&lt;p&gt;&lt;i&gt;People give talks at conferences not to convince others that their work is awesome and totally worth the time and effort they put in, but themselves.&lt;/i&gt;&lt;p&gt;I would add: &amp;quot;If you see a big name company give a talk about some cool thing they made, it&amp;#x27;s probably already been abandoned by that company.&amp;quot;&lt;p&gt;&lt;i&gt;Turning things off permanently is surprisingly difficult.&lt;/i&gt;&lt;p&gt;If you don&amp;#x27;t have a plan to sunset whatever you&amp;#x27;re building, you&amp;#x27;re basically telling your future self to go fuck himself. Unless you plan to quit first, in which case you&amp;#x27;re telling your successor to go fuck himself.&lt;p&gt;&lt;i&gt;The source you&amp;#x27;re looking at is not the code running in production.&lt;/i&gt;&lt;p&gt;((cries))&lt;p&gt;&lt;i&gt;Mandatory code reviews do not automatically improve code quality nor reduce the frequency of incidents.&lt;/i&gt;&lt;p&gt;The primary purpose of mandatory code reviews - without a sensible plan of who, when, why or how - is just for people to nitpick your code.</text></item></parent_chain></comment><story><title>A few ops lessons we all learn the hard way (2020)</title><url>https://www.netmeister.org/blog/ops-lessons.html</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>marcosdumay</author><text>A &amp;quot;plan to sunset&amp;quot; something looks like an incredibly alien concept to me. How do you do it when people keep finding new uses for whatever it is?</text><parent_chain><item><author>0xbadcafebee</author><text>&lt;i&gt;If a post-mortem follow-up task is not picked up within a week, it&amp;#x27;s unlikely to be completed at all.&lt;/i&gt;&lt;p&gt;This one is literally a law of physics.&lt;p&gt;&lt;i&gt;People give talks at conferences not to convince others that their work is awesome and totally worth the time and effort they put in, but themselves.&lt;/i&gt;&lt;p&gt;I would add: &amp;quot;If you see a big name company give a talk about some cool thing they made, it&amp;#x27;s probably already been abandoned by that company.&amp;quot;&lt;p&gt;&lt;i&gt;Turning things off permanently is surprisingly difficult.&lt;/i&gt;&lt;p&gt;If you don&amp;#x27;t have a plan to sunset whatever you&amp;#x27;re building, you&amp;#x27;re basically telling your future self to go fuck himself. Unless you plan to quit first, in which case you&amp;#x27;re telling your successor to go fuck himself.&lt;p&gt;&lt;i&gt;The source you&amp;#x27;re looking at is not the code running in production.&lt;/i&gt;&lt;p&gt;((cries))&lt;p&gt;&lt;i&gt;Mandatory code reviews do not automatically improve code quality nor reduce the frequency of incidents.&lt;/i&gt;&lt;p&gt;The primary purpose of mandatory code reviews - without a sensible plan of who, when, why or how - is just for people to nitpick your code.</text></item></parent_chain></comment><story><title>A few ops lessons we all learn the hard way (2020)</title><url>https://www.netmeister.org/blog/ops-lessons.html</url></story>