Just getting caught up perusing some recent ;login: issues, and ran across Mark Burgess' article about DevOps[1] in the April 2013 issue. I don't remember a discussion of this on this list, but maybe I missed it or something... Anyways, seems like a good topic of discussion. (FWIW, I tend to agree with his thoughts, although I'm not sure LOPSA [or SAGE] was trying to "unionize" anyone...)
Quote: "Organizations such as SAGE and LOPSA seemed to lose their way, too; by trying to "unionize" the profession, they effectively sent the message that sysadmins just felt poorly treated and underrepresented when they could have led the march to modernize practices and be the heroes of IT emancipation. In fact, the profession as a whole simply failed to adapt to the needs of the rapidly expanding IT industry. Perhaps, if sysadmins had taken on the mantle of responsibility for integrating into business processes, that might have led to their rising up the pay-scale automatically. But system administration has remained, for many, an introverted gaming occupation. Now it needs to become a more disciplined engineering profession. And history is in danger of repeating itself with a new generation of junior admins and impatient developers working with the cloud, or with new scripting frameworks for automation." Should LOPSA "lead the march" to DevOps? If so, how? [1] "Is DevOps the Future of Sysadmin? Bemoaning the Failures of the Sysadmin Profession" ;login: Vol. 38 No. 2 (April 2013), pp 6-7 _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
