> they're fairly unrelated to creating, maintaining, or deploying code Actually it's very useful to know and understand potential misconfigurations. e.g. if y

> they're fairly unrelated to creating, maintaining, or deploying code Actually it's very useful to know and understand potential misconfigurations. e.g. if your 3rd party integration starts failing, it's useful to know the signals that imply their sysadmin messed up a zone transfer. This sort of 'hands-on' knowledge that you only really get from messing around with the daemons yourself reduces downtime and emergency maintenance from hours to minutes.