text
stringlengths
7
369
[228.72 --> 233.44] this 100K subs if it ever comes. But it came pretty quick. So I had to get on the ball.
[233.44 --> 238.84] Well, that's a nice problem to have. You know, I'm not sure if I've ever told this story on air,
[239.10 --> 243.98] but I did a computer science master's. I was originally a trained musician and then did a
[243.98 --> 248.70] few years at the Apple store and went and did a comp sci master's. One of the friends I made on
[248.70 --> 254.84] that course went and did a PhD straight away afterwards. And his PhD was into defining DevOps.
[255.28 --> 259.84] I don't know how he managed to swing that with his supervisor, but he did. And he got paid to do it.
[259.84 --> 267.58] And I think this dude spent four years defining DevOps in his PhD thesis. Do you know what the
[267.58 --> 269.44] outcome of the four years was? What's that?
[270.14 --> 272.78] There isn't a definition. It's too nebulous.
[273.88 --> 275.38] I like it. I like it.
[275.96 --> 279.94] If only someone would pay me for four years to do absolutely nothing. I mean, sorry,
[280.08 --> 286.46] sorry, Steve, if you're listening, but it's an interesting thing that you raise seriously,
[286.46 --> 293.70] that DevOps in general means whatever you want it to mean. It really, truly it does. You know,
[293.74 --> 297.84] to some people, it means that you're a cloud expert. To other people, it means that you can
[297.84 --> 302.00] write Terraform code. To other people, it means that you know all about networking, right? It just
[302.00 --> 305.94] depends on the problem that you happen to need to solve that's in front of you this week. It's
[305.94 --> 311.62] almost like just like a buzzword, like a magic word that management don't have to hire specific
[311.62 --> 316.58] people to do specific tasks. We want a generalist that knows a little bit about everything. And I
[316.58 --> 319.06] think that's typically where DevOps comes in.
[319.40 --> 324.56] Yeah, that's a good point. And it's, you know, it can be lumped as anything from getting code
[324.56 --> 330.04] into production and whatever that means. It could be, you know, that's a huge chasm to cross.
[330.52 --> 335.60] And it could be many different technologies. And yeah, it's a, you know, a jack of all trades type of
[335.60 --> 337.92] role, but very needed.
[337.92 --> 341.88] Oh, you've, you've used a database, have you? Okay. So that means you're a DBA now.
[342.04 --> 343.64] That's right. That's right.
[344.16 --> 347.88] So what kind of stuff have you got planned? I've seen you've done, you know, your launch video,
[347.98 --> 353.66] your 100k subs video was pretty cool. You had 12 of the biggest home labbing YouTubers as a
[353.66 --> 358.10] massive collaboration. You know, there's Wendell, friend of the show on there, a bunch of other
[358.10 --> 362.52] people, Jeff from Craft Computing. What else do you have planned for the 100 days?
[363.06 --> 367.58] I'm on day four today, you know, but for me, it was just to kind of get people
[367.58 --> 372.96] motivated about, you know, getting into home lab, whether they are already doing it or rekindling
[372.96 --> 378.66] that, you know, that passion they have for it. It was just kind of getting everybody on the same
[378.66 --> 384.22] page, like created a hashtag for it. And what I'm realizing through this hashtag is, is, is that one,
[384.28 --> 388.36] people are using it. My, my Twitter's never been so active. I don't have a lot of followers. So I'm
[388.36 --> 392.18] like, whoa, this is how almost famous people feel.
[392.56 --> 393.26] What is the hashtag?
[393.26 --> 398.32] 100 days of home lab. It's small, but people are using it. And what I'm discovering through this is,
[398.40 --> 403.62] you know, these, these updates that people are giving are very similar to my daily standup to
[403.62 --> 408.02] my scrum, you know, as a software developer, you, you know, if you do scrum, you stand up and say,
[408.18 --> 412.84] you know, what did I do yesterday? What did I do today? And, you know, do I have any roadblocks? And
[412.84 --> 419.02] it's, it's very awesome seeing everyone just kind of chiming in with what they're working on today,
[419.02 --> 424.32] what challenges they're facing and then seeing other people join in and talk about how you could
[424.32 --> 429.48] solve a particular problem or, Hey, how did that work out for you? It's just been very awesome.
[429.48 --> 435.36] So I, I don't know what the long-term plan is. If I get to day 100 and someone is on day one,
[435.74 --> 441.30] feel like that's a success. That means that, you know, this has gone longer than my hundred days
[441.30 --> 445.74] and someone else's journey is starting now. And so, you know, there's a lot of people said,
[445.80 --> 448.86] do I start with you? Don't I start with you? Start when you want. Like,
[449.02 --> 453.08] you know, just because my train's leaving today doesn't mean your train's leaving today.
[453.22 --> 454.58] Your train could be leaving next week.
[454.76 --> 455.16] Choo-choo.
[455.54 --> 461.14] That's right. That's right. And so, you know, I, I, if I get to day 100 and I see a day one,
[461.26 --> 465.84] that means this whole thing was a success because it's, it's bigger than, than my hundred days.
[466.44 --> 471.14] You must have some kind of an overarching goal because, you know, the time I think about when I
[471.14 --> 476.82] was really probably the most active in terms of development over the last few years was just before I
[476.82 --> 480.82] immigrated. Actually, I was, I was pretty stressed about the move coming up, you know,
[480.88 --> 486.38] England to America and I just needed something to distract me. So I used, I spent hours writing
[486.38 --> 492.16] Ansible playbooks to completely Ansible eyes the deployment of my server. And at the time it was
[492.16 --> 497.50] mostly Ansible eyes, but I'd done it three or four years prior. So a lot of the stuff I'd learned,
[497.56 --> 501.92] you know, as a consultant for a while, I'd learned some tips and tricks and I'd learned some new stuff.
[501.92 --> 507.62] And I thought, right, I want to do it properly. And my goal was to do as much as I could through
[507.62 --> 512.14] one or two commands to deploy the whole thing. Is there something like that at play for you here?
[512.64 --> 517.22] Possibly. I mean, I, I've done some Ansible automation. I think just a couple of months ago,
[517.30 --> 522.36] you know, I, I created an Ansible playbook to create a high availability Kubernetes cluster along
[522.36 --> 526.62] with load balancers all in one, because I saw that as a pain point for a lot of the people that were
[526.62 --> 533.76] using Kubernetes. So yes, it is. And so I, I found a whole bunch of forks that were left abandoned and
[533.76 --> 538.70] I made them work. And so I, you know, automated a lot of that, but with this, you know, I'm,
[538.70 --> 544.06] I'm not sure. I mean, for me, it was really supposed to be kind of a, you know, a celebration
[544.06 --> 549.48] video and at the same time get people involved. But long-term, I, I honestly, I didn't think it was
[549.48 --> 553.66] going to be, you know, turn into something as, as big as it is now.
[553.66 --> 557.52] Well, you've got to stop coming on people's random podcasts and talking about it.
[557.52 --> 558.90] Yeah. Stop promoting it.
[559.66 --> 564.66] That's true. That's true. I mean, it, it, it's a great initiative. I mean, if, if, if there was
[564.66 --> 570.18] ever, you know, some learning company that wanted to do something and, and help people and infrastructure
[570.18 --> 576.10] do something, I'd be all for it. But, uh, honestly, no, no long-term plans. It was an idea that turned
[576.10 --> 582.26] into a video. I got a lot of awesome people on YouTube to help me out. And that's where it stopped.
[582.26 --> 585.64] For me, it's, it's, you know, it's, it's obviously still going.
[586.00 --> 591.44] Sounds to me like you had this bright idea and you didn't think what happens when I release this
[591.44 --> 594.14] into the world? Like, do I actually have to follow through on this thing?
[594.18 --> 594.62] That's true.
[594.74 --> 598.88] I've been, I've been, in fact, that's this show, you know, for me, I've, I'm living it, baby.
[599.10 --> 604.24] That's right. I bet. I bet. Yeah. Like I didn't think how does this scale? What,
[604.40 --> 606.10] you know, what's my long-term goal?
[606.34 --> 610.20] Right. Which is ironic for someone who's as deep into Kubernetes as you are.
[610.20 --> 615.36] Yeah. I mean, usually my, you know, my videos do okay over time, but this one did really good,
[615.44 --> 620.14] really fast. And that's, that's not, you know, my typical, you know, release cycle for videos.
[620.34 --> 625.98] I released a lot of videos on tutorials and how to set things up on deeper topics. So I get lots
[625.98 --> 631.60] of views over time. Um, and you know, usually I'll get some tweets and, Hey, how did you do this? Or,
[631.94 --> 636.16] you know, or someone on discord will ask, how do I fix this? And, you know, basically like
[636.16 --> 643.62] async tech support. But with this one, it was like, no one needs my help. They're all doing it
[643.62 --> 648.68] themselves. And, but at the same time, they're all joining in. So it's, it's, it's really unique
[648.68 --> 653.02] from what I've done in the past. So at this point, I suppose it's worth kind of defining
[653.02 --> 659.56] what a home lab is, and maybe you could tell the folks how you got into home labbing to start with
[659.56 --> 664.88] and, you know, that kind of thing. Yeah, that's a, that's a huge topic. I even have a hard time
[664.88 --> 670.32] describing home lab to people at work or anything else, because I think that, uh, you know, that the,
[670.32 --> 676.08] the term has kind of evolved into a lot of things. The way I look at it is it's, uh, you know, when
[676.08 --> 681.38] you think of, you know, you went to school, you had a computer lab there where maybe that computer lab,
[681.46 --> 686.26] you were able to set up certain environments, um, and destroy those environments or build them up or do
[686.26 --> 690.80] whatever you wanted to tinker in those environments. And that's kind of the idea I think behind home
[690.80 --> 695.54] lab is that you can set up an environment, a safe place where you can set up an environment to,
[695.54 --> 702.88] to tinker with tools or to explore new technologies or automate some, some infrastructure or geek out on