Ha! Yeah... it's good practice to revisit and update processes regularly. Many times, they exist because they were better than whatever chaos might have been in place before, but that doesn't mean there isn't plenty of room for improvement. Kind of like software... ;-)

That's also why I'm a huge advocate of writing comments in code describing what the code does.  That way all future developers can fully understand the what and why of what the code does, as opposed not having that perspective and  doing the wild goose chase of 'what the hell is this, and who wrote it??'.

A good programmer should always do that!  It's good practice!  Problem is, getting the balance right!