Patrick Debois, TweetBridging the gap between projects and operations
Biography: Patrick DeboisIn order to understand current IT organizations, Patrick has taken a habit of changing both his consultancy role and the domain which he works in: sometimes as a developer, manager, sysadmin, tester and even as the customer.
During 15 years of consultancy, there is one thing that annoys him badly, it is the great divide between all these groups. But times are changing now: being a player on the market requires you to get these ‘battles’ under control between these silos.
He first presented concepts on Agile Infrastructure at Agile 2008 in Toronto, and in 2009 he organized the first devopsdays . Since then he has been promoting the notion of ‘devops’ to exchange ideas between these groups and show how they can help each other to achieve better results in business.
Website - http://jedi.be/blog
Presentation: TweetDevops Fools, Tools and other smart things
Now that devops has some traction , tools vendors are happy to re-brand their 'old' tools into 'devops' tools, piggy backing on the new buzzword. We know better, no tool is going to help against bad organization, people thinking in silos or plain stupidity. Still, lots of people get attracted to devops because they came across a new cool tool. Very similar to how testing and unit testing gets them into Test Driven Development. So tools clearly have their place in the eco-system. Devops is largely about changing the culture, but because culture is hard to change it's best to start with behavior, which in itself again can be influenced by introducing new tools. New tools might cause the necessary stir to rethink what people are doing and how they do it.
This session draws heavily on experiences in a recent mission where tools like chef, vagrant, jenkins, fog, amazon where added in the usual tool mix and how it changed workingship relations between devs and ops.
In the talk, the tools are highlighted because of the behavioral and cultural changes then can cause. It does not make devops fool proof or proof for devops fools.
Keywords: Example of keywords: Java, .NET, Architecture, Process, Patterns, Web 2.0, Languages, Code-near, Enterprise, Hot topic etc. Infrastructure as code, Cloud, Automation, devops, Testing, Monitoring, Vagrant, Chef, Puppet, Veewee, Amazon, EC2, Fog
Target audience: A description in a line or two who would benefit from this talk Developers, Programmers, Operations people