The DevOps toolkit and its organizational impact

Viktor Farcic: Moving on to the DevOps toolkit, what tools do you see as empowering workers? Do you think that some tools fit better than others into whatever definition of DevOps people have?

Kohsuke Kawaguchi: In the context of broader automation that goes across a number of different things and this ever-expanding need for automation with human control, the tool is obviously the primary means of enabling automation. I know a lot of Jenkins users see the world that way.

Software developers like myself enjoy inventing tools. That's what we do. So, given that world view, it's only natural that we come up with our own tools to bridge those gaps and expand automation even more, because without automation, you can't create shorter feedback cycles, which is a critical part of DevOps. For me, this is the interesting part. It feels closer to what we can solve, as opposed to the organizational structure problem...