Did you ever write a follow up to this article? I’d love to hear about the cultural issues you faced in building your team and how you went about creating SaaS offerings and DevOps at NI – a company that was not necessarily familiar with the two before you came along from my understanding.

Thanks!

Correction on slide 19: Azure Queues, readers won’t get the same message. As it is hidden from the queue once a message has been read. This will then stay hidden for a configured time. And you can delete the message once it’s been processed. There is a chance of duplicate processing. But that’s life with queues.

In a larger org, you may have some operations folks that embed into product teams and others that don’t directly. You may have developers working on system provisioning tools, release automation, or monitoring and testing frameworks. Those may have specific role names, but which one is “the” DevOp? None of them, for that’s not a job title.

When agile came, you didn’t start calling developers AgileDevs. If a dev does test driven development, they’re not a DevTester. When a QA person works closely with developers to automate their testing, they’re not a DevQA. At best, agile is an adjective or something put in a job description to indicate “we want people used to collaborating in this way” – but you don’t hire an “Agile.” Same with DevOps. There are DevOps devs and DevOps ops and DevOps who have both skill sets and do some of both.

I’ve just re-published the article I wrote for CVu, for reference:
http://matthewskelton.wordpress.com/2005/10/04/tracking-exceptions-in-web-services-with-guids/

Hope this is some use – I’ll let you know if I make some progress with the log-stitch tool.

Matthew