>This sounds like a setting expectations issue. Developers are expected to write code, write tests, and troubleshoot issues. Why not also expect them to produce

>This sounds like a setting expectations issue. Developers are expected to write code, write tests, and troubleshoot issues. Why not also expect them to produce written documentation? They often do, when sysadmins say "There is no documentation" doesn't mean that there is literally no documentation it's often the documentation looks like this: "Set up a cron job and have it fire every few minutes" instead of "login to the server located at 192.168.1.25 via SSH using the administrator credentials located in the password manager and type chrontab -e..."