<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Devops on qone.io</title><link>http://qone.io/tags/devops/</link><description>Recent content in Devops on qone.io</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 20 Dec 2016 00:00:00 +0000</lastBuildDate><atom:link href="http://qone.io/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>different sides of devops in recrutment and engineering</title><link>http://qone.io/posts/devops-in-reality-vs-recrutment/</link><pubDate>Tue, 20 Dec 2016 00:00:00 +0000</pubDate><guid>http://qone.io/posts/devops-in-reality-vs-recrutment/</guid><description>&lt;p&gt;The question is what is devops? How do you recruit a devops engineer. The short answer is you don&amp;rsquo;t. a devops engineer does not exist. The thing about recruiting a so called devops engineer is all a bit undefined and often miss understood and is often used by head hunters and recruiters to find software engineers/ops engineers.&lt;/p&gt;
&lt;p&gt;If we look at it a bit in short first, what is devops! devops is a way of working in a engineering organisation. The way of working generally means a few thing. You start by moving the organisation from a &lt;code&gt;itil&lt;/code&gt; or &lt;code&gt;waterfall&lt;/code&gt; to a more &lt;code&gt;agile&lt;/code&gt; way of working. What this means is that you strive to have a culture that allows people freedom under responsibility, short development cycles, allowing quick adoption and changes, to move fast. The one big part here is &lt;code&gt;trust&lt;/code&gt; in the engineers.&lt;/p&gt;</description></item></channel></rss>