A lot of documentation is rote. For example new hires usually follow a “getting your dev environment setup” guide which can have small errors or issues. Simply

A lot of documentation is rote. For example new hires usually follow a “getting your dev environment setup” guide which can have small errors or issues. Simply updating the guide to reflect new undocumented processes is a simple thing that brings value and does not require in depth experience. In my mind this is just an extension of good software engineering practices: if your system has a bug or error which requires development time to fix you should find and fix the root cause of the error. Similarly if you are onboarding and you are blocked by undocumented processes you should go out of your way to find out the root cause of the issue and fix it for future developers.