Jim has been working on solving engineering efficiency problems for over 20 years, working at firms such as Build Forge and Electric Cloud, pre-dating the inception of Hudson/Jenkins. Jim walks through his experience and how complexity and bottlenecks have shifted around in the decades gone by, and whats in store for the future.
Read the transcript
“Shifting Complexities in DevOps”
Ravi Lachhman 00:06
Hey, everybody! Welcome back to another episode of ShipTalk. I’m really excited to be here with Jim Shilts, who’s a developer advocate. So Jim’s a developer advocate at a cloud native firm called Shipa— but Jim, for the folks who don’t know you, why don’t you tell us a little bit about yourself?
Jim Shilts 00:25
Yeah, thanks for having me on your podcast here today. I’m Jim Shilts, as you said, I’ve been in this space for quite a while; I think it was 2003 when I got into this space. It was before the phrase DevOps even existed— about six years before it did. And about six years ago, I started a group called North American DevOps group, also known as NADOG. That group is really all about getting together [and] learning from each other. We started here locally in Southern California, and it quickly grew into other cities. It used to be the SoCal DevOps Group, and then we had to change the name to NADOG; then we started doing events in Europe a couple of years ago, so rather than change the name again, we’re just known as EuroDOG there and NADOG here.
Now with COVID, you know, we’re doing all these things online— but still, the spirit is the same. It’s about getting together, talking about our industry, learning from each other and doing it in a fun and casual environment. So you can actually make some real connections in this space.