The thing is that &quot;you can always find it back with Git&quot; only holds when you&#x27;re pretty proficient with Git (or know where to click in a UI like SourceTree, and even that takes a while to figure out). Many people basically don&#x27;t get much further than commit, push, pull. For them, deleting means they need to go and ask someone like you for help to get things back. Commenting keeps them in control.<p>A rule that I like that is 100% enforceable: commented code is allowed, but there needs to be a comment above the code explaining why the code was commented. The effect in practice of this rule is that<p><pre><code>    - People delete code more and comment it less
    - Readers know whether to need to pay attention to the commented code or not.
</code></pre>
Point 1 happens the most. I begin to write down something like &quot;keeping this code around because I&#x27;m not sure yet whether the new code is better&quot; and then I backspace and delete the whole thing because I realise it clearly is.