I find this useless advice. I didn't write or are aware of much of the code I'm part of. Or remember some of the code I did write. Or even understand the ram

I find this useless advice. I didn't write or are aware of much of the code I'm part of. Or remember some of the code I did write. Or even understand the ramifications of what the change log means. All assuming it's a well written change log. You need external process to ensure upgrades don't break things. Not a 'read the change log' policy so someone can blame you post breakage cause then it'll be easy to find issues in the change log.