As a set of bullets, I can agree with parts of this list, but the supporting paragraphs of weird assumption and baffling generalization, not nearly as much. Th

As a set of bullets, I can agree with parts of this list, but the supporting paragraphs of weird assumption and baffling generalization, not nearly as much. The phrase "I'm not a coder" can mean all kinds things coming from a sysadmin, context is import. If a sysadmin truly lacks the ability/confidence to write useful code, I'd expect has more to do with the typical nature of the job and organizational divisions than prejudices, hang-ups or fickle behavior of the sysadmins themselves. A role which is too often reactive doesn't leave much time for development. Likewise, development towards the goals of a sysadmin (automation, insight, reliability) too often lead sysadmins to unemployment due to misunderstanding as the relationships between sysadmins who "don't do anything" and systems that don't break. I expect new businesses, particularly the type common on HN could be exceptions, but in many organizations the preferred language of system administration and those of software development don't align. As a result, serious sysadmin code written in say Python as opposed to corporate standard of .NET/Java is putting the sysadmin on an island and likely to be seen as a threat/liability.