[ale] DevOps implementation anything more than hubris?

[leam hall]

The ideal of DevOps; greater cooperation between Development, Engineering,
and Operations, is a great way to go.

So far the implementations seem to be application developers ignoring all
the sound experience of Database programmers, Systems Engineers, Operations
staff, and anyone else. "We can do this programatically!" they cry,
ignoring that there are smarter and more experienced people who have
already solved the problems they are just finding.

Chef: "Let's install 8,000 files on a perfectly tuned server."

Ruby: "Make it easy for programmers to write the way they want. Ignore
wanting to find out where they repurposed '+' to subtract."

Node.js: "Why tune Apache or Lighty? Replace it with something slower, less
secure, and with less support."

Infrastructure as code: "Documentation? Planning? Why?"

Can these people come up with a change that is also an improvement?

Not that I'm grumpy today...

Leam
-- 
Mind on a Mission <http://leamhall.blogspot.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20130708/392b33ea/attachment.html>