In this podcast episode, we welcome Kris Buytaert, consulting CTO at Inuits.eu, DevOps evangelist, one of the organisers of DevOpsDays. We talk about the conference, how to introduce CI/CD to teams, and what are some patterns and antipatterns for infrastructure as code. We also discuss why teams are reluctant to spend money on testing and operations, and what happens if they donât.
Edited Transcript
Darko Fabijan:
Hello, and welcome to Semaphore Uncut, a podcast for developers about building great products. Today, Iâm excited to welcome Kris Buytaert. Please go ahead and introduce yourself.
Kris Buytaert:
Iâm Kris, I live in Belgium. About 20-25 years ago, I started playing with Linux and realized that open source was what I wanted to do. I started out as a developer doing projects in Java and other languages.
As I progressed in my career, I started doing more operational work because I knew how to make clusters and work machines. Some 12 years ago, I spoke at a lot of conferences on how we did high availability and scalability and automation, etc.
I bumped into Patrick Debois at a CloudCamp in Antwerp. He had this crazy idea to bring together 70 best of our friends to a small conference and get both operational background, HL background, cloud people, and developers in one room. Thatâs how we started DevOpsDays in 2009.
Since before that, Iâve been helping organizations to deliver software in a better way using open source tools.
The reality of conferences in COVID times
Darko Fabijan:
Great introduction! Whatâs the reality of DevOpsDays in COVID times?
Kris Buytaert:
My last DevOpsDays was New York, 2020. I havenât been to one since, I went to OSMC beginning of the month, in Nuremberg.
Online conferences are really not the same as in-person. The real power of DevOpsDays was the open space, getting to talk with people who have similar experiences, who can share ideas. Itâs hard to mimic online.
There are still DevOpsDays popping up left and right; some of them happen in-person. One happened in Tel Aviv recently, and a lot of people were happy to attend it in person.
But thereâs DevOpsDays that have been postponing 3 or 4 times already. Itâs not easy.
Introducing CI/CD to teams
Darko Fabijan:
I couldnât agree more: the best part of any conference is when you get to talk to a bunch of people.
One of the main things that you wanted to achieve with DevOpsDays is to bridge the gap between operations, DevOps, agile, and structuring work. You gave a lot of talks on how to introduce teams â DevOps, development teams â to CI/CD as a topic.
Can you give us an overview, whatâs the best practice?
Kris Buytaert:
A lot of the work I do is consulting, which means I end up walking into organizations that are struggling, that are failing, and that actually need help. Which does mean, in a lot of cases I only see the shit thatâs around.
But people are struggling because they have a problem they need to solve. They cannot get to production at the speed they want, they have stability problems in production. Basically, they have problems delivering software.
Oftentimes, you talk with different people in the teams and realize that their whole effort into trying to deliver software hasnât included operational people. It has just been developers doing some testing, then building a pipeline. Theyâve been doing continuous integration but how itâs being delivered is totally ignored by the rest of the team.
On the other hand, thereâs successful transformations. Itâs the ones where operational people were involved, and they weâre upfront willing to automate faster, build things. They want to be able to support their developers teams.
Then you tell them that youâre going to do infrastructure as code and continuous delivery on their infrastructure. Youâre going to teach concepts like how to do promotions, test coverage, all those things. When you get teams to understand that, itâs much easier for those people to support their developer teams.