On Mon, 1 Jul 2013, Will Dennis wrote:
Should LOPSA "lead the march" to DevOps? If so, how?
Yes. In my experience, developers are not well suited to doing Operations, the mind sets are too difference. Developers tend to be really smart and really good at figuring out problems in a hurry. They also tend to be optimists. These are really good traits for moving forward on development. For operations, this approach doesn't scale very well. Fixing a broken system is often easy. Fixing hundreds of broken systems, not so much. If you are working in a space that can accept failures of production system (like Github), it's not a big deal. If you are working in a space that does not tolerate failures (banking, hospitals, power generation) very well, then the somewhat paranoid attitude of a good sysadmin is very valuable.
Developers don't want to worry about a lot of the underlying details, they just want to write their code. Worrying about the details just wastes their time and energy. A significant part of a sysadmin's job is often making the developers more productive. It's also a matter of making sure proper security is in place, too many developers tend to take shortcuts for convienence (like setting everything under /etc to be world readable).
As sysadmins we need to be leading the effort to move to DevOps by demonstrating the stability, security and productivity that Operation people can bring to the effort.
-- Matt It's not what I know that counts. It's what I can remember in time to use. _______________________________________________ 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/
