 Hello, I'm Omar Fernandez, Director of Strategy and Operations at GitLab and today I am here with Chris. Chris, can you tell me a little bit about what you do and how you first came across GitLab? My name is Chris Evans. I'm a principal DevOps engineer. When I first started, I saw, I was kind of learning the environment and in terms of tooling was a little disjointed. There was a headless SVN server. Systems were kind of segmented into smaller groups, one of which had some like continuous integration processes using like a standalone tool and it was really not homogenous at all. Code reviews were just like, hey, can you hop on this meeting call and I'll share my screen. Like there was no like interactive code review with a tool where you can just leave comments asynchronously. And that was one of the first things that I brought up. So all right, we need to, we need to migrate, you know, in our own time our repositories to Git so we can have tooling that supports modern software development. And the first thing I said is, you know, I would like to do a bake off with all the, you know, the major vendors that have platforms such as these. And we ended up going with GitLab. That's sort of where we are now. We're running GitLab, all of our codes are 100% migrated. We've got build configurations going good and we're very happy with the product and looking to move forward. What were the ways in which you saw your team or you personally benefitting from just being 100% on GitLab and using GitLab for your DevOps cycle? There's a single source of truth. There's a big thing. Like, you know, we know everything we need all the time is in GitLab. GitLab's open handbook is an absolute godsend every day and I work in my job. It seems like anytime I have a question, I'm like, you know, what's the, what's the best way I should be doing this thing, especially when it's like procedurally policy wise? Like, you know, what's the best way to go about this is like, I bet GitLab has it in their handbook and nine times out of ten it does. What do you feel when you're working in GitLab? Joy, I guess is the, the simplest word, the openness of GitLab. It's a very performant tool. It's well documented. It's just a pleasure to use the user experience is great. The UI is great. I can tell there's a lot of love that goes into the tool. Like, it really seems like the, the team that builds the tool really embraces and takes pride in it and it shows in the product. How would you say GitLab has benefited you and your career? I think it's benefited me tremendously. I previously came from a position, started off as a network engineer. I ended up taking on some like sysadmin related roles, but I was never really exposed to the software development life cycle just by the nature of the company I worked for, but just through taking that leap into choosing GitLab as like a project management platform, I was exposed to so many of the tools of the trade for these other industries, software engineering, and I was able to almost learn those in a way, not directly having to use them. Anything else that comes to mind that you want to share with us about your experience with GitLab and your GitLab journey? I hate the old like trope of best of breed, best of suite, but if I already use that trope, GitLab is absolutely a best of suite. It does everything I want it to do. And for the most part, I think it does a wonderful job at all those things, and it just makes my life as a DevOps engineer way easier than it was before. Awesome. Well, thank you so much. I really, really appreciate it, Chris.