Chris's Wiki :: blog/sysadmin/DevopsBlameProblem Commentshttps://utcc.utoronto.ca/~cks/space/blog/sysadmin/DevopsBlameProblem?atomcommentsDWiki2011-10-01T05:44:25ZRecent comments in Chris's Wiki :: blog/sysadmin/DevopsBlameProblem.By Chris Siebenmann on /blog/sysadmin/DevopsBlameProblemtag:CSpace:blog/sysadmin/DevopsBlameProblem:dfcd12e77d834c700e457c4beecee1e262856334Chris Siebenmann<div class="wikitext"><p>Scott: I've removed your first (duplicated) comment using magic
site admin powers.</p>
</div>2011-10-01T05:44:25ZFrom 68.183.236.8 on /blog/sysadmin/DevopsBlameProblemtag:CSpace:blog/sysadmin/DevopsBlameProblem:a2b3eb65e87a405ae8c05feb33578161afb0cbd3From 68.183.236.8<div class="wikitext"><p>sorry for the double post. if there's a moderator here could you please delete the first one?</p>
<p>@Danny for both ops and qa, i think it comes down to things that are hard to automate and scale, so orgs try to throw manpower into it. there are tools for automating both. i don't know the qa tools that well, but ops tools are not easy. the org i want to work for recognizes hard problems and needs for specialists is a core competency.</p>
<p>Scott Dworkis</p>
</div>2011-09-30T22:53:12ZFrom 194.203.208.142 on /blog/sysadmin/DevopsBlameProblemtag:CSpace:blog/sysadmin/DevopsBlameProblem:3de789e44c11fb20a89f122b9c24a119a9e0e18eFrom 194.203.208.142<div class="wikitext"><p>Huh</p>
<p>Dev? Ops?</p>
<p>Where the f**k is QA in all of this????</p>
<p>Surely the ones who are having problems with stability, features and everything else are the ones who simply do not TEST anything?</p>
<p>If some of the effort put into blame was invested in full unit tests and a <code>separate</code> QA team with fully automated and properly executed testing, this whole DevOps nonsense would never have taken hold.</p>
<p>Danny</p>
</div>2011-09-30T16:49:23ZFrom 68.183.236.187 on /blog/sysadmin/DevopsBlameProblemtag:CSpace:blog/sysadmin/DevopsBlameProblem:e74e3bddb20c84d85a9668ccffa13cd7ecced5b8From 68.183.236.187<div class="wikitext"><p>i'm thinking devops is the gateway concept to realizing ops itself is a scam. ops folks are hired when dev is tired of fiddling with machines. dev decides that's not it's core competency. in reality, the machines matter, and if dev can't keep a handle on them then it's on the way to becoming part of a non-tech org. ops should really be a specialist type of dev, not a human proxy for a pager (basically what tedd said).</p>
<p><a href="http://downdirtyfunkyd.blogspot.com/">Scott Dworkis</a></p>
</div>2011-09-29T21:13:58ZBy Chris Siebenmann on /blog/sysadmin/DevopsBlameProblemtag:CSpace:blog/sysadmin/DevopsBlameProblem:469a557599d194ec89ce83887699b1dbe3c588c4Chris Siebenmann<div class="wikitext"><p>I disagree that DevOps is just about improving communication, because
I think that there's multiple levels of DevOps problems that organizations
can have. Since the full argument got long I put it in an entry,
<a href="https://utcc.utoronto.ca/~cks/space/blog/sysadmin/DevopsProblemLevels">DevopsProblemLevels</a>.</p>
</div>2011-09-28T15:40:04ZBy trs80 on /blog/sysadmin/DevopsBlameProblemtag:CSpace:blog/sysadmin/DevopsBlameProblem:ee201b5287b38ae65826f1fe3da8937b480ad958trs80<div class="wikitext"><p>Now, if only Firefox could embrace devops instead of pushing out a release with new bugs every 6 weeks.</p>
</div>2011-09-28T00:44:55ZFrom 173.164.130.93 on /blog/sysadmin/DevopsBlameProblemtag:CSpace:blog/sysadmin/DevopsBlameProblem:d5c02776606a814beda97ca0f2e7520e5b0e59dcFrom 173.164.130.93<div class="wikitext"><p>My take is that <a href="http://www.hollenback.net/index.php/DevOpsMeansDontBeAnAhole">DevOps Means Don't Be An A-Hole</a>. That's kind of a compliment to what you are saying I think - devops is about improving communications.</p>
<p><a href="http://twitter.com/philiph">Phil Hollenback</a></p>
</div>2011-09-27T18:49:48Z