Lessons from 15,031 hours of coding live on Twitch with Chris Griffing [Podcast #214]

💬 Chat with this Video
Ask anything about this video…
Welcome back to the freecodecamp podcast. I'm Quincy Larson, teacher and founder of freecodecamp.org. Today, I'm interviewing a developer who has live-streamed himself programming for more than 15,000 hours on Twitch and the many lessons he's learned along the way. Before we get to that, some quick community news. Freecodecamp just published a comprehensive course that will walk you through using the popular AI assisted development tool Claude Code. You'll learn about code harnesses, agentic loops, sandboxing, and other key concepts straight from a CTO. By the end of the course, you'll be able to spin up an entire fleet of agents to help you fix bugs and build out new features. This is a free 12-hour course on the freecodecamp YouTube channel. Finish listening to this podcast first, but certainly go over and check out that course as well. We also published a comprehensive course on the Hugging Face tool ecosystem. No, that is not something from aliens. It is a popular platform for sharing models, and you'll learn how to connect those models, data sets, and deployment tools into a single unified build pipeline in this free 7-hour YouTube course. We also published a handbook that's free, as with everything we do, where you can learn how to secure your Kubernetes clusters. This is an in-depth tutorial that starts by exploring real-world security breaches at big tech companies like Tesla, Shopify, Capital One. Then it walks you through how to prevent each of these attacks by hardening your setup. It's a great series of case studies, and it takes about an hour to read this if you're a native English speaker. Next, if you're not a native English speaker, but you're a Spanish speaker or you have Spanish-speaking friends, tell them that freecodecamp just published a new course on SQL and relational databases. It covers tables, foreign keys, queries, data manipulation, and more, all in the Spanish language. And yes, the instructor, Sergey, actually looked like this. He's an absolute badass. If you're looking at the video version of this podcast, the guy looks awesome, and he's a great instructor. Today's song of the week is 1988 song by Genesis side project Mike and the Mechanics Nobody's Perfect. If you like synths, if you like guitar solos, you'll love this song. Paul Young has an incredible voice and I love the edifying message behind the song. The video is about as 80s as it gets and if you're watching the video version of this podcast, please pause to admire the incredible record cover art. Uh both uh two of the band members their dads had died during the recording of the album. And so if you look at the album cover, it's essentially one man who's reached kind of the edge, the shore, and he's no longer able to progress and then kind of inside him is another man who is continuing to walk forward into the darkness. Really profound, one of my favorite album covers. freeCodeCamp is a 501c3 charity. We're tax exempt and you can make tax-deductible donations to our charity and help us keep moving, keep creating these free open-source learning resources for everyone. Support our mission at donate.freecodecamp.org and you can also rep the freeCodeCamp community with pride. Get one of these freeCodeCamp shirts for 20 bucks, free shipping anywhere in the US, or you can print your own. Just use our label, uh use our logo. Uh it's free for non-commercial use. Go to our assets library on GitHub and you can get that. That brings me to today's interview. We're talking with Chris Griffin, a software engineer and prolific streamer of live coding on Twitch. He spent 10 years as a snowboard bum, essentially doing odd jobs around ski resorts to facilitate him spending as much time on the mountain as possible. We're going to talk a little bit about snowboarding, which is one of my hobbies, uh but certainly one of his core interests. At age 28, he taught himself PHP programming and started building websites for friends. And in 2018, he started streaming himself on Twitch, uh which blew up during the pandemic and has led to lots of opportunities as a dev and a developer advocate. We talk about how he learned programming at age 28 and built projects, uh how he uh learned Go and how that made him a better Rust developer and why he encourages you to also become a polyglot programmer. How Chris uses LLM tools, but still builds most of his code bases manually, and his tips for building projects in public for anyone interested in also streaming coding. If you want to get started streaming coding, I did it for a while, it's a lot of fun. It is scary, but uh, we're going to hear more about that right now. Chris Griffing, welcome to the freeCodeCamp podcast. Thanks for having me. I'm stoked to be here. Yeah, man, I've really enjoyed watching your stream, and I think a lot of people are going to enjoy watching it if they have time. We'll get into that in a minute, but I want to start with a spicy take that uh, I heard you say. You said, quote, "Server-side rendering is an edge case, but not many applications actually need it." Let's talk about what is server-side rendering and why is it an edge case in your opinion as opposed to like a a core selling feature of a platform? So, I mean, server-side rendering is what like the main bread and butter for something like Next.js is. And even like old monoliths like Ruby on Rails, etc., they're rendering templates on the server dynamically based upon the data and all that stuff and shipping it to the user. I think that's actually an edge case because in general, you're going to have things like a marketing site or a doc site that can just be static assets. I actually I cry internally whenever I see someone building a doc site with Next.js. It makes no sense to me. Um, and then beyond that, right? You're going to have applications that are login gated. Those are going to be client-side rendered, right? Like, you don't need server-side rendering for the like the majority of applications in which you're logging in. Server-side rendering has a very specific niche in which you have way too many pages that statically rendering them is unfeasible and the data changes too often. And, you know, you still need like SEO and things to like be able to crawl that data. So, we're talking like the edge case is e-commerce and classified ads and like, you know, car listings and things like that. But, that is not the majority of the stuff that we're building day in and day out. Okay, so like if somebody is not building one of those specific things where SEO is like a principal concern or where uh it's just like a massive amount of data, you would say don't jump straight to server-side rendering. And I guess what is the reason? Is it going to be faster for the end user or it's not going to necessarily be faster the end user, but it adds complexity, it adds cost of hosting? Yeah, I mean, so I've at least seen this like just in the past couple days where I'm navigating a site and then for some reason I click a link to go to their docs and I just see like the the Next.js error page. And why should you ever see that when you're reading a docs page? It doesn't make any sense to me. Right? Like it should just be some statically rendered HTML, CSS, and a little bit of JavaScript sprinkled in. So essentially you're saying it's just like overcomplicating things. Exactly. >> They're overthinking it. They're they're using the proverbial bazooka to kill the mosquito when they do something like >> it does make sense for some startups where yes, they don't want to think about their stack. Everything's Next.js so they don't have to make that decision for each like individual part of the project. I I get it maybe, but it's still like it that seems just lazy to me. Yeah. Well, I can I can certainly understand like a lot of people are probably just, you know, having LLMs generate a lot of their original project boilerplate. Um and that's something I want to talk with you about LLM code generation. And of course when I use it like it'll be like, "Okay, we're going to use this, this, and this." It makes a lot of those architectural decisions for me unless I specify. And a lot of times it is defaulting to like just using Next.js or some proverbial bazooka um to build the proverbial very simple like docs site. Right. Right. Uh documentation for like a a new programming tool for example. Uh can you talk about like you you spend a lot of time programming. I think you spend like 30 hours a week just programming on Twitch. So that's more than most people I know. In fact, a lot of people I was just hearing Jared Santo of The Changelog, whom I've interviewed many times on this podcast, say that it's he doesn't even try to program more than 4 hours a day because his brain just is mush by the end of 4 hours. But you're spending 6 hours 5 days a week 30 hours a week streaming. So you >> just on stream. I have work stuff that I got to do, too. Yeah, yeah. So you work a full-time job in addition to that. But you've been quick to point out that you don't consider streaming work cuz it doesn't feel like work. It's fun. Exactly. >> But like let's talk about LLM code generation and your perception of it, how it's being adopted by developers, and where you find it useful, where you find it unnecessary. Um yeah. So I'm I'm not at the forefront of like this vibe coding gas town, like all these agents and orchestration and all that stuff. I'm really just not doing that much. But it doesn't mean I'm totally anti-vibe coding as well. Um I've totally used open code, Claude code, bunch of those things just for work cuz I have to as as a devrel, right? Like for our dev tooling. But even then like I really like the idea of vibe coding for something that is classified as a program rather than like a product. And there's a Dylan Beattie like blog post the guy that made Rockstar Lang and all that. He's amazing. He has a blog post about the difference between programs and products. And vibe coding is great at making a program, but that doesn't mean that oh, does it work on Windows? Does it work on whatever? Like your program is meant for you to just do something quicker and easier. And vibe coding is perfect for that stuff. Um but Yeah, go ahead. I was just going to say like a one way I've heard that described is like software with an audience of one. It's usually just something you're doing or something that is just helping a few of your teammates behind the scenes like back office type coding. Those kinds of workflows that are being quickly automated where if it's not perfect, it's not the end of the world because no paying client sees like a 404 page, right? Exactly. Yeah, I think there's the idea I don't know if you're familiar with XKCD or if the audience isn't, but XKCD makes these awesome comics. They've existed for 10, 20 years, something like that. They have this one where it's like, is it worth automating a task? And it's this like graph. And it says, well, if you're doing it five times a day over the course of three years, how much time would you save? And that helps you think about like how much time you would you could reasonably spend on this task before like the automation is worth more than the value you get from it, right? And I think LLMs have changed that graph a little bit in that you could vibe code out some of these things real quick and easy and save yourself a lot more time and the investment is no longer like as big as it was before. But any code we write is something we have to maintain eventually. And I think that does really like There's another XKCD that shows like, oh, I'm going to build this thing. And it shows this graph of like what you expect the graph is going to do about the amount of time invested. And then the maintenance part goes way up. Right? So, I don't know. It's interesting. Yeah, I mean, in theory any code base probably can you're probably going to sink like 10 times depending on how long the code is used. There there's heavy maintenance cost and I'd encourage people to check out the Maintainability podcast by my friend Robbie Russell, whom I've also interviewed several times on the uh freeCodeCamp podcast. And he just talks about maintainability. Yeah. >> Right? And uh and I that's so much important and I think a lot of people that are not experienced devs, they're coming to the field think like that the writing the initial code base is the hard part or adding features is the hard part, but I think the real hard part from what like the really experienced devs I talked to is making sure that things continue to work over a long period of time as new uh people are entering the code base and having to like understand it uh as like new um edge cases emerge. Uh for example, for a long time responsive web design wasn't a thing and you were just cool with like, okay, this is going to be viewed on a monitor on a desktop and I can do like, you know, 680 by 420 or whatever I can't remember the exact resolution, but 600 by 400, right? Like like there were set resolutions you just assume that most people would be viewing it, and now all of a sudden, you've got mobile, uh you've got all that sorts of accessibility considerations that are making these websites available to tons of people who historically would not necessarily have been able to use your website or or your app uh because now they can you've like made it accessible to for screen readers and stuff like that, right? It's It's a net positive, but it is more work than just the initial like uh MVP minimum viable product that I think a lot of people use like an LLM code gen tool to to vibe code, some tool that they're going to use for themselves. Uh wouldn't it be great if I had like some uh way to just quickly take, you know, photos from this service and put them on this service, right? Sure. And things like that, right? So, that's kind of like the the program you're talking about. Like a program takes the the but a product is something that paying customers or uh you know, at least you're serving ads or something like that that that your end users are going to experience. Yeah. Yeah, I think it's not even just the like it coming back to the maintainability part. It's not even just that it's about program versus product anymore. It's about your ability to understand the code base. And there's that anthropic article that just released within the past week uh where they're talking about like they did this study, and it's kind of counter to what like their entire marketing rhetoric has been in that devs that are relying too heavy on the LLMs are actually far worse at like the later stage of debugging. Right? And by doing that, sure, you're getting a lot of value up front, but you're just like really shifting where you're going to spend your time. You're not actually saving that time. That's at least my opinion of it. And >> Yeah. Yeah. Um to me, I like understanding my code base. When someone points out a bug, uh you know, cuz I'm building like my own startup stuff on stream, etc., and I you know, people can use it, they can log into it, they report bugs. I like them being able to tell me, "Oh, they hit that bug." And just instantly knowing like, "Oh, all right." And then knowing where to go and at least like look at look at it and fix it. I like this mental map. >> Yeah, like what you're doing is building in public, you're learning in public, you're using your your positioning yourself as a vulnerable person who uh you know, can be criticized. Your code is being scrutinized in real time as you write it, and then people are using it and they're reporting bugs. Uh I guess one question I have for you is where did you get the audacity to do that? Like who are you to put your code on the internet and to to make all these mistakes in front of other people? Like have you no shame, sir? Like I think a lot of people would be terrified of that prospect of doing what you're doing. So, I mean, I am okay falling in front of people because I used to be a snowboard bum. Like I used to snowboard 150 days a year, and I've ridden in competitions, and I've totally fallen flat on my face in front of people. So, like, yeah, messing up some code in front of people is really simple compared to that. Yeah, and this is a great point for us to go ahead and delve into your very interesting developer journey. Uh of course, uh you were a snowboarder who sponsored, and uh that doesn't mean lots of money, but that does mean lots of like free gear and stuff, right? Um and you you spent like I think we did the math and you spent more than 2,000 days on the face of a mountain snowboarding. >> Yeah. Yeah, something like that. So, I don't know, from 2002 to 2012, I was riding it like around 150 days a year. One year I guarantee I got over 200, and I had been snowboarding for like four or five years before that. So, yeah, 2,000 days is probably about right. Um and yeah, it's just my favorite thing to do. It's so fun. Oh, it's the best. It's so cool that you have something that is your favorite thing to do cuz I think a lot of people are spending a lot of time on like social media or they're spending a lot of time just watching, you know, reruns of The Office and stuff like that. And like they don't have that one thing that really energizes them. Like I imagine when you get time you're going to want to go hit the slopes. Is that accurate? Like like do you is that one of the things you really look forward to as you're doing all this work, you're getting all this stuff done and you have that goal like okay, I'm going to go back out on the mountain, you know, this weekend or the spring break or something. That would be the dream. Like these days I tend to just ride the powder days cuz I'm I'm 41 now like I'm I'm much more fragile than I was in my 20s. So I definitely don't ride the park like I used to. I kind of like pick and choose like the good days to get up there and I try and avoid weekends and other people like the plague because snowboarding is better when there's no one around. Yeah, yeah, and I've snowboarded I don't know maybe like 10 different occasions I've gone to like some different like resorts and stuff like in San Francisco. You get on this bus and go to like Mammoth or I can't remember where I went, but you just get on a bus at like 3:00 a.m. They drive you to the mountain and then you get your lift ticket and a lot of times it's just included in the package. You get to do the slopes for one day then you get on the bus and you like sleep on the way back or like we watched Spaceballs on the way back. I love that movie. >> Classic. And yeah, it was just like the chillest time. But but like that was like the perfect encapsulation for me. But maybe like you can put me in the context of somebody who's snowboarding that much. And I promise we're going to get back to software development but it's not every day you have somebody who you know, was a sponsored snowboarder on your podcast and you can like glean information about them. So maybe you can kind of talk about like how you got into it and and maybe mix in some childhood and everything like that there. >> Sure. Yeah, so I started snowboarding around the age of I don't know like 13 or something like that. Did it through high school and I was not always like the best student in high school. So I really just didn't have any like university prospects or anything. You know, like I was good at the tests and stuff. I just hated homework. So I had terrible grades. So at the age of 18 it was okay, well friends are going off to college, friends are doing all these things. I just want to snowboard and I found out that you can snowboard at Mount Hood during the summer. They have just slush and parks and it's like amazing. So, I went down there for my first summer, worked as a pantry chef at at the start at least because they needed someone cuz someone was going on vacation. So, I got to make the salads and the amuse and it was like a a fine dining restaurant in the Cascade dining room and it was just a blast just getting into it and just going out on an adventure at 18 and then I just kept doing that, you know, Stevens Pass during the winter and Mount Hood during the summer for 10 years after. 10 years of basically like snowboarding the same few slopes. I mean like maybe a few dozen different particular slopes that you went down? I mean yes, it's the two same resorts. Like Mount Hood during the summer, there's only the Palmer snowfield basically. So, that that could be boring but terrain park, you can make that as fun as you want. You can make it as different as you want. You can learn a new trick every day if you want. Uh but Stevens Pass it's a fairly large resort. I do have like some of my favorite runs and everything but the thing about snow is that it changes the terrain as like it fills in, as stuff gets like stacked on, as trees fall down. Like you're never riding the same exact run ever, right? Because just everything's changing. So, it kind of gives you that like improvisation a little bit. Yeah, and it sounds very contemplative? Contemplatative? I'm not sure if I'm pronouncing that correctly. Like meditative. Uh you're up on the slopes and and you can think about the passage of time. Like would you ever be on the slope and be like like I remember five years ago when, you know, there was like the thickest of powder or something. Like think back to some particular occasion. I definitely have very specific days that stand out that are just these milestones of like, oh, I haven't had powder like that where it's like, you You we got some of the heavy like Washington snow, uh you know, over a couple days and then it got really cold and we got this like really dry stuff on top and that became like this Superman snow. You could send anything but you'd never get hurt. And >> Wow. I do have some days like >> like attempting some sort of like potentially dangerous trick? Uh like when we're talking like cliffs and like uh like the free riding aspect of it. >> Okay, so so you're talking about going down like a steep decline where like if you start tumbling, you're not necessarily going to get injured because you're it's like tumbling on, you know, not quite this affording but >> So I mean that's how powder is in general at least when you're like tumbling but I mean more like the Superman snow is like you can send anything and you're not going to dip down so far that you're going to like catch and like nose in and flip. Like it's like that dry bit on top you can like fluff into without worrying about like submarining under. Ah, submarine. Okay, so I don't know a lot of the terminology. >> I don't know. I'm like For sure. That's a cool term. That's a good visual. Okay, so I want to talk about the economics of doing this because you're working kind of like like I don't imagine that being a pantry chef even at a fine dining establishment at you know, a ski resort pays anywhere near what like being a developer or developer advocate pays. >> I think I made 825 that year per hour. >> 825 per hour. Okay. So yeah, that's like in the US minimum wage is I think 725. It may have gone up. I was making 515 an hour when I was working as you know, a high school dropout and then ultimately as a college student. I worked at like Taco Bell and grocery stores and stuff like that. So So you're making about what I made and probably just a couple years behind what I am because you're I think you're like four years younger than me. And basically you're just like doing this work to support your lifestyle of going out on the slopes. Like what proportion of your money was going where? I just like to dive in to understand like the economics of it because you've got to buy lift tickets. You probably have to have a place to stay. So I mean if you're working at a ski resort, you get a free pass. So, that's that's awesome. And Mount Hood during the summer and winter, so they have uh in Government Camp, like the closest town, they have employee housing. And most ski resorts have some kind of employee housing because the people working there are not making a lot of money. Okay. Wow, that's great. So, it's kind of like you're able to bank some of that. You weren't necessarily spending all the money you were bringing in? Uh no, you you spend most of it, for sure. Like, you go on trips, uh you know, there's still rent. And you're basically trying to work as little as possible. So >> spend as much time as you can on the slopes. >> Exactly. Yeah. And so, you spent like 10 years. Like, so just to put that in perspective, it's kind of like you're on the sidelines of your career for 10 years. Because this is not really a career like again, I hope that doesn't come across pejorative, but like even like the most elite snowboarder like it maybe if you're like an Olympic level snowboarder, maybe you have the equivalent of like what a teacher would make in the US or something like that, right? Yeah, I mean, so that is something, right? Like, pro snowboarders have a very limited lifetime, right? They're like they're they're like any pro athlete, right? So, they're going to hit like the age of 30 and the vast majority of snowboarders aren't going to be able to do it at the same level anymore. So, that like almost every snowboarder has to think about like where they're going to go after this. Very few people can be the announcer at X Games. There's only like three of them, right? >> Yeah. Yeah. And and I'm just sure there are like roles in like coaching and stuff like that, but the the total amount of money in the ecosystem I look at it as kind of like music, which you're also a musician, uh in that like uh the value is like where is the actual economic value of being a pro snowboarder like captured? It's in the form of people watching like the X Games or something like that, or watching the Olympics, and then going out and buying gear. And then so, then you've got like the the gear companies that are selling the boards or the clothes or something like that and they are basically getting the money and then they're using some of that money and putting it back into the ecosystem through sponsorships like you were getting and and but the total amount of money going into the industry is small just like the total amount of money going into the music industry is small to where it kind of like relegates it to a hobby for most people. Mhm. And most people of course going to ski or going on a ski trip or going on a snowboarding trip is like a loss-making proposition but they're doing it because it's fun, of course. >> Yeah. Most people get into skiing and snowboarding not to get sponsored, right? They just want to snowboard and ski. So, let's talk about like you start getting injured uh and it starts getting harder for you to, you know, do it at a peak level. You still enjoy doing it but you have to have more of like forgiving circumstances. You can't just go out on like ice and like snowboard around and like, you know, if you're if you're snowboarding 150 days a year, I imagine you're not it's not always ideal conditions and sometimes you're wiping out pretty hard. Yeah, so I mean during the majority of those years, uh I was working in the terrain park which meant I had to snowboard on some of the worst days. Uh just you like had to go through the park, make sure people aren't hurt and then well, if I'm passing the features, I got to test them, got to rake them and so yeah, I'd be riding on some very very not fun days sometimes but still having fun while doing it. Yeah, so what point did you realize, okay, like I do need to transition into something else and then what inspired you to choose software development? So, um yes, I have a shoulder that dislocates. I've broken both my collarbones. I've done AC separations on both shoulders, a couple concussions, right? Like the injuries add up, right? And you're always kind of paying a tax on them even after you've like healed. So, as those like start started adding up, I realized I needed to do something beyond snowboarding and my parents were in tech. They, you know, they worked on like the 1-800 system at like Bellcore and you know, just a bunch of telephony and crazy stuff, right? So, I come from like a kind of a programming family, which is funny because I'm the only one of my siblings that's like a a career programmer. My little brother's getting into it, which I'm really proud of, but like yeah, I'm really like the only one that kind of followed in my parents' footsteps a bit. But because they did it, it always seemed approachable, right? My dad doesn't have a degree, I think at all, maybe. He might have gone back to finish it, but it wasn't in programming, cuz this was during the '70s or something like that. Same thing with my mom, she has a degree in math. Like she's not a programmer like like, you know, by degree or anything like that. But that just made it even more approachable to me. So, eventually I went and got like you know, I started doing some like freelancing for some like snowboard friends. I built like Steven's Pass snowboard shop's like website, and even did some e-commerce for a little bit using Magento back in the day. And then yeah, that seemed so approachable because I had at as a millennial, we grew up with GeoCities, that taught me HTML. We grew up with MySpace, that taught me CSS. So, like all of these things kind of like primed us to be devs. So, like millennials got really lucky in that regard, I think. Yeah, absolutely. So, you're getting these skills, you're getting some like small contracts from you know, Steven's Point like snowboard shop and stuff like that. You did go to community college. Yeah, this was like age 28 or so is when you started to learn to program, and at one point you did go and get like kind of the equivalent of an associate's degree. Yeah, yeah. So, I I I spent like like three or four years getting my two-year degree, just because I did it during spring and fall, you know, and like between snowboarding seasons. Yeah, yeah, and and that's perfectly respectable, by the way. Like they call it a two-year degree, but very few people actually just focus on going to school. Like especially in the community college system, unless you're bound for college and you're just saving money going through community college, which is what I recommend doing. Don't go straight into a four-year university. Go to a community college. You'll probably get even better, you know, instruction cuz the teachers are not focused on research, they're focused on you and and teaching you. And it's way more affordable and it's your most of your classmates are going to also be working. It'll be more relatable. They won't just be a bunch of rich kids stuff. So it'll be more interesting. And so like again, I will always stand for community college. I think it's one of the best things about the US higher education system. And uh you know, rent there. But so so you're in community college and you're you're snowboarding continuing to snowboard despite your injuries and you're continuing to build your programming skills and take on clients and stuff. Walk us through that process. So yeah, um basically I realized I needed to move into tech and I had I was living in Woodinville here in Washington and Cascadia is a community college that's like I guess closely affiliated with U-Dub or University of Washington in some way. And it was just so close like yeah, I'll go there, get my two-year degree and then possibly transfer because because they're associated with University of Washington, it was like a no questions asked like transfer that you could do. But I at the end of it I decided I didn't even need to do that, right? Yeah, and what gave you the confidence to skip that? To cuz like a lot of people like University of Washington is a great school. It's probably one of the top, you know, 20 or 30 universities in the states. Uh Yeah, I mean, I had known a few people who did the university thing especially for programming and some of that and it just seemed like a lot of what the curriculum was trying to do was get like too deep into the weeds and I just wanted to do web dev. And web dev isn't really a thing that universities teach that much. Maybe they do nowadays, but back then they were not teaching it that much. And I didn't care about bit shifting. I didn't care about bit masking and like all the you know, CPU registers. I don't care. I I think that might be another one of my spicy takes that you were asking about. Like I really don't think web devs need to care about CPU registers. You should maybe understand caching and some of these things, but in the majority of what you're doing, you don't have to care about how you know, the just-in-time compiler works in JavaScript. You can just accept the fact that it's going to do its job. Yeah. And I mean, the tools and the layers of abstraction, like I always advocate for going as deep as you can, but there are practical trade-offs, right? Like it costs a lot of time and energy to try to understand how memory management works in C and garbage collection and like to go write your own compiler to go write your own operating system. Yeah. And I'm not saying people shouldn't do that. If you're like passionate and you really want to like get that low level and do it, absolutely. But I just know for me, I'm I'm kind of like an ideas guy that knew I couldn't ever afford to pay people to build the software they want, so I just started learning how to do it for myself. Awesome. And I want to talk about like your developer career. So, you were doing freelance work, which is great. And I encourage everybody to start with freelancing. I think that it's the best way to prove your skills and get a reputation and a professional network and people that will vouch for you while also making ends meet. And then when you go apply for jobs, you've got this entire portfolio of actual paid work that you've done for clients, which is way more compelling than just like, "Oh, look at this, you know, uh you know, Unreal Engine game that I made." Which is cool and all if you got people playing it, but like at the end of the day, like they are just trying to de-risk you as a candidate and they look at like the work you've done in the past and they're like, "Well, this person can probably get the job done because look at all this work they've already done. They've already gotten the job done for all these other people, right?" Yeah, I mean, um I I think I agree somewhat. Freelancing is a great way to start, but I think people do themselves a disservice if they stick with it too long without getting like going into like a proper job. Because as a freelancer, you're typically working alone. You don't understand how to work with a team. You get to miss like you miss out on a lot of like the how the project planning should work or how it does work at other companies. And as a freelancer, you have to wear every hat. You have to be sales. You have to be marketing. You have to be the project manager. You have to do all of these things and very few people are going to be good enough at all of them to actually be successful as a freelancer long term. So, I tend to recommend yes, maybe get started with freelancing. You should absolutely be trying to break into a full-time employment gig somewhere just to get like that working with other people and all that. And then as you've done that and learned it, maybe then go back into freelancing. Sure. >> Yeah, awesome. And I appreciate you pushing back on the notion like I do know a lot of people. I'm biased heavily in this regard because a lot of my recent podcast guests have been professional freelancers who essentially expanded and now run agencies, but they could be those outliers you're talking about where very few people are good at like the the sales side and also like communicating work and expecting things out, budgeting, like making sure that that they the payroll gets sent out, all that stuff. I consider myself to be one of those people because like I like I'll boast about that like I'm running free code camp, right? We've got like a 30-person team and we've got things going, but I I agree it's not for everybody. A lot of people just want to focus more and get good at like a key skill instead of just trying to be a jack-of-all-trades. Exactly. Yep. Yeah, so talk about your job search. Like you've got this you know, you don't have a degree, but you do have a lot of client work that you've done and you do have a passion for developing software. It seems that that was never a an issue for you. You enjoyed building. Am I correct? >> Yeah, exactly. Yeah, like the the way I kind of got my first job was interesting. Like, you know, I was doing freelancing stuff, doing Magento sites, and blah blah blah, and sure, it's fine. Uh I then started interviewing, and I had some of the absolute worst interviews ever. Uh man, there was one at like an agency in like West Seattle, where it's like a two-person like shop, and they had me doing debugging of PHP code using pen and paper. It was a nightmare, right? Like, just why are you making me be like the the static analysis tool when we have software that does that? Like, why are you expecting this to be something that someone has to do? Like, it was just That was an awful one. So, I'm glad I didn't get that job. Um there was a couple others where uh like it again, like a smaller like shop, and the interviewer was very combative. Like, I don't know. So, I dodged a lot of bullets, and I got really lucky that uh Fresh Consulting, an agency, gave me a chance because they needed someone to hammer out a WordPress site like real quick. And then, they also wanted to go into JavaScript applications, which is where I wanted to take my career anyway. Yeah, and how did you know that that was where you wanted to take it? Like, the entire time you've been talking, you've been like, "Web dev, web dev, web dev." And a lot of people are like, "Web dev? Like, I don't even use websites anymore. Almost everything I do is interacting with the web maybe through mobile apps." And I think most like, certainly US consumers probably spend like 10 times the amount of time they spend on a given website in some sort of mobile app. I don't know if that's an accurate um you know, approximation of but but like, I can tell you like, certainly less sophisticated and I I I am saying that kind of pejoratively. People that care less about like, the open web, care less about um using websites, and are happy to just be on some platform and be fed stuff. Which unfortunately does describe a lot of people who are frankly tired and probably overworked and having all kinds of like economic, you know, hardships and and like I can understand they just wanting to like doom scroll for a while at the end of a busy day. But but like why web dev? What what is it that draws you to web dev when uh many people would say, "Oh, they're like countervailing winds." Like essentially like web dev's best days are behind it and everything's mobile now or every you know, like there there's so many other areas you could be focused on. Why are you interested in web dev? I mean personally to me uh like I got started back before like mobile apps were even really that good. Sure like uh you know, I got a two-year uh not a two-year, sorry. I got a certificate from U Dub for like iOS development because it was the boom back then. And it's it's interesting, but I I think the magic of web dev is that you can ship so much faster. There's no app store to like wait on. So like your ability to just like continuously improve this product over time is massive. And there's just like there's so much you can do with the web. And I think a big part of it is like why did I want to do the web stuff? Well, because I did GeoCities and MySpace and all that. Like I already had this kind of like a bit of like skill built up. But in my opinion, I think the JavaScript application like web dev space is really powerful and even with stuff like React Native, you can take a lot of that same knowledge and apply it to make building mobile apps, too. So I don't necessarily see like too big of like a a cut-and-dry differentiation between web app and mobile app. To me, it's still just an app. Right? And it it's way different from like a desktop application at least. Like the process and some of that stuff. Yeah, and that's helpful to you know, since you have kind of like walked both both worlds. Um and this is one thing like again, that was kind of a devil's advocate question cuz I'm a huge fan of the open web and like freeCodeCamp heavily emphasized teaching web dev. And when people are like, "But I want to make Android apps." I'm like, cool. Take one of our extracurricular, you know, Flutter app courses or something like that, right? Like I'm a huge Flutter fan and we use Flutter for both our iOS and Android app and they're maintained in the same code base and we treat them kind of like a web app in that we can iterate quickly and ship things and we're not just constantly waiting on the the app store because a lot of it is pulled from the web through APIs. So, we're kind of shipping like a shell and then populating that shell through the web. So, so this is one thing that I I tell a lot of people and I'd actually like to hear your assessment of this as somebody who has probably built a lot of mobile apps as well and has has studied that has that cert from University of Washington in mobile app development. Mobile app development is like web development, but instead of developing for the browser, you're developing for a mobile app client. But most of the back end is the same type of work. Yeah, right. You're still going to have like There are apps that don't need a server, but a lot of the apps that we use every day have some kind of server. So, that's still basically web dev, right? Half of it is still like what you would be doing if you're building a web app as well. Like you have this back end that you have to build and maintain and ship the data to whatever is going to consume it. And this kind of maybe hearkens back to why I think I'm not a fan of server-side rendering, especially like the monoliths like Ruby on Rails, because I just want to build a single canonical REST API and then consume that data into the other things that are better at rendering for what I'm trying to do. So, Astro for a static site, React for a client-side application, right? I I just like the idea of taking this REST API that is fully portable and just consuming it wherever I need to. Awesome. What are some tips you'd have for somebody who is interested in developing REST APIs? Uh, and and for those of you who are listening who are less familiar with what an API is, application programming interface, I think is what the acronym stands for. What I like to say is it's like a website, but instead of sending you HTML to your browser, it sends JSON. Yeah. Yeah, I think the word API is actually so much more broad than that, right? Like everything we do has an API. The languages that we work with have APIs. Like, you know, so that's the trickier part, but then REST >> I'm talking about I guess specifically REST or GraphQL type Yeah, I just wanted to make sure that was like more obvious at that point. >> it's an overloaded term because technically anytime any sort of software talks with another piece of software, it's through some sort of application programming interface. But we're specifically talking about like web APIs. >> Yes. And here we're talking about like REST APIs. The main reason I have to put that in quotes is there are people that will push back on like HATEOAS and like all the things that like REST should be and self-discoverable and blah blah. I'm not necessarily as rigid about that definition. I just, you know, I know there are people that are. But the idea of just simply like having this server that spits out data and then you can decide the rendering of that data, the presentation of that data based upon the the medium that you're consuming it on. So, that could be your browser, that could be a mobile app, that could even be your fridge, right? All of these things could just be getting data from some place. And how do you get that data? That's what your REST API is doing. Awesome. Well, while while we're on the kind of like space it takes, we're going to get into some other cool stuff in a moment, but you One quote that I love from you is programming languages aren't sports teams. Don't pigeonhole yourself. Good ideas are portable. You don't just have to be a Cubs fan, you can be, you know, a fan of the Cubs and I don't I don't know that much about baseball, but like the Red Sox. Uh, you know, you you can be a a fan of many programming languages and you don't have to fall for like kind of tribalism, if you will. >> Yeah, I mean, it's a common thread on like a lot of streams I see, where um you know, I I'm not going to name the streamers, but there are streamers that are very anti certain languages and very pro others. And like it's a really fun vibe on their channel when they can kind of like group up and like, you know, get that like herd mentality around those things. Like it works for their channel, but for my channel, I really dislike that. I because learning a new programming language makes you better with the ones you already know. Learning Rust made me a better JavaScript developer. Learning Go made me a better Rust developer, right? Like just understanding and learning the different patterns, right? Because like I like you quoted me, good ideas are portable, right? You with the evolution of like effect TS in JavaScript and TypeScript, that is basically taking a whole bunch of like functional programming ideas that are not as prevalent in JavaScript these days, but it could be and it makes more robust programs if you can like handle these things the way like that functional programming languages do or just like some of these more robust back-end languages have figured out. Yeah. So, it sounds like you're you're kind of trying to get the best of all worlds in terms of like why not sample a little of this, little of that. Uh so, that's a really cool way to be. I want to talk a bit about how you keep your skills sharp. I mean, you're a professional developer, you're coding for 30 hours a week on stream, and then you're also doing your full 40-hour 40-hour work week at Git Kraken, which is some sort of version control management tool. I actually don't know a lot about it. If you want to just give a Yeah, so Git Kraken's a desktop Git GUI, like that's the main thing. Uh we also have Git Lens in VS Code. You might have that. >> Okay. Right? Um we also have a web app. We have some other things. Most of it is around just making Git easier to work with. Okay. So, it's a >> Kraken, I'm not writing nearly that much code. I'm I'm a developer advocate, so I'm making content, but it does mean I have to like set up demos to like actually use the product against, right? I have to set up merge conflicts so I can demo our merge conflict resolution tool, things like that. Yeah. So, you're kind of like setting traps so that you can fall into them and then work your way out of them. Yep. That's awesome. So, one thing I have is just like you're keeping your skills sharp. You're learning all these new tools cuz you kind of like there your audience is probably doesn't want to just watch you build the same project over and over again. You constantly have to find new problems to solve. How do you keep your skills sharp and like what is your information diet? What is your like learning routine? What is What is some of that the ways that you keep yourself in shape? So, um the main thing I do on my stream is I build side projects. So, I'm I'm not necessarily doing like reaction content like some other streamers do. I'm not necessarily like like focusing on lead code or anything like that. I'm building projects and by building projects and like seeing them through, you're going to solve problems that you wouldn't necessarily think about and it's it's always something kind of new. So, that just keeps me guessing and learning. And then when it comes to like other programming languages and things like that, I just I don't know. I find it fun. I like to tinker. Um yeah, I just I like building stuff. Yeah, and and that is 100% coming through in your stream which I've enjoyed watching. I'm I'm not like one of those very vocal people that's peppering you with questions. But like you have like an incredible like bedside manner so to speak like a physician almost kind of like like just the way you talk to people in in like kind of give people in insight into your thinking pattern and also just like the the kindness with which you receive people that have tuned in. Like you're so hospitable. It's It's really incredible. I would say most of the time I'm hospitable. I I'm I can be a jerk sometimes. There are definitely some people that would say so. So, Yeah, I mean you don't want people to push you around and take advantage of you, right? You have to stand up for yourself. >> Yeah, exactly. Like it's my stream. I want to I want it to be the way it is and I am sometimes a little wary of new people and I need to be better about that. But, yeah, I mean, when you stream 30 hours a week, you're going to maybe have moments that you're less proud of. So, I'm working on >> capture 30 hours of any given person's week for long enough, you're going to catch them in weak moments where they lost control or they lost composure or they just did something silly and embarrassed themselves. So, why stream? So, this is actually kind of a fun story. Uh the way I got into streaming, like I didn't even know that there was programming on Twitch, right? Like, you know, software dev on Twitch. Uh I did an interview for Mixer. Uh this is probably in 2017, maybe early 2018, something like that. And Mixer, if people are unaware, was the Microsoft-owned version of Twitch. And, you know, they they paid Ninja >> of money to Ninja. Yeah, that's all I know about it. And then they shut it down and left everybody out in the open like they'd been building their platform. It was pretty pretty dick move on their part to just shut it down so summarily. Yeah, yeah, pretty tough. Um but yeah, so I interviewed at Mixer and uh like basically they were a company that got acquired. So, the the CEO of Beam, which is what it was called before Mixer, uh he was one of the interviews that I was like interviewing with. Uh Microsoft does like a four-round process. He was interview number two, I think. Um but I'm sitting there like chatting with him and I remember one of the things he said was, "Man, it'd be cool if you streamed just because you would understand like the customers better, right? You'd understand our users better." And I was like, "Well, all right." Yeah, I didn't get the job at the time. Uh I felt like, "Well, maybe I could try again in the future. I should probably figure out this streaming thing a bit." And that's when I went and looked at Twitch and saw that there was actually like software dev and that kind of blew my mind. And I actually saw a streamer, uh his name was like Adam13531 back in the day. Now it's like Adam Learns Live. And I just saw that he was just working on a side project and that was like at the time I had had all of these projects like in a Trello board that I wanted to work on that I just I never seemed to have time for. And I was like, well, maybe I'll start streaming and then I can work on those. Then within like the first month or two I had knocked out like three or four of the projects I had I'd always wanted to do, which was perfect. Yeah, that sounds awesome. So, uh what are some of the like what's the stream like? Like what is a general flow for people who haven't tuned in uh to a Chris Griffin stream? Like in terms of like take us from beginning to end like what a typical stream might look like. Mhm. I mean it has changed over time like uh currently I just I'll like start out we have like 5 to 10 minutes sometimes longer of just like you know, starting soon screen and like hanging out like chatting like, "Hey guys, you know, how's your day going?" People coming in saying hi and that's where I'm like, you know, posting to my Discord of like what my plan for the day is. And I usually like I have an idea of where we left off the night before. I have an idea of like what features we want to launch. I have a a linear board with all this stuff in it. And I basically just like craft my like today command in chat and also like my Discord announcements so people can like kind of like figure out if they want to show up that day or not. And then from there I just I start working. Uh you know, just knocking out the tasks and doing that stuff. There was a time where I was doing like what we called like the Hacker News crawl where I would like find like news articles and just read them and we'd like, I don't know, I had the idea of maybe doing some like Primagen style like reaction stuff. I'm bad at that, but it was still like a good way to keep up to date with things. The I think one of the nice parts about streaming is that I don't necessarily have to do that anymore. People will just come in and ask about it, right? And so I don't need to do the discovery of of news on my own anymore. >> So, essentially they're bringing you like interesting articles to you to see what your thoughts are on them. Yeah, yeah, that happens all the time, for sure. Like, "What's your thoughts on blank?" And yeah, if I hadn't heard about it, well, I guess we're going to talk about it for a half hour or so. Awesome. >> very like free form in that I will happily rant about something for a half hour to an hour and then get right back to work. Yeah. So, let's say somebody who's listening to this first of all, I'd encourage them to spend some time watching your stream before they attempt to do this themselves. But, let's say they are thinking like, "Hey, I'd like to stream. I enjoy programming. I enjoy talking to people. Like, I'm pretty outgoing person." Like, what would you recommend they do? Where where would you recommend they get started if they wanted to start streaming? So, like, I'm always going to recommend that you have a camera and a microphone and some decent lighting. It doesn't have to be a perfect camera, right? You can get by with like a really cheap webcam, right? Like the There's like a a Logitech C920 or something like that. I think there's a newer model number. >> one I'm using. I'm not a gearhead and I just use It's good enough. I've got natural light coming through my window. It's good enough. I don't need a 4K webcam or anything. >> important than the camera in most cases. And there's like a Harris Heller video that talks about that specifically. He shows like an expensive DSLR with bad lighting and then the C920 with good lighting and the C920 kind of looks better. But, yeah, the idea is just get any camera. If you have like an old iPhone or something, those make great cameras for like stream stuff. So, you know, old iPhone, old Android phone, any of those, you could wire those up as a webcam and, you know, like very cheap if you just have it lying around already. Make sure you have a microphone. I think the way that people consume my stream, sure, they might be watching. I think the majority of my audience is like co-working while I'm doing so. So, they're just having me on in the background as if it was like a podcast, but it's it's different every day, right? Like it's just completely new and they can just put me on and zone out and then, you know, with their compiling, they can actually like focus and do their thing or whatever. Um I just think it because that's how a lot of people consume stream, your audio is actually more important than the video of your face. But having a face is still important for the people that do watch because it just makes it more personable. There are streamers that don't have a camera in the software category, like uh El Colun Q or whatever. Um he has this like cool ASCII avatar. It's awesome. Uh he can he makes it work, but very like that is an edge case. To try and like think that you're going to be the exception is usually kind of a bad thought pattern. Yeah, and I remember a while back like I was reading about the top, you know, streamers on Twitch in the gaming category, which is where probably 99% of viewing happens. It's not on programming. I think you said that there are like 2,000 concurrents in the programming category at any time? Yeah, I mean that's maybe at like peak, like 2,000 concurrent viewers in the entire category. I think it's closer to around like 800 to 1,000 at any given moment. Yeah. And you're getting 40 to 100 of those, by the way, which means you're getting like somewhere between 4 and 10% of the total audience viewing. That's That's pretty big. I mean, anybody who got like 4 to 10% market share in whatever category they're in, that's that's like they're a market leader, essentially. Theoretically, like I've been doing it for 7 and 1/2 years, so, you know, I'd like to have maybe grown more, but it's still like just awesome. I just like having a community that I can come back to and like it because it is this like 1,000 to 2,000 concurrent viewers that all of like the people in the category are like vying for. It It's not technically like that, but it's still like it ends up being a community. Like you end up meeting and chatting with like the other streamers in the category. You can raid them and like, you know, bring your community to them, They can bring it to you. And it creates this like tight-knit like community within software and game dev that I don't think you get nearly as much in a lot of like the game categories on Twitch. Yeah. >> In In a lot of Twitch, it's like it's a very like zero-sum game to a lot of the streamers. And I don't think it is that way. Yeah. Well, I I can tell you that like my understanding was a lot of the top players who are not like particularly outgoing, uh but like they may not have a face cam on or anything like that, but they're so good at the game even if they're not talking a lot. People will tune in to watch them play, you know, StarCraft or something like that just because they're so insanely good that you can just kind of watch them and learn and they don't really even have to talk. People just want to watch them play. Sure. >> Right? Kind of like people might like analyze games of chess just by looking at the notation independent of like watching like some televised event where there's all this drama and stuff like that, right? Which I I find completely the opposite of like the programming on Twitch. Like in programming on Twitch, you have to engage the audience. You can't just be sitting there working with and ignoring the the chat, right? Like people want to like interact. Um yeah, I don't know. Uh that is like something that really does separate the programming category from from like other categories in my opinion. Okay. So so some tips that I'm getting from you and I'm going to recap them. One, have a good camera or at least good lighting. Lighting's more important than camera. Mhm. >> Have a good microphone. That's the most important. I would personally recommend the SM53, I think is the number. I can't remember the number, but this is the same mic that Rob Halford from like Judas Priest uses when he sings and stuff. He's got a very powerful voice. It's used by like, you know, um the Beatle uh one of the Beatles, man, Paul McCartney. Okay. This is his go-to mic and it seems to be pretty good dynamic mic and it's cheap. It's like 50 bucks or 60 bucks or something. >> So it's like a great deal. But you might have better recommendation, but in terms of audio, this this has done me pretty well cuz I'm much more focused on audio than I am video. Uh even though a lot of people are watching this on YouTube, I wouldn't be surprised if a lot of them had like locked their phone and put it in their pocket and they're like pumping iron at the gym or doing dishes and listening to this. But like so audio, video, those are different definitely considerations, but also being a face in the corner or bigger. Um because I think now everybody's skeptical that like are you a an AI, you know, like >> True. And I Yeah, thankfully like I get that all the time when I'm emailing people, but like I've never had somebody watch a Free Coke Can Podcast episode and leave a comment that says, "Hey, is Quincy like using some AI avatar?" Like because I'm clearly not AI. I'm clearly a real human being talking here and you can see that and you can hear the modulations, the mistakes that I make when I talk Yeah. >> because I don't edit this. I don't try to like A lot of people like edit their podcast to the point that it sounds synthetic because everything's so, you know, clippy and like the second one person starts talking, the next person starts talking and there's no pauses for thinking or anything like that. So like on stream, you can't fake that, right? Like I mean, I guess technically you could fake it. Like you could do like like VTubers is an entire category and they're not putting their faces on, but they've got this like emotive kind of like 3D model and stuff, right? Um and that allows them to be pseudo anonymous and because I I can understand why they would because like a lot of those platforms are way more parasocial uh and creepy. Especially with like a lot of the female streamers and stuff. Uh like the the audience there, a lot of weirdos out there. Uh have you had any experiences with weirdos or anything like that? Any bad I've got like I've got a few dedicated trolls uh that are interesting. I've never met them in person and I don't think like, you know, they're in like totally different countries. I don't think they're that unhinged like that anything weird would happen, but I'm again, I'm a dude. Women have it way worse. Like they have to protect themselves way more. Uh I I have several like women friend streamers like BashBunny and a bunch of others that have to be very careful about how and what they say and they don't want to dox where they are and like things like that. Yeah. Yeah. So, that is a consideration like your personal privacy and safety, but um I mean, I obviously the trade-off has been worth it for you. Like, what do you get out of it other than just like obviously street cred? Like, people are like, "Oh, this guy streams. Like, we know he can code. We have literally thousands of hours of archived footage of bots of him building software." You know, so that's like is that like one of the major things? Like, have you gotten sponsorships? Like, do you make any money from like the ads? Like, you don't have to go into too much detail. But, like in terms of like what you get out of doing it. Yeah. >> Yeah, I think I make like the biggest money maker on Twitch is the subs, right? But, like if we were to break it down, I'd say I make probably between like $400 and $700 a month from streaming, right? $50 of that is like ads and the rest is the subs, right? So, that's people choosing to like give you that money. Maybe to avoid like the ads on stream because they're annoyed by them, right? And they're missing content when the ads are showing. But, yeah, like you know, it's a decent amount of money. It's not the reason I do it though. I have done some sponsored streams too. Like, I did a couple for Microsoft. One was like for the decentralized identity thing they were doing. Another was for their like cognitive services. So, I was like that one was a fun stream where like I built a project that was simply like get doing like sentiment analysis of my video camera and then like changing like a bar of color above it, right? And like thinking like, "Well, yeah, once I get that sentiment analysis, like could I change the you know, instead of just a bar of color showing my mood, we could do something different or whatever." And I never took it any further than that, but it was really fun to mess with that stuff. So, yes, I have done some sponsored streams and those are fun. But again, I stream myself just because like I said when I first started, I knocked out a bunch of side projects that I had been wanting to work on that I couldn't motivate myself to work on off-stream. And I still maintain that. Like the project that I'm mainly working on now, like most of the projects I I have that I've built on stream, I don't touch off-stream. So like and I do that purposefully. I want to motivate myself to come back to stream. So number one, if I'm not working on it off-stream, that means everyone sees every single aspect of the project. They see me struggle, they see me go through like every decision, every thought. And that has value to them. It has value to me too because if I'm not allowing myself to work on it off-stream, that's just extra motivation to click that go live button every day, right? Some days I don't I might not want to like be that social, but you know what? I really want to work on the project. And then other days, I I might not care about the project as much. I just want to hang out with my community. So there's this like double-edged sword of like just doubling the motivation. When one isn't there, the other is like the thing for me. And I kind of like doubled that from like when I was snowboarding. There were days where I just really want to snowboard. And then there were days where I'm working in the terrain park and I have to snowboard. Yeah. >> still like just by doing that, it means you're putting more time in the saddle the way the prime engine puts it. And uh yeah, I just I really value that. Yeah, absolutely. So let's say hypothetically that uh somebody wanted to essentially get into the field. 2026. You know a lot about how you you probably talk with people all the time. We certainly do. About like, oh, you know, the LLM tools are destroying the field. Like there's not going to be any jobs. Or um like why even bother learning programming cuz I can just prompt an LLM a proprietary LLM tool which which would never have, you know, vendor lock-in or anything. Yeah, I know, right? >> Right? Yeah, like uh like why why bother learning programming? Like like what advice would you give to somebody who wants to get into the field who ultimately would like to get some clients, build some skills, get a job, get paid to learn more during their job, and then eventually create uh probably the two exit strategies that I see. With a third exit strategy, I just had somebody who retired at age 38 on my podcast. Uh congratulations to them. Uh but like uh somebody wants to ultimately create like a product-oriented startup, or they want to create like some sort of software agency. Uh and and those are generally the ways that you kind of like move from being an individual contributor who's beholden to some company and limiting their income to you can determine your own level of income based on how many clients you can get, how many people you can get underneath you. And then that's where like you know, the the real money gets made generally is being like higher up in some sort of hierarchy beneath you. Yeah. >> Not in a giant corporation, but in a place that you have full control of yourself. Like let's say that that's the dream for I'm going to like half the people listening to this. Half of the people would just be happy to have a a stable job, but let's say that is the dream. What are What's your current like read on like what people should do to get there given all the the change um going on right now? So, I mean, just approaching it from like a startup perspective. You have to understand your product. Uh you can hammer out a an MVP or a proof of concept really easily with these LLM tools, and that's going to be fine in most cases to at least like prove an idea. But the moment you get past that, you have to worry about security, you have to worry about your users and feedback, and you have to like ship these things in a way that is maintainable and tenable. And I've heard from a lot of people who are in various like agency positions, there is a lot of work for them now because people are vibe coding out these like proof of concepts and then they're not capable of maintaining it beyond that. They're not capable of like making it robust and leak proof. Like the Mult book, like leakage of all of those API keys for every bot on Mult book. That's crazy. Yeah, it's crazy. >> this is going to be a massive loss of data that essentially wipes out most of the value of that company. >> think so. Yeah, right? Like just no matter what as developers, we are responsible for whatever we're assigning our name to, whether A and AI did it for us or not. Right? Someone is that in line item in the Git history of I committed this even if an LLM did it on my behalf. So, you can't escape the liability of writing bad code. Eventually, that liability will catch up with you. So, no matter what, uh learn LLMs, learn how to use them. I I don't think there's any doubt about that in my mind. But don't treat it like some silver bullet. And then maybe not even from like a startup perspective, but from like a working at a company perspective, there's always going to be a need for devs because management never takes on extra tasks. That's not what they do, ever. Right? Back in the '70s, SQL's going to kill developer jobs because management can just like do the data queries themselves. Did that happen? No, definitely not. So, that's my approach to it. I think in general, there will be room for experts. The way that we get things done may change and that's that's always going to happen. Stuff will change over time. How we create the code will change, right? There are people that when IntelliSense came out in Visual Studio, they weren't allowed to use that for some reason. And I think sure, that was short-sided on the company's part and there are people out there who refused to use IntelliSense because it takes away some part of the code. LLM's are just the evolution of that same mentality in my opinion. I want to repeat what you just said because I think it's really profound and I think it really informs a lot of the discourse around this like people have this like weird vibe that like managers are just itching to do more work and they can't wait to eliminate the people that are doing that work for them. Uh, why? May like it's not like unless they're running the company, it's not like they're suddenly going to get this giant like pay bump hey we we laid off all these developers and all their the money we were going to be giving to them we're giving to you now. That doesn't happen. That never happens, right? Maybe you get like some sort of you know promotion and maybe a little bit of pay bump but it you know, you're going to be doing a lot more work. You're going to be having a lot more liability as you said, you know, you've got a lot more responsibility on your back. You don't know what you're doing and uh I I am a manager uh and I have lots of friends and I was a manager before I got into software development. I was running schools. I had teams of like you know, 25, 30 teachers and stuff like that, right? Like that's probably actually my core competency. I'm I'm a much better manager than I am a developer. So again, I don't mean any slight to managers uh but they they have a hard job too and they're not all just like the Dilbert boss. Like there are good managers out there too. But like what you said, you said I just want to quote it directly cuz I I I've been taking furious notes as you've been talking. Management will never take on extra jobs. SQL did not kill database administrators. Yes, in theory a manager who knows SQL well can just go go get the data themselves. They could probably just you know, get the reports generated and all that stuff and and to an extent I think actually a lot of these LLM tools are going to be like more dangerous for like people who are doing like data science kind of like adjacent type roles not like the real hardcore data science but like the people who are just doing quick data visualizations for management and stuff like that um because it does make those tools a lot more accessible to managers and managers are much better like a manager can look at a spreadsheet and generally understand what's going on. They can't necessarily look at a, you know, uh like a database schema or a code base and understand what's going on, right? Even us as devs, we often struggle with these things, right? And we're specialists. So, I I think that's an extremely heartening observation. Also, what you said, LLMs aren't a silver bullet. Learn how to use them, but don't treat them like a silver bullet. Um and I think that's an extremely practical perspective. Um I just want to end on one more question that that you are uniquely qualified to answer among the many guests I've had. This is not a programming-related question. Uh we've talked about programming plenty. I hope everybody who tuned in to get Chris's programming takes has gotten their fill cuz, man, there is a lot of knowledge here. Uh but and and again, I'm going to encourage everybody to go watch your stream, watch this man at work. Uh but you've spent more than 2,000 days on the slopes snowboarding. And you lived as a a self-professed snowboarding bum. Snowboarding bum. Which there's ski bums, there's beach like surf bums, there like any kind of like I guess like relatively inexpensive sport where there's like not like you're not going to generally find like uh polo bums. Right? Right? But but like any sport where where like anybody in theory if they have some time, they can spend like a thousand bucks and get the gear that they need and go hit the slopes, right? For people out there who've always wanted to do a ski trip. Like, "Oh, man, I've really wanted to go skiing." Like, "But isn't that expensive? Like, don't you need to go to like some big resort and spend like what is the most economical way you would say to somebody, let's say hypothetically they're not going to take their kids, maybe they're even single and they don't have kids or anybody else. Like, what would be the most economical way if they're in the states to just get out on the slopes and try either snowboarding or skiing?" And like like what what would you advise them? Yeah, see, I mean, I think that's tough. Um just because it is not a cheap sport and it's gotten more expensive since I was even a snowboard bum, right? Over the past 15 years since I kind of like, you know, stopped being a full-time snowboarder, it has gotten exponentially more expensive, it seems, right? Like, uh just Vail buying up all these resorts and charging $200 a day. So, I think that's tough. Um if you can get out for night riding, that's usually a lot cheaper. If you can get out for like off-peak days, that can usually help. Um rentals are a good way to like try things out, but eventually you're going to want to get your own gear. And what I would say about getting your own gear is do not worry about getting like the latest and greatest stuff. You can get a snowboard from 4 or 5 years ago that is just as good as the stuff out there right now, right? Like, the tech doesn't move that fast. Now, you don't want to go 20 years back, but five five-year-old snowboard is going to be just fine. Right? So, like, don't worry about getting like the latest and greatest newest gear. That might be like a good way to like adopt snowboarding as more of a hobby. And maybe not just for like a quick trip, but if you find that you really like it, get a season's pass and buy it early, like before the next season, right? Because that is the the best way. If you can get a a Steven's Pass season's pass for like, I don't know, like at the earliest, I think like $500 for just Steven's Pass, you pay that off at like lift ticket rates within five usages. Like, five days on the resort and you've paid off that entire pass. Right? So, just thinking about like it's a lot harder to do it and dabble. If you really do start enjoying it, there are ways to make it cheaper. Uh in terms of terms of gear, just to pull on one more thread, like if if you would you be comfortable uh if you're just going to go like not do it at like a really serious level, but if you just wanted to get some gear, uh and you saw like what looked like a good deal on like Craigslist or something like that, is used gear viable or is it dangerous to use used gear? I think that's the toughest part because used gear, it's hard for a beginner to know what's actually like new enough that it's worth using. Um you probably don't want to do used boots, right? Like someone else's foot just sweating and stinking in this thing. You should probably get your own boots at least. Uh but snowboard and bindings, yeah, you can get used snowboard and bindings just fine. The problem I would say with like Craigslist and Facebook Marketplace is people people try and sell like 4-year-old snowboards for what they paid for it, not recognizing that these things do have a depreciating cost. So, at some point I you can get good deals on those marketplaces. I In general, you get people selling something ancient, something that they maybe somehow got a free rental snowboard and they're just selling it for 40 bucks, but rental snowboards are kind of junk anyway. It's a lot tougher to find those deals on Craigslist that are actually like a good deal. Um and yeah, bindings are one of the things that would be maybe the most dangerous of like buying used because if it's really old, like the plastic in bindings oxidizes. Uh when I was working in rentals, there were skiers that had these like ski boots from the '70s and they would just it shatter, right? Because the the boots have been oxidizing in their closet for the past 20 years. They go out maybe once a year and then on a somewhat colder day, they go out and their boots just blow up. Uh and that was like a very common thing in the in the rental space. Okay, so maybe don't don't uh like get it from a like Are most of these rental shops owned by like the the resort itself or like some some contracted like But but like how safe is the rental gear generally? Are they are they pretty vigilant about testing it? Oh, rental gear is usually uh pretty good. Yeah, like most most uh rental shops I I don't even know if they're like fully like buying their fleet every time. Like some may have like a deal worked out where they're getting like you know, two like no older than 2-year-old gear and they're just like cycling it like through like the the company like as a lease kind of program kind of thing. So, it just depends. Uh rental gear is typically not going to be the best, but it's better than than like a 20-year-old board, you know. In terms of safety, that's another thing people might be worried about. Obviously, you said you have lots of injuries and stuff. I assume you take more risks as a snowboarder at least you did when you were younger than like the typical person who's going for the first time. But, would you recommend wearing a helmet? Um I mean people should probably wear helmets. I don't because I have opinions about that. I don't think my opinion should matter towards other people. You should probably wear a helmet. Uh okay. Yeah. And then like any other like just safety advice that you would give people like like everybody knows this, but maybe you going snowboarding for the first time or skiing for the first time. For programmers especially, when you're snowboarding if you're going to fall, don't put your hands out, right? Tuck up, right? Because your wrist is how you make your money as a programmer, right? You cannot afford to mess this part up. So, just learning how to fall is maybe one of the most important skills you can have as a snowboarder. And that's maybe why like I'm not as concerned about the helmet thing because I have this habit of like boom, this is where my arms go whenever I'm doing like a major fall. It's just like reflex cuz in powder when you fall and you're rag dolling, you don't want your gear flying off, right? You're with a helmet that wouldn't be an issue, so maybe I should. But, just like having your goggles fly off into the powder is so annoying that I've just developed this habit of if I'm falling, boom, that's where my arms go. And it just saves me from like you know, wrist injuries and some of that stuff. So, in general just like yeah. Figuring out how to >> be scary because you're going to like fall further, right? Like you're going to have more kinetic energy when you hit, but you're going to be hitting on I guess like a more durable like if you think like in boxing, you know, people block with their arms and stuff. Yeah. Right? So, so in theory like I guess this is durable enough. Well, I mean in general like the just the physics of it there's like uh the amount of pressure that something takes is based upon like the amount of force times the amount of like surface area that's hitting. Yeah. So, if you're like increasing that surface area, you're absorbing more impact, right? Regardless of the extra force you might have gotten by catching yourself. >> an an extra, you know, foot because you're like this instead of like this. Like I always would fall and like put my fists out instead of my fingers cuz I didn't want to bend my arm like that, but like this sounds better. I'm going to start doing this. Next time I'm boarding. Um man, this has been a really helpful uh like I'm I'm so glad you shared those uh snowboarding tips. Like for anybody that's going out there like if you get a chance, like it's so fun. It is expensive. It It is cold. That's the That's the thing that a lot of people like, "Hey, I didn't sign up to be freaking freezing the whole day." And it does get really cold and it gets really awkward cuz your nose is dripping and you're like rubbing with your gloves. Do you use finger gloves or mittens? I do mittens. Okay. Cuz your fingers are close together so they keep one another warm a little bit. >> they keep warmer that way. Like the gloves I have are extremely thin. Like some people get these like super thick mitts, but yeah, I just use very thin like mittens because the fingers are close so you're not getting like the cold pinky. Uh and yeah, I don't know. Like uh what I think a lot of people mistake is they end up bundling up too much and then they get this like sweat going and sweat is actually like the enemy when you're snowboarding because that will actually get cold way quicker and you're going to start like Yeah, you're going to get hypothermia. >> Yeah, exactly. sweat gets super cold. So, you want to avoid sweating. Uh which is why like I do very thin mitts. Yeah. Yeah, I mean like like one of my friends snowboards and he he just wears like a t-shirt basically. And sunscreen, of course. That's the other thing I'll say. Wear your sunscreen when you're snowboarding or skiing. Uh one last question. Like ski or snowboarding? Like if if somebody's going on a trip and they've got like small children, like my kids started off with skiing like and they've only gone I think once. Which which by the way is a very privileged thing. Like I I realize that not everybody has the luxury of taking their kids skiing. Like that's a huge kind of like expenditure taking your family and and getting a hotel and like going up and doing the lift tickets and the rentals all that stuff. I mean, you're potentially out like thousands of dollars if you've got a family of four. Uh not to mention the travel costs and stuff like that. Um but uh so so I don't think they're likely is is I'm very proud that I was able to take my kids skiing and they really enjoyed it. But would you recommend kids start with snowboard or skiing and then adults as well if they've never done it before? Where would you recommend they start? I think that's that's tough. Um I think skiing to start out is worthwhile if you've never done anything where you're kind of sliding like that. So, if you've never done skateboarding, if you've never done ice skating or rollerblading or any of that, right? If you're not familiar with that like sliding feeling, skis are probably a better way to get started. Um especially for kids. I I think the nice part is it's like so kids are still figuring out how to use their body, right? So, like they're still like not even that good at walking yet. So, at least give them like the thing that's closer to walking. Um >> Yeah. At least for like the first few times. And if they start to really like being out on the snow and they want to snowboard, well, yeah. I think snowboarding's great, too. Um the part I will say is a snowboard does feel more versatile to me. Like I can take my park board, which is a a It's not the biggest board. I'm not the biggest person though. And I can ride powder with that thing. I can ride it anywhere. Whereas like skis, you end up needing like very specialized skis to enjoy powder better. All right? You need very specialized skis to ride park better. Things like that. And I can just I can use my same snowboard anywhere. I don't have a quiver of snowboards. I just I got one. Yeah, very cool. Well, Chris Chris Griffing, it's been an absolute pleasure interviewing you on the freeCodeCamp podcast, learning more about you and your prolific stint on uh Twitch streaming, programming, and making programming accessible and and you know, just like the mistakes and all approach, building the the entire project on stream, so people get to see every aspect of the struggle, the creative process, the piping and plumbing and all all that kind of mundane stuff that you do as well. I I mean, just putting that out there, that's a huge service for the developer community. So, I want to commend you and I want to thank you again for coming on the podcast. Yeah, I appreciate it. Thanks for having me. Like uh yeah, I'm a huge fan of freeCodeCamp. People come in all the time asking about like, "Oh, how how should I learn how to be a web dev?" I send them to freeCodeCamp. Thank you. That means a lot to me. And uh yeah, uh shout out to anybody who's a regular at Chris's um stream who who came in here, like we welcome you. Uh and we have a Discord too. If you're if you're in Chris's Discord, we're just like a Discord hop away, chat.freecodecamp.org. And we'd love to chat with you, too. And we are not going anywhere. We're going to focus on continuing to inject rigor into your studies and not just show people a bunch of shortcuts with LLMs and stuff like that. Like as I've said many times, I don't want to make this podcast very long. I'm not a detractor from these tools. I think people should learn these tools. But I do think that they should learn the fundamentals like Chris has done here and that he continues to show the manual process of developing software while using some contemporary tools as well. Uh it's just like a very balanced take on this. and and I really enjoyed this conversation. Everybody until next week, happy coding. Yep, happy coding everyone. Thank you.

Generated algorithmically for Search Engine Indexing.

Summarize Another Video