A few ops lessons we all learn the hard way (2020)
<i>If a post-mortem follow-up task is not picked up within a week, it's unlikely to be completed at all.</i><p>This one is literally a law of physics.<p><i>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.</i><p>I would add: "If you see a big name company give a talk about some cool thing they made, it's probably already been abandoned by that company."<p><i>Turning things off permanently is surprisingly difficult.</i><p>If you don't have a plan to sunset whatever you're building, you're basically telling your future self to go fuck himself. Unless you plan to quit first, in which case you're telling your successor to go fuck himself.<p><i>The source you're looking at is not the code running in production.</i><p>((cries))<p><i>Mandatory code reviews do not automatically improve code quality nor reduce the frequency of incidents.</i><p>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.