On Feb 15, 2016, at 1:55 PM, Esther Schindler <[email protected]<mailto:[email protected]>> wrote:
If you could get your software development team to change ONE thing, what would it be? ... Maybe it’s because they operate on different time tables; perhaps it’s a difference in priorities; or it may be something else entirely. For whatever reason, despite the industry’s laudable DevOps efforts to bring together the communities (at least in workflow), over the years I’ve heard loud grumbling from Developers about Operations, and from Operations about Developers. Just off the top of my admittedly Ops-biased head: #1 - After we deploy, in spite of all our efforts, things will still break. Disk will fill. Network latency will be variable. Links will fail. Files you expect to write will be read-only. A process will run out of file descriptors. A critical, redundant system you depend on will be down. Systems need to keep running as well as possible in spite of this; we can't raise an InvalidMoonPhaseException and crash. A close (related) second: #2 - We're not done until the customer actually receives the value we intended. "It works on my laptop" is necessary but not sufficient. We're not done with the release at code commit (or package build, or...); we're only done if it's live in prod and customers see/use it. (These aren't meant to be disparaging of Dev; it's a widening of the classical timeline horizon of both groups. Ops needs to be aware of and collaborate much earlier into the Dev process, and Dev needs to be aware of and collaborate much later into the Ops process.) - Dave
_______________________________________________ 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/
