I feel like their original quote doesn't support the rest of the article: > it’s time to turn back to old documents to figure out the logic behind some of the

I feel like their original quote doesn't support the rest of the article: > it’s time to turn back to old documents to figure out the logic behind some of the engineering decisions. Dodd says it’s easy to find the engineering decisions, but harder to find the reasoning. It's not that they don't understand what the code is doing. It's that they don't understand why the code is doing what it's doing. Abstractions do not help with why. Documentation does. This is why I try to include as much of the why in the form of comments and long commit messages. Including alternatives considered and why I chose not to use them.