 Hi, and welcome to a special episode of OpenShift TV. I'm Stu Miniman, and back in 2020, really everything changed. Many companies out there looked at what was going on and said, oh, we need to get in touch with our customers. At the time, I was in the media industry, and we said every company during this pandemic is going to become a media company themselves because, yes, there are media services that you can use, but that we need to understand this. At that time, Red Hat looked at things, and there was a small group of entrepreneurial people that said, how do we take advantage of this? The technology for streaming is a relatively low bar. We have good content and great community, and they started OpenShift TV. It's a memorable build date, especially if, like me, May the 4th is a holiday in your household because, spoiler alert, it is Star Wars Day, and if you can't guess by my background, yes, I'm a big Star Wars fan. So that was the launch of OpenShift TV, and I want to bring in the voice of OpenShift TV, the creator of the program, Chris Short. Chris. Thank you, Stu. I appreciate that intro, and it is kind of funny that we're sitting here today, a, what, 16 months, 18, I can't count anymore. I have to give it up. The map isn't my thing anymore. And days and numbers have become meaningless since, you know, I've now been working at Red Hat for a year, Chris. Right. You and I have talked numerous times over Google Meets and Zooms and things like that, but we've never met in person. Never met in person, no. So, yeah. So, can you just, you know, give us the setup, you know, what were you doing at Red Hat and, you know, what was that meeting like to say, like, hey, we're going to flip on a camera and talk to the world. So, like, we had a very, like, bandwidthy kind of problem, right? Like, we had a few TMMs, and they could only talk to a few customers at a time, right? Like, there's only so many hours and a day kind of deal, and we have to feed these people and let them sleep kind of thing. So, we needed to scale that up, and, you know, we knew that. We just didn't know how. And then, one day, our boss, Chris Morgan, was talking to Andrew Sullivan from, you know, Ask an Open Shift Admin, you know, hey, you know, your kids are doing what on, huh? Oh, they're streaming their video game stuff on Twitch. And, like, I guess they're meeting Glitched or something. And then it's like, huh, lightbulb started coming on. It's like, maybe we should try some live streaming stuff. And so we did. And then, like, we set up a schedule for the first week, and we were like, all right, this is cool. But we realized, you know, I mean, we can get further into it later on. But we realized it, like, very quickly, right? Like, we had 1,000 followers on Twitch, which was like, whoa, hello. Okay, cool. And, you know, that was, like, a very, like, eye-opening event, because people wanted us to see maybe break stuff on, you know, live TV, for lack of a better term. And apparently fixing it in front of them teaches them many things. So we learned very quickly that it was a great learning asset for everybody. And then, you know, we could point people towards, hey, you're going to QCon next week or catching it virtually, you know, that kind of thing. We could still do a lot of the normal stuff we would do as TMMs, right? Like, hey, getting, you know, our customers to the, you know, the summits of the world that are out there now. And can still, you know, interact with, you know, normal people, like they would at a conference. And so we built out a full schedule of shows. And I guess, you know, for, you know, I think most of the Red Hat audience are going to know, you know, TMM is a technical marketing manager. Oh, yes. So doing demos, hands-on type of stuff, very different. So when I was at theCUBE, I was doing interviews. It was discussions and analysis segments, people talking. The content for OpenShift TV is a little bit different. So live streaming, typically, you know, longer form content, like... We avoid slides if we can. Yeah. Not slides, but there's a screen up for good parts of the discussion. So, and there's a number of different shows out there. So, you know, how did you break up, you know, hey, is this the same kind of demos that we would have been doing at a KubeCon, a Red Hat Summit, things like that? Or is it just things they're working on? How did the kind of the creating the shows, the hosts, and what content got done? How did that get sorted out? So, I mean, let's take Christian Hernandez. I think he's the perfect example. And he's done the theory... And the host of the GitOps Guide to the Galaxy, something like that. Yes, yes, yes, yes, exactly. Host of the GitOps Guide to the Galaxy has really embraced the live streaming format, right? Like, and, you know, he said early on, he's like, you know, I want to be the Kelsey Hightower of GitOps. And I was like, well, hang on tight, buddy, because here we go. You know, you need a show, you need this, you need that, you know, and, you know, he's started up the open GitOps, you know, initiative and all these things have happened. And like, he's just so great at demonstrating things live on air, and then when something goes bump in the 90s, so great at, you know, troubleshooting it and like saying, oh, this is how you would check this. And, you know, so he's done this amazing successful job of just making live streaming work for his content. But to answer your question to an extent, right, like we're all in charge of some component of OpenShift. So as new things come out or new features get released, even if they're, you know, the UX teams features, why not do a show about it, right? And if you can do a show about it, then we can do some regular cadence to it. And yeah, you can get your feedback, you know, from a live studio audience kind of thing and not studio, but a live audience. And, you know, those sessions have been great. The developer experience office hours was Serena from the future. She's got a nickname now, right? Like customer support actually asked us one day, you know, I was in some meeting that I got called into. It's like, hey, is there any way you could like flash some, this is a future facing feature thing. Don't try this in your cluster, you know, right now kind of deal because they were getting calls. They were trying stuff they were, you know, we were demoing on OpenShift TV and maybe it wasn't quite fully baked because it was tech preview or dev preview and it was missing something, but we had a fix for it in place to make the demo work. So yeah, like our job is to make those demos like as early as possible. And showing them off is, you know, something that we would normally do going from conference to conference to conference, right? Like I would travel quite a bit, so would everybody else on the team. And, you know, so if you're now, okay, let's do a weekly show, let's do a bi-weekly show. So now it's like, oh, okay, I'm doing an hour of solid content, maybe longer if you need it. But, you know, I know the exact time and date and what resources I'm gonna have available, everything in your home, you know? So it's literally sky's the limit, right? So we have had generated tons of great like demo facing content type stuff. That's pretty obvious. Chris, you know, when I first joined Red Hat last year, you and I had a number of discussions talking about live versus prerecorded. The demos, it's not Camtasia. It's not, you know, I buffed it and polished it. And, you know, here, let me hit play and give you a talk over what they're doing. I mean, these are, you know, live real demos and talk about why live, the engagement, you know, the audience, what kind of feedback you have because that's something normally, you know, I've seen Kelsey Hightower speak and he'll go do some stuff. You know, the audience isn't lobbing questions at him usually in real time. Right. So, yeah, no, and that has contributed to some of the intimidation factor with some folks, right? Like they can ask questions at any point in time. It's like, yes, but you don't even see them if you don't want to, right? You don't have to open the chat and, you know, see it will be your filter for you kind of deal. So, you know, there's three things that we'd like to make sure we tell people and the liveness of it is core to that. One of those three things is we embrace failure on this channel, right? Like we wholeheartedly accept that things will break. An API call might get missed while you're, you know, firing off 20,000 of them at once kind of thing. Maybe, yeah, okay, something breaks. Let's go fix it. And that we've gotten two great pieces of feedback, like multiple emails telling us this. Like it really humanizes the brand of Red Hat, right? Like, yeah, we're humans too folks, you know, even though we're that quote experts in the box, we can still make mistakes and things still do go bump in the night, you know, and various cloud providers or wherever your home network, you know, whatever you're working on, you know, case in point, all my network outages this past summer. The, and then the next thing we've been told is that it teaches people how to troubleshoot, which, you know, if you're watching this right now, you understand how hard it is to learn how to troubleshoot. Normally that only comes through experience. You don't get to see something break live and then all of a sudden people are now diving into this problem and be like, oh, is it this, is it this, is it this? And then, you know, to see the product kind of unveil itself over the year and a half or so, we've been doing this. A lot of improvement has come into the product to make it like easier to use and bringing, you know, forward very useful information in a timely fashion. That's, you know, we've seen that because of live streaming, I feel like, and it's pretty cool. Yeah, so other than the aforementioned, you know, network issues that you were having, you know, what, what, what broke, you know, what, what caused issues, you know, what, what, what learnings have you had? So I just published a blog post about this because like it had been in the backlog for so long and I was like, I'm going to write this this weekend. There was actually like an area wide outage affecting much of the fiber line that runs adjacent to the main road that runs in front of my neighborhood. So they had done some maintenance and then all of a sudden we get these really weird like interruptions in service. And like it would take down the entire channel sometimes. And, you know, we're using remote boxes and it shouldn't do that, but it did. So luckily Bobby, the intern was here at the time so we got him, you know, plugged into the, you know, production systems and he can produce shows. But it took a lot of, I think it was five visits from Comcast business. Like keep in mind, like I upgraded my like level of service with Comcast because of the live streaming because I was sending out so much contents, right? Like the data camps that existed were just getting blown through in the first 15 days. So yeah, outage after outage after outage, and finally it was just like, I'm gonna build a status page for my house, right? Go build status.crisshort.net. And then now I have this thing that I can show any Comcast agent on Twitter, on the phone, anything. Hey, there's been a consistent outage issue here, right? Like something's very bad and I'm not the only one reporting it because we're seeing it on, you know, the various social media sites that are out there and it's like, can you just fix it? Like that'd be nice, stop coming to the house. Like, I mean, they had like some orange cord from literally the backside of my house all the way around the back, up the side yard, plugging into the side of the house because they just wanted to replace the cable to make sure it wasn't that, you know? So it was, I mean, it got so bad to the point where I bought a like MyFi, a 5G MyFi hotspot thing. So that I could, you know, somehow keep the show going while Comcast did whatever during the summer. But yeah, I mean, it was actually a long-term issue that helped prove that there was a bigger, wider area issue. Yeah, unfortunately, any of us that have ever done any streaming were well-familiar with the speed test site and lots of ways to troubleshoot, you know? Wait, is it me? Is it something else? Is it the internet? Yeah, and like, you're leveraging the cloud now for, you know, a lot of the activity. So it's not a box, you know, sitting in your home that's doing it. Was that, when you started OpenShift TV, when did you, how long did it take you to say, oh, okay, I need to, you know, my poor system and whatever graphics card is, you know, crank into a halt. I need to do something else. So it was kind of funny, right? Like I got into live streaming for the Kubernetes community meetings that would happen once a week. And when, you know, when we were like, okay, let's start the channel. I was like, all right, I can do this pretty low budget, right? Like I had, you know, Logitech webcam. I had this microphone already because I was doing like a lot of podcasting and stuff. So, so yeah, I was like, okay, I've got the box for the live streaming meetings that I use OBS on anyway. Let's just go ahead and use that. And that worked for a little bit. And then it was just like, you know, a certain version of OBS, you know, it not having a, you know, strong enough graphics card, that kind of thing, we'd start losing some packets here and there during shows, like especially, you know, if there's a lot of motion on screen or anything. So Eric Jacobs and I worked, and it was mainly Eric that worked very hard to figure out like, where can we get, you know, since OBS is like a first class citizen for Windows because of gaming, where can we get a Windows 10 rig in the cloud? Even though OBS isn't supported in a VM, all we need is a cloud instance with a GPU, technically speaking, right? And so we did this really unsupported thing and actually like productized it. We put it in, you know, it's open source. All the stuff we do is open source pretty much. You know, you can't have the keys to the passwords or anything, right? Like, sorry. But yeah, all, we have this all documented and it's all laid out. And, you know, you basically download this repo locally and off you go, once you have your Azure account, all, you know, plugged in and everything. So it's an amazing like necessity problem that we had to solve because it was like, Windows 10, not Windows Server because getting OBS working Windows servers a nightmare. So it was just very much like, okay, we got Windows boxes in Azure with GPUs. Let's make this work. And we did and that generation of GPU is now expiring next year sometimes. So we've upgraded a generation now. We've been using them so long. And they just work, right? Like they have so many, you know, so many cores and enough RAM to sync a ship kind of thing because they have a GPU, right? They cost only like a buck an hour. So production costs are pretty low. Yeah, yeah. I mean, overall, if you look at, you know, rather than, you know, dumping a few thousand dollars into a machine and then worrying about all of the issues about, you know, internet connectivity and all that stuff. And everything like that, you know, hey, the promise of the cloud, you know, Microsoft, it works, Azure doing great. And yeah, I mean, Chris, I approve your expense report on that. And it's not free, but it's not, you know, it's not ridiculous for, you know, what we've been doing with OpenShift TV. So it's interesting to see. And, you know, we've been looking at, you know, there's lots of SaaS alternatives out there. And that market has been growing in leaps and bounds. Yeah, it's amazing, right? Like we're using Restream right now and I've been poking around on their live studios because they didn't have a live studio until the pandemic hit, right? Like they didn't even think about having one. But then it became a product that they needed because everybody was doing all the streaming now. And, you know, as that, you know, web-based, browser-based platform has expanded. It's been awesome to watch because they just keep adding features. And it's like, eventually it's just gonna be OBS on the web folks, right? Like you're not gonna dial into Zoom meetings and have- Well, it's one of this- I mean, Chris, we're leveraging Zoom for the guest management portion of this activity. It does all of that. In webinar, there's things like that. It wouldn't be too difficult for Zoom to extend what they're doing into this space. That's very true. Love to see them, you know, to do some things along those lines. So scaling is something we talk about, Chris. So we'll talk a little bit, you know, how many shows did you start out with and where did it go? Oh, man, I don't even, like I think we had like a show a day that first week. And then we started building up a normal cadre of shows, right? Like we had an admin focus show. We had our get-offs focus show. But then, you know, we wanted a director level kind of show, right? Like director level and on up kind of show where we could talk high level to folks about like important things in the cloud native ecosystem and how it impacts their- Yeah, in the cloud show, which, you know, hey, Chris, my smiling face has been on the front page of Red Hat Live Streaming for a little bit too long, but that's another topic. I think we have a meeting with them tomorrow morning. But yeah, the, you know, when it started off, it was like a Hugo page that I designed, right? Like it was nothing fancy or anything, right? Like I was like, this is ugly, but it's the best I can do. Sorry. So eventually like we got a real website and then eventually became a real Red Hat website. And, you know, it's evolved from, you know, this kind of bootstrap, you know, very much a startup within a company kind of thing into this like smoothly running freight train kind of thing, you know, chaos some days, like tomorrow, I think there's four or five live streams total on the channel, including what's new in four, nine briefing. So don't miss that. Those are always nice to catch up on what's coming down the pipe in the next release of OpenShift. So yeah. But total, I mean, you were up to a couple dozen shows at the moment. So I think at the peak, it was 26 shows. Right now we're running 15 with like a couple extras here and there. And that range from, you know, once a week to monthly or even a little bit longer. Yeah, we had one show that was on a three week cadence. We had multiple shows on bi-weekly cadence. We had multiple shows on weekly cadences and we had some shows that were like, it's only event based, you know, and that, you know, it all works out in the end. Right? Because there are certain ones that KubeCon or Summit that there were special activities that that plugs into too. Right. And it's cool how we kind of just wove everything together with our events and with our everything else, right? Like we streamed OpenShift Commons gatherings, right? Like we've streamed, you know, hackathons for OKD and, you know, like long, long streams. Like we've done those marathon type streams before and it's, those are, those are great, right? Like if you really want to learn a deep dive into a particular topic, but I like the freshness and the TV style of the hourly show. It works very well. But, you know, sometimes you do need two hours to demo something, especially if it's like cloud-based Kubernetes type stuff, you know. Yeah. And of course it's all available on demand too. So it's always interesting to look at the metrics of something and some shows have a big live audience. Some of the, you know, executive level ones get, you know, some nice on demand and, you know, various pieces that hit there. I know I've leveraged a lot of it. So I've got a lot more questions for you, but I think we've waited long enough, Chris, to share. There was there was some news that we kind of teased in the piece there. So as you said, it's been, you know, well over a year, many of the shows going through, there's been some reshuffling. Why don't you share with the audience, you know, your news? So I have decided to take a new role at another company. And I didn't come to that decision easily. A few events had to occur to make me realize that I wanted to do that. And when I say events, I mean like personal events, not like, you know, red hat stuff, right? Like red hat's fine. It's a great place to work. I have thoroughly enjoyed my three years here, both on the Ansible team and the OpenShift team, but I've decided to take a different path. And I've done that a few times in my career, I've worked out and sometimes it hasn't, but you know, it's been a good run here, right? Like I felt like I've built up this thing and maybe it's time to try something else. So just wanted to let folks know that, you know, you won't be seeing me around that much anymore. Well, still be in the community though. You're going to be in the community, Chris. You know, I want to say from the red hat team, a huge thank you. You know, you were loved and respected by the team. You definitely live the red hat culture. I know you and I have talked and you just spoke about, you know, how, you know, really enjoyed your time at red hat and heck, maybe you'll come back someday. We've seen some boomerangs. I'm not throwing away any of my shirts or anything. Yeah. So are you ready to tell the audience where you're going? No, not yet. I want to take a little break and then. The one thing to tease out is we don't expect that Chris Short will be changing channels and that you will be seeing him on daily, weekly, monthly shows after it, but you are heavily active in the cloud data in Kubernetes community. You're going to be a representative red hat still at QCon in LA and we can expect to see you at future shows of that type in that community. I should say. I'm not leaving the cloud native sphere, right? If that makes sense, right? I'll still be, Kubernetes is going to be a part of my daily job. So I will be amongst the clouds with you all natively. Well, yeah, Chris, it's a chapter. As I said, you know, you've been the voice in the face of OpenShift TV on a bunch. I've seen in many all hands calls and on some of the corporate channels, you know, videos, photos, you know, you show up everywhere. So, you know, you've got a long catalog and, you know, I know a little bit about, you know, making that shift and having, you know, a lot of content behind that will live on and continue. So hopefully we will get you back on, you know, one of the shows personally. It looks like at least for the timing we'll pick up that in the cloud show. We are planning, you know, Christian and Andrew, you mentioned their shows, we'll keep going. They're doing that. We're having some looks internal as to, you know, some of the hosting and some of the details on that. But yeah, let's, you know, Chris would love, you know, some of your, you know, what advice would you give to people if they're starting? What is, when you look back and say, you know, are there anything where like, boy, you know, I wish I had gone to the cloud months earlier. I wish I had done this. I wish I had stopped or started, you know, something and done it a little bit differently. So I tell this, like this is an inside joke on the team, right? Like for any product, there's like an 80-20 rule, right? Like there's 80% of the population your product probably works for and 20% where, nah, it just doesn't, right? Like whatever your product might be, you know, Kubernetes works for a certain percentage of people out there and other people are running something else. So I am a 20% use case user of Google Calendar, I feel like, not picking on Google in general because I use like a third party app to actually manage multiple calendars, but like there's no great calendaring tool and none of it integrates with anything else. So if it were me and I were starting over, I would have like told my brother-in-law or something, go start this startup, build this product and let's get rich because like if we could automate everything we could do it all through our calendar because we put all the stuff in there and it would be great if it just filtered out to all the networks and like, right? Like I would have built something like that if I had the time early on maybe, you know, like... I've been a heavy G Suite user for over a decade, Chris. And when people move over from the Microsoft Suite to the Google Suite, that's the one thing that you give them a warning is you kind of expected all the integrations and everything to work with Outlook and calendaring and everything. The Google stuff just doesn't hit the mark. And oh my gosh, if you have multiple accounts and have to deal with that, you know, nightmare. I mean, you know, I still keep, you know, two different browsers, one for a personal and one for work and keep those up on two different windows. And it's better if you can do them on two different devices because, you know, if they, whichever one you log in first with just tries to always own that. So, you know, just log out, refresh, try to go back in. I've got like four different browser profiles that I use between like all the live streaming and, you know, community stuff and everything else. So like, it's, you know, just buckets of organizations is what it is. I guess, you know, don't wanna jump on a nerve here, but, you know, when you started OpenShift TV, I believe the expectation was, hey, this would be a fun project for three months. And here we are 16 months later and it grew into it. So like all of us, it was, when does the temporary become the new norm? And, you know, live streaming is part of the fabric. It's not going away when you leave inside of Red Hat. So, you know, anything along those lines that, you know, hey, if I had known going into this, would you have limited the number of shows, change things? Yeah, I definitely would have like put a cap on the number of shows. I don't know what that cap like, I probably would have just thrown out the number 15 because it's my favorite number anyway. But, you know, I would have said like there's an upper limit here, right? Like there's only so much content. What are you talking about? It's 42, Chris. That's the upper limit. Okay, 42 hours a week. No, it's just 42 is the answer. That would be a lot of logistical work, right? Like it's kind of funny how like it's, like in the early times, we never invite people on the show to talk about anything they don't know about, right? Like it's not like I would invite Stu on to talk about the guts of machine API, right? Like no offense to, you probably don't know. So, yeah, so it's one of those things where it's like, you know, just join us, have a conversation with us. If you need to frame it with a few slides, go ahead, you know, use your three slides to frame the conversation and then let's dive into some things. And I think those shows are like the most engaging shows, but then, right? Like you do have to have that balance. And I didn't think about that much in the beginning either, right? Like you have to have a balance to address all your audiences, right? Like, you know. And it's interesting, even internally, I don't think people understand the difference between there's a channel and there's all of these shows with their own distinct audiences and focus and things like that. It's just, you know, OpenShift TV is not a monolith. There's lots of things that go on and hit those pieces. But, you know, out of, you know, you've done, I don't know if you know how many episodes you've done of all of these variables. Oh, it's over 800 now. That's a ton. That is there. And, you know, you weren't necessarily a host on all of those. But, you know, there was, you know, way more, I mean, I remember Corey Quinn interviewed me once and talked about like, I did like, you know, 470 interviews in 2019. And it was like, that's more than one a day. I'm like, yeah, well, when you were going to conferences, something like KubeCon, you do three days and you go to Amazon, it might be three or four days and you could do 10 or 12 interviews in a day. Those pile up really fast. And then, you know, you collapse over the summer and you take some time off here and there. But, is there, and I always found this question tough. So I understand, but is there an episode that stands out and are there any guests that you were like super thrilled that you got on or did just brought out anything else? So I'll give you a little bit of leeway on those and a couple of categories and it's okay if it's more than one. So like, we did the mini series, call for code for racial justice. That was like, when they reached out to me, I was like, yes, because that's something I'm very passionate about. Explain that one. So there's call for code. It's a nonprofit nationwide nonprofit here in the US and I think globally now, and they work on projects kind of like for civic good basically. But then there was a upswell of racially focused violence in the US not too long ago and projects were created to kind of help with, you know, analyzing our sentences fair are people being, you know, judge the same way in a fair and balanced manner. And it turns out that's not the case. And so there was seven or eight, I forget how many episodes, eight part, any series. So eight projects that were all done to help, you know, kind of balance the playing field and not have it, you know, with the thumb on one edge of it to make it, you know, what it is today. And they're making real change and real progress. And I think it was awesome to work with the IBM team on that. And, you know, they have a core team that are working to get, you know, more people involved in their community. And, you know, I highly encourage you to go check out the playlist on OpenShift YouTube. Yeah, and I believe you just have the final episode of that, correct? Yeah, we just did the final episode on Tuesday. So yeah, well, yesterday, yeah, what day of the week is it? What year is it? Days don't matter. It's almost 2022. March 2020 is almost done and we'll flip the calendar to 2022 here before we know it. Yikes. So that's awesome. I mean, Chris, you know, one of the things, you know, you've been active in the open source community. The, you know, tech for good stories are always great to hear. I've, and I too have, you know, called out interviews I've done and discussions I've had. Some of them, you know, Red Hat customers would, you know, how they, you know, track and do things around COVID and the like. How about from a guest standpoint? I mean, you've done some, you know, high-profile executives. You've had, you know, so some brilliant people down in the weeds, you know, give us a couple that kind of stand out of you as either excited you or interest you or you learned something. So like the interview with Stephanie Sherriss I did last year was like the most intimidating interview of my life. Like for folks who don't know, like Stephanie has like, she speaks multiple languages, has multiple degrees, like doctorates, I think. Yeah, she's a PhD. She's, she's brilliant. She's an amazingly smart person. And, you know, here I am. Oh, they're like, if you look, there's my community college degree diploma over there, right? Like it's, so like, you know, I made sure that like I worked with her executive assistant to flesh out the questions and, you know, bounced it off of Chris Morgan at the time. And it was like, hey, you know, like, I actually told him like, you know, I am a little, I'm feeling a little intimidated by this. And he actually called me that morning because, you know, it's in the clouds is usually on pretty early. So it's called me that morning. And he's like, hey, you know, just gave me a pep talk and I was, okay, cool. But that was a really fun interview. That was last year. Go check that out. Stephanie is awesome. So I had the opportunity. It was funny, you know, she was an IBMer for, you know, I think like a number of years or something like that. And it'd been over at Red Hat like less than a year before the acquisition. And I remember talking to her, you know, after and it was like, did you know, was it your part of it? And it was like, no, Stu, I didn't know. But yeah, she's, she's brilliant. And, you know, does she throw you with the Boston accent though, Chris, a little bit? It does. Yeah, a little bit. Yeah, but, you know, I live up in the area. And yeah, she's phenomenal executive and just so good and a fun conversation. It's one she does and does a lovely job making sure her backdrop looks there and super well branded. From a, in the weeds perspective, Stu, I gotta hand it to Scott McCarty. But I want to give an honorable mention to Rob Zomsky because he actually brought his CNC machine via video onto the channel. So that was pretty cool. But anytime Scott McCarty came on, he would just be like, he would dive so deep into the topic. It was like, see, it's all just file system stuff. It's all just files on disk, like containers or nothing but files on disk, blah, blah, blah, blah, blah, run CC run. It doesn't matter what runtime you're using. It's all just files on disk. And it's like, oh, okay, I understand that now. So like you would, you'd walk away from those conversations with like a depth of knowledge that you just did not have before. Right. And Scott and Rob both, I had the chance of interviewing both of them on the cube too. And it is rare when you have someone that really understands the depth of that but can explain it to a point where the lay person who, you know, I don't know my file systems inside now and, you know, don't think about that other than, you know, when I plugged in a backup drive, you know, I have to choose. Right, yeah. But, you know, he explains it and you understand it. So yeah, those are good ones there. Yeah, how about, you know, how about your set? You said you had the, you know, the mic, you know, any things, you know, how did you build out the backdrop and, you know, some of the pieces? This all started in my unfinished basement, right? So like my actual backdrop was a concrete wall. It didn't look that great. So back then I just hung up a bunch of flags because A, they were like $4 for like the most expensive like college flag I could find. And like, it was like I had a Star Wars flag. I had like state flags for every state I lived in. I had a college flag for when my daughter was going to school and like that was cool and all, but there's actually like inspectors coming today because we're finishing the basement. That's why I'm now in our former guest room. A pandemic means you don't have many guests over so it kind of works out. But, you know, there's a standing desk that's very wide, 72 inch wide desk where all the stuff can just sit on. So I've got a UPS, I've got a subwoofer, I've got a TV, Apple TV with a monitor over there. So I can actually watch the live stream like live as if you were watching it. But yeah, there's three monitors, including the laptop monitor stuff happened like the virtual machines over here. I got notes over here, all the comments and zoom is in front of me. There's two lights that are bouncing off the wall. You know, there's a very, it's a used Sony A6000 camera with the Sigma 30 millimeter lens is probably the nicest part of the setup, right? Like I actually spent money on the camera and the microphone, that's a very expensive microphone. You were nicely well branded. Yeah, so the funny thing about when I was in the basement was like, it was like, okay, turn around and it's like my back desk, which was like my personal work desk. And we basically just brought that up here because it has this nice fireplace and I could totally throw a red hat up full screen for when I'm doing live stream. So why not? And like the fireplace in the background thing was like a mental thing for me because if you recall polar vortexes, I'm in Michigan. We got nailed by some of those. It was like 42 degrees one day in my office. And like, I was like, okay, fine. I'm gonna not have all the stuff that I need for this one, you know, period of time. I'm gonna have to be in the basement to live stream though. So the fire came on and it just gave me that, you know, psychological feeling of, hey, maybe it's a little bit warmer in here, but I had a space heater down there and all this other stuff. That got upgraded that day. But yeah, it's a lot. And like I fully embraced the USBC mantra as a result because you kind of need that level of speed to make all this work, right? Like if I tried to do a demo on top of everything else I'm doing right now, my computer would start to slow down. Like you would notice it visibly. So yeah, you gotta have your ducks in a row kind of thing. If I was going to do like a demo, I would actually throw production on to like my iPad and use the remote desktop client available for iPadOS to log into that box and manage, you know, stream on, stream off that kind of deal. And having that flexibility is great, but it's a whole lot of gear sitting on the desk because it's not just a microphone, right? Like it's a microphone, it's a cloud lifter. It's a, you gotta have something that converts it from XLR to USB seed, you know, and it's just dot, dot, dot, dot, and you never want to lose the data that's on your disk because you might be in flight working on a video, you know, redo or in like constant backups. It is one of those things, Chris, that, you know, yes, I could grab this and I could go live on Twitch with just that, yes, no problem. But, you know, you keep adding pieces and it keeps adding complexity. And yeah, it's, you know, troubleshooting all of those things and making them all work. So, yes, you know, empathize and it's funny. It was like, I always think my experience for like building a stereo system from components, you know, back when I was like in high school is something that some of the new generation doesn't know. Right, like my freshman year in high school, I took an electronic class and I still use stuff from that today for this job, which is pretty cool, right? I think that was very forward thinking of myself. Yeah, but, you know, everything from the physical layer, like weight, like let me text connections to, you know, the, you know, my networking background has helped me with troubleshooting. It's like, let me understand the flows, let me understand where I can test things, you know, do I have three different places I can put my headphone jack to make sure that it sounds the right way? Because yeah, we've, you definitely have the things. It's like, okay, wait, my inputs all seem fine, but there's something wrong with the stream. Right, and early on, that's how we knew, right? Like we kept having these little bumps on the night kind of thing, right? We didn't know what happened. Zoom just flaked out on the box for some reason, right? Like who knows? But also like early on, like Zoom didn't necessarily work with Linux very well. And that's what I was using on that box. And so like having Zoom as a communication layer was fine, but there was some stuff that like annoyed me a little bit, right? We had to do some extra stuff for Linux, mainly use Xorg and not Wayland. And that, you know, has sorted itself out over the year and a half or so and isn't a problem anymore. But those like little nitpicky stuff like that, right? Like that happens with this, that happens with the box it's connected to, that happens with the computer, that happens with the camera, that happens with the HDMI thing to go from the camera into the computer. So yeah, you're taking all these basically analog things and digitizing them and shooting them out over the internet. It's not trivial when you really like get into live streaming if you want to do it right. But Chris, you know, if I hear, you know, from our conversations here, while it hasn't been perfect, you've enjoyed a bunch of those things and getting to know and play with it. You know, you've been hacking and doing that. So, you know, what's it meant to you to be, you know, OpenShift TV? Well, I mean, it's been a real honor, right? Because, you know, we didn't know how far this would go. We really didn't. And the fact that it became like my day job was, you know, a real tantamount to like its effectiveness. So it's been a real honor to bring my team's content, other people's content from throughout the company, throughout IBM, from other companies, you know, our partners, it's just been a real honor to just be able to deliver that and give a platform to voices that normally wouldn't have had one otherwise during the pandemic or would have had to have one in a virtual event, which, you know, you and I know is sometimes not as easy to pull off as a live event, which, you know, that is kind of the niceness of it being live. You just do it once and you're done. You don't have to perfect it. Some imperfection is totally expected. And like I said, we embrace the failure of all types. It is actually one of those, you know, not-so-secret secrets. If you talk about doing the live stream is, Chris, how much post-process editing do you do on all the OpenShift TV shows? None. Yes, and anyone that's done any video, I have some friends that are in, you know, TV and movie-type businesses. Oh my gosh, you know. It's all editing, yeah. Not only, you know, not only could you spend, you know, hours to try to, you know, record properly the five minutes that you want, but then the poor people that have to do the post-processing, usually it's at least 3X, the amount of time based on the length. If you're doing a podcast, you can, it's not nearly as much, but still that's a little bit of, you know, cutting things down and doing it. So if you can record and then just hit publish, that does save huge amounts of time. And that was something I actually learned while I was goofing around with video stuff back in the early 2000s. Was that like, yeah, if you could record it, it took 3X to edit it. And I did not want to be in that situation, right? Like I didn't want to become like a video editor, right? Like I didn't want to be that, you know, particular person that needs like the Mac Pro or whatever, you know, the ridiculous box. So that's why I insisted on live to an extent, right? Like we don't do replays. We don't do, you know, anything like that. It's live only kind of thing. And it works, people appreciate it. All right. Well, Chris, what give you the final word, you know, what's the audience, the community meant to you and will continue to mean to you going forward? I mean, like I said, I'm not going far. So, you know, I'll be around. The audience I think has been great. We've had everybody from, you know, a junior, you know, like college student, well, like a junior developer slash college student to, you know, like seasoned, you know, government workers that use OpenShift come on the channel and, you know, we've helped them solve problems and educate them on things. And that I think has been the most rewarding and fulfilling thing. And then just getting the voices of all the people out there, right? Like that means a lot to me to be given that responsibility and then to be able to actually pull it off, I think is like a real honorable thing. And I feel humbled by, you know, I look at the numbers every month and it's just like, wow, I did that? Me? Wow. You know, so it's been a very, very much a learning experience for me, a growing experience. And I will miss the people for sure the most. Well, as you said, Chris, you'll still be in the community. We still look forward to, you know, talking with you and keeping in touch. So, you know, while it might not be on this channel, for now, we will see where it goes. So thank you again. Great to be able to talk with you, you know, share those lessons learned with the audience because, yeah, that's a lot of it is sharing that and learning from it and building on it. So thank you, Chris, you know, we will, you and I will both be at KubeCon in person and then, you know, you will be sharing with us, you know, soon after that where you'll end up. I do recommend everyone, you know, do check them out. Chris is super easy, he's Chris Short on the Twitters. He also has a newsletter on Kubernetes that I recommend that you check out. And thank you, Chris. Thank you, Stu. And check out our schedule out tomorrow, folks, if you haven't yet, I got to do my thing for just a second, Stu. Got a busy day tomorrow live streaming, so please check out the calendar, hit what you want to hit. And yeah, we'll see you then. Stay safe out there, folks.