Not really. It&#x27;s a bad idea to bury past decisions that deserve some sort of &quot;no trespassing,&quot; &quot;thar be dragons,&quot; or &quot;do not feed after midnight&quot; monument off in some historic commit in version control. The problem is that VCSs are completely undiscoverable inside the flow of walking through code to see &quot;where&#x27;s the right place to implement this awesome feature idea I had.&quot; What you might not realize as you start implementing that feature is that it&#x27;s already been implemented 5 times and removed.<p>A comment at the end of a &quot;go to definition&quot; chain serves as a good dead-end indicator that can save lots of overhead and wasted effort.