[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[SAGE] Complexity of sysadmin scripts/programs in your organization?
I have searched the archives of this list and found some useful
information about whether sysadmins should be programmers and what
people believe is a script versus a "real" program. I still do not have
a good idea of what people think is an acceptable level of
programming/complexity for the sys admins as a whole.
At some point there is bound to be someone who has enough programming
experience to work on more sophisticated applications that can be very
helpful, but the organization could be in trouble if that person leaves
and no one else has the necessary skills.
How much programming are sysadmins allowed to do in your organizations
and how does the org maintain the level of knowledge to support those
programs after individuals move on? I am talking about long lived
scripts/programs and not throwaway data cleanup scripts.
Are you limiting the languages that can be used to "scripting"
languages? Limiting the complexity? Specifically hiring people with
programming backgrounds?
Thanks,
Eric Wannemacher