My impression of DevOpsCon 2017 Berlin

Lately I have developed interest on devops. From time to time I try to learn about the new possibilities to automate and optimize my software delivery process, and I find quite exciting to learn about what devops offers today.  I think all developers should at least know a little bit about system administration and devops to understand better the environment their applications are deployed and make themselves more productive.

Last two days I had the opportunity to attend DevOpsCon 2017 conference in Berlin. The conference had a pretty busy agenda full of presentations on five different tracks and four different keynotes. The presentations covered broad subjects such as designing microservices, using tools like Jenkins to create container images, security of docker containers, managing delivery pipelines, managing deployment in a polyglot environment, etc.

What I liked: most of the given talks were about real life experiences from some companies and consultants on how they implemented or helped other companies implement devops in their company structure. Some shared their previous failures and what they learned from them, which I found very useful.

What I missed: most of the talks were plain presentations of slides and very little to no demo. It felt a little dry to just listen to people sharing their experience of using a tool without a single demo about it. I was expecting a lot more hands on demos.

What I didn’t like: some of the talks were given by the conference sponsors. As they were showing use cases around their products, sometimes the talks sounded more of a marketing pitch rather than experience sharing presentation.

As a takeaway from those talks and experiences shared, I understood that quite a lot of companies are already working towards having DevOps people on their teams, be it as a specialized position, or as a mixed responsibility of developers or operations people. I also understood that companies quite often are struggling to fit these positions into their current organizational structures and sometimes there is a need to change the way their teams communicate. Being a relatively new position, it is also one of the misunderstood positions as the responsibilities of a devops person are not quite clearly identified in most places.

If you enjoyed the article, please share...Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInPin on PinterestShare on RedditEmail this to someone

Leave A Comment

Your email address will not be published. Required fields are marked *