You know what is more important for a infrastructure&#x2F;devops engineer,
previously simply called &quot;sysadmin&quot;? Understanding several compilers and
interpreters (and actually learning several programming languages). Unix C API
(fork(), exec(), file descriptors, pipes, sockets, and others). Understanding
how services daemonize and how they log. Learning how packaging systems work,
how to build a new package, and how to install it. Learning what can be
read&#x2F;detected about the system and what does this information mean. Learning
how does the networking work (address configuration, resolver, routing,
firewall, packet inspection). Traditional networking helpers, along with
several protocols carried out by hand. NSS and PAM, and how the accounts work.
And many, many more <i>basic</i> things.<p>I&#x27;ve never seen anybody understanding the basics, who would have any trouble
picking up anything that was a fad in the last ten years <i>from its
documentation directly</i>. On the other hand, I&#x27;ve seen Docker or Ansible
fanboys that couldn&#x27;t unify accounts across dozen servers in a sensible way,
despite their &quot;modern automation&quot; tools.<p>And screencasts are the second most useless way of conveying technical
material (the top one being podcasts). You can&#x27;t skim through the material,
you can&#x27;t search it, you can&#x27;t copy-paste it, you can&#x27;t print its fragments,
it&#x27;s inherently hard to navigate.