> Because as a sysadmin it is your job to understand how a system works.
No, as a sysadmin your job is to deliver a working system. To do that it usually helps to understand how the system works, but it's not a necessity. As long as something keeps working, and you're equipped to go digging if and when it's necessary, it's fine to not understand or know how something works.
>As long as something keeps working, and you're equipped to go digging if and when it's necessary, it's fine to not understand or know how something works
How do you know it's working if you don't understand it? What's preventing some admin socket to be activated, is the firewall good, etc
you can ride and breed horses without understanding horse physiology or DNA. when you need to fix a broken or lame horse or breed a better horse, knowing how it works helps alot
presumably most sys admins are more akin to vets than riders
No, as a sysadmin your job is to deliver a working system. To do that it usually helps to understand how the system works, but it's not a necessity. As long as something keeps working, and you're equipped to go digging if and when it's necessary, it's fine to not understand or know how something works.