Doesn't need re-explaining but makes me realise we often talk about comments explaining what code does, which leads to "your code should be well-written so it's easy to understand what it does" or "I'm a good developer, I can understand that easily by reading it".
But as you say the question is why - people will often be reading existing code because of a bug, so clearly the thought process that created it had a faulty step somewhere.