🚀 Prep for Tech Career Beginner Boost

for prep for tomorrow's beginner boost. Uh just a reminder, the beginner boost for tech careers is going to be focused on all tech careers and in general uh when it comes to like preparing your the yourself for the culture and all of that. But then it will also be uh geared toward the technologies for for anybody who wants the more of the the hard skills uh all around. So So that's that's what we're looking at. Uh last night I spent a significant amount of time getting the uh stuff ready for the actual some of the logistical stuff like you know where are we going to put the the container? or how are we going to do that? And how are we going to continue to make these videos as as quickly as needed? I apologize again. I have a cold. It's turned my my voice into a of a mess and I've got my my hanky hair, but uh it's going to it's going to be it's going to sound like this for a while. I do have to leave in about an hour to go uh lift. I'm going to go do some pull-ups. Uh, but I'll be back and I'll come back. I'm going to be streaming most of the day today because I need to get as much of this done before tomorrow as possible so we have a good kickoff. So, again, the goals for today are to get the OBS renaming tool finished. Uh, that's probably the most important thing. And uh the second most important is to get the the current uh skill stack site. I need to update this too. So let let's actually make a let's make a a number of issues here. Uh actually let's let's do this right now to kind of keep ourselves on track. So let's do let's go into the boost and do issues. This is a good way to do a to-do that you can kind of follow up on. Create a break for nice things. I did that. Close. Close 46. Uh uh update landing page on Twitch with defaults and tags. These are all things that I can do. I think the reminders in 43 got finished as well. Get teeth fixed. This is a funny joke. Um yeah, and we need to there's there's a number of things. So let's let's add the issues. It's just easier for me this way because I'm very ADHD. I don't even think I'm officially ADHD. That's not my my diagnosis. I kind of would like to know what that is, but I have to I I I'm all over the place. So, uh but I'm also obsessive about the thing when I when I switch around. So, it's just my style. And so, I've created a streaming methodology that kind of captures that so I can focus on the thing that I'm thinking about and then do it. And and issues is actually a really great way to do that. So when I'm thinking about something spontaneously, I can just write it down. It's also my style for writing. That's why I like Zetocasten method for writing as well. Uh and I actually going to make some videos about a writing technique that uh was used to write Lolita Nov used. Uh I'm using that to write my book and uh all right. So issue I'll say uh the first thing is okay. So migrate as asky do we need to get that in there and then what we need to do can I do this I can't remember no yeah issue and then we need uh What did I say? See, this is why I have to do this because I my brain is very my memory is very bad. Let's say we're going to go ahead and Oh, right. Uh clean up landing page. How you doing, Alexir? Uh submit issue breakout OBS stuff into own repo. So I can put all my overlays in there. Right now one of them has a bunch of secure keys in it that I need to like modify so that the keys can be stored on disk uh without re you know taking over the repo. This is kind of required, but it's not super important. Uh, actually that that does not need to go here, though. Yeah, let's close that. We don't that that needs to go on the other repo. That needs to go on this repo. Yeah. So OBS stuff along with stuff in notes to own repo. Need to move need to move live coded overlays into own repo that also does not contain secrets in the code and I could probably container consider no I can't containerize it because I have melt the the thing. Actually, I could because I I'm running servers in there. Containerizing. That would be really useful. Other people could use it if I did that. So, that might be something. There's so much tech that I want to do. It's funny because I'm kind of got the bug right now. Kind of got the tech bug. I I go in and out. Sometimes I have it other days. be like, "Why am I not on the mountain climbing or something?" All right, so we got that. Uh, so the main thing we want we can need to get the landing page cleaned up. Uh, this is it. This is the the 48 is for is for GitHub. I don't know if I should say that. Issue 48. Um, gh issue edit 48 title uh cleanup. All right, thanks Rob landing page. We need to do we need to change the donation page as well. Default tags migrate skills site ask do um issue add uh update uh GH sponsors sponsorship uh information. Go add that back so people can tell how they want to help. We already did the nice things. Um, and what else do we need to get today done? We need to do I think that's most of it. I don't think we have I don't think we have much more than that. Then we need to do the first few videos. Uh, okay. Because that's that's kind of where I was going to go with this. I'm not going to waste time repeating myself. So I'm going to rather than say things I'm going to make a video about it and then I'm going to and then I'll post the video. So right oh right right now we're going to make that was the other one issue is like uh create websocket uh listener and sub uh great websocket listener and uh event sub uh conf uh configuration web hook. Let's say websocket listener. Uh, wait, let me do that again. Create OBS websocket event listener with subscriptions. And so the search is just going to be like a YAML file that says what you're subscribed to and it'll go find it and then it'll run the thing that's subscribed to and the thing will just be a script. Uh we could do that maybe with agent with agents or something in AI, but I don't think we need to do that. So this is another one we need. I got to watch my time by the way. So 7:35 when it's 8. It's about 8:15. I need to go for a second. Take a break. Uh okay. So, let's get this done. Let's start out with the the OBS thing. Uh, what would be really cool is if I could Oh, you know what would be even better? I I have to do this. I want it to change my title and everything based on the issue I'm working on. Oh my god, that would be so freaking cool. I'm going to make that right now. Issue devel um 51. Oh no. GitHub issue edit 51. Edit issue 51. Uh, all right. So, create OBS web socket. What do we want to call it? subscribers. What I wonder what my AI thinks. I wonder what she thinks. Uh, how would you summarize creating such a thing into a GitHub status gear wiring OBS recording events to to web hook automation? Yep. Wiring OBS recording events to web hook automation. I don't even think it needs to be web hook. Wiring OBS events to bash scripts. Oh, damn. I know we can do this. We can say OBS events. How you doing? Good morning to you. Wiring OBS events. Hello there YouTube. Wiring OBS events to uh to commands. That's it. Okay. Now, yes. Issue. Uh actually, let's get back here. Issue. Well, uh guess this is kind of related. sources to say uh uh work on a specific issue how to how to do that. So, how you doing Mr. Barl? Yep. Let's see. The boost is tomorrow by the way. Issue. Wait, link. Uh. Um. Oh, cool. Yep. So G issues uh add support or GH issue if chest number. Okay, I'm going to do that right now. Uh, I could do the whole PR thing, but that takes a long time. Actually, why don't I do that? I I can still merge it into main, but let's do that. So, then I can do GH issue develop uh D-C uh issue 7. This will branch me and everything. It's pretty cool. So there you go. Now I'm all ready to go. Uh let's see. We can do a squash emerge at the end. How you doing bull on YouTube? Install GH is not found. Uh what do you mean when you when you try to build a container? When you try to build when you try to build a container, it gives you an install gh error. Interesting. That's good. We need to know that stuff. So, can you open it? Do you know how to open GitHub issues? Can you open an issue against the boost art boost container that sells that describes the problem and then dump the error message, please? Do you know how to do that? So, if you go to the to the website there and then you click on to the to the boost. If you click on issues, it'll say create a new issue and then you can put the stuff in there. That'll super help me because then I can like check it out and I can fix it right away. I assume that's going to be a problem an ongoing problem, but that's one of the reasons I have it so dynamic and I don't have to repush the image every time. Uh so, if if you could do that, that would super help me. Um, I need to step away for a second for uh uh to blow my nose and stuff like that. I'm going to go ahead and mute. I really need to get my stream deck. Cool username. Artix makes Rob. Yeah, I've had that username for a long time. When using the boost container, I was having a huge issue with line endings on Windows, but I changed a lot. you had line edings on Windows. I need I need people I need people who have had problems on Windows to report it. I don't have Windows here available to test it. Um, and I don't think if I run a virtual machine, a Windows virtual machine, and I put Docker on there that I'm going to be able to replicate the issue. Uh, smile plus X Rob. Yes. So, please guys, if you have issues, not only is this this is going to give you, you're going to get credit. If you submit a if you submit an issue, if you submit an issue against the repo, you'll get credit for reporting the issue and your little icon will appear on my repo. So, you can it'll show up in your profile about contribut contributions you've made, like that. So, when you go to get an interview or whatever, some of you mean I care. You might already have job, but but that would super help me. Plus, it just makes it super because I can't I can't get my head around the problem unless you kind of dump the air actual error and you put it inside of the issue. So, if you could just take an extra second to do that and using default pod mount machine. Okay. Uh tripod accurate when it comes to sec. It is definitely more accurate. I've talked about that briefly, but I don't have it right now. So, again, I'm going to go hit the restroom really quick. Yeah, there's a lot lot of really good things going on in the machine learning world, of course. Um this is a Linux line endings. Okay. So interesting. Um, I'm going to need to get a Windows machine to practice this, aren't I? I need to I need to add an issue for this today. I think I have a Windows VM running right now voice com or Linux. Thanks for everything. Yeah. Uh maybe it was an old commit. Yeah, you that's the thing. You got to make sure to do a git pull to get the latest, right? However, I mean it depends on what you're doing. If you did a git pull versus if you you're you're I don't know, it could have been a different machine. But yeah, so it's it's it's a you know, it's a given that we're going to have issues on on occasion. So, we we need to go look into those. So, I'm going to go ahead and look at this issue. Thank you for writing that up. Then I can put you right here on the screen and you can get credit for submitting it. Uh, did I open that issue? What test on Windows? Step 20 of 26. Oh, all right. What's that about? Okay. Um coming in from tstur UWRx on Windows 10 Windows 10. Wow. Uh using Windows with podman the podman VM in default VM when you run pod man machine in it. Here's some output. Uh boost boost go bin run install sh is installed not found. Uh building at step run installer when running when running runtime exit test. Uh that looks like it can't see the install script, but that should not be an issue. Let me check that really quick. Uh I'm going to leave it open, but I want if it might be a quick fix. So run install gh. So, uh, these are the installers that are loaded in from home. I I suspect it's because it's having a problem finding the path. Um, I I wonder if it's because this here, it can't find it because of this I mean, it should be able to find it. I don't see why it wouldn't be able to find that. That seems rather odd. Uh, yeah. I don't I don't But see what we have to figure out is why Windows 10 path. Hey, how you doing? We have to figure out why Windows 10 is having a problem with that. Uh cuz this should take care of it because it puts everything in in there unless it's not in there for some reason. So home Ubuntu local bin and we have installed the GHS there. Podman is running a Linux VM. Yes, you cannot have containers without Linux Lex C containers that is which are really the only ones that we ever talk about. This this is fine. Uh, download copy the binary. Yeah, that's a very odd error. I'm not going to lie. Is not found. I I wonder if I put a full path in there if that would fix that stuff. I wonder, you know, like if I did a if I did a run I'm I'm gonna I'm gonna ask the AI. I wonder. You know me too well. You totally do. So have a look at this container file and tell me why install gh might not be found on Windows 10. Worth a shot. You try that didn't work. So what did you fork did you fork the repo and change it? That's some pretty advanced things that you're doing there for you to say you've not regularly containers. Most likely reason never gets copied uh never gets copied into the directory that is on path in your container. This line blah puts the repo contents at the root of the container file system. So if you have a file name install GH in the project route it lands here. I do not. Uh how you doing Misha? It's good to have you. Somebody shout me out. I need to make a command a terminal command to shout people out. Try to container care issue. Uh yeah. Okay. Can you try this? Does it This doesn't build at all. Right. Can you Did you comment out that line? Because you really don't need it that much. Comment out the run line and see if you can get it to build without it and see if it hook if it if it barks on something else. Actually, I'll put that in the I'll put that in the issue. Yeah. Uh, it's always better if I do it that way because then you guys can do it too. Yeah. All right. Okay. Thank you so much for looking that up, though. That's the kind of help I really need. Really need that kind of help. Jalapy, it's not here, but he was so much help with that as well. Um, yeah, we we need to figure out a way to test on Windows and run a VM under Mac. I don't think I have my VM system running and I have to like revisit the whole use of VMs because you know VMware is kind of in flux and I haven't even looked at them in a year uh in order to test on Windows. I I need to get what I used to do is I would have a Windows machine running and then I would uh I would remote access it but I don't I don't have that server connection right now. So I need to figure I actually need to figure out how to do this on Windows. So, like how to install Wistm on Windows, how to all that stuff. So, that needs to be done. I'm feeling a little bit better. Hey, Ray. Um, I I I'm trying to decide if I actually even have VMware on here. I do. I have VMware Fusion on here. Uh, run in the background. This is I might start stuttering because I'm kind of pushing this little MacBook Pro to its limits. Uh using Fusion some security fixes. I bought Fusion and stuff. I own all this stuff. Uh Red Hat Enterprise Linux. No virtual machines. Where is my other virtual machines? I don't even remember how to use this scanner for virtual machines. Document virtual machines localized share. I think I might have it in here somewhere. I don't need Red Hat right now. I go ahead and close that. Windows Mac. Yeah. Ma'am, I'm never using Virtual Box. Virtual Box totally did me wrong. Uh, new install from discrimage. Get Windows from Microsoft. Wait, what? Yeah, I want to do that. Windows Edition Pro. No, just pro. Wait, did they make it this easy? [ __ ] This is definitely going to tank my stream. I get we fusion for free at work because Windows is required to get stuff done apparently. All right. Well, that's like slowly doing its thing. Uh, let's uh do why are the OBS events up? This is kind of really cool. Oh, no, no. Let's make it let's make it so that we can do Yeah. Uh, we want to add support for GH issues if it's just a number. So if I do GH status, I want it to grab uh the current uh issue uh by number. So uh you know I know I I know generally how to do it. So I'm just going to prompt for this. Uh what is the command that to just output the issue title or a given issue uh number from GitHub this I'm just modifying a little thing in tech. Did you see that one? The dentist one. Yeah. Issue view blah blah blah title. Is it really that easy? You've got to be kidding me. God, I love AI. Oops, that's not it. Oh, I got copy. How about was the last one we did? 42 seven uh GHSU view seven. Oh my god, that was so easy. That I love the GH tool. I love it. The rest is like super duper easy. GH status. I can't believe how fast we're going to get this done. Uh require clear status. Well, blah blah blah acquire gh expires at uh then grab API kill. Actually, I'm going to do some recursion here. This is all vibe coded, so it's not clean at all. I don't care. So, I'm going to I'm going to go ahead and put some code right right up here in the front. Yeah, right here in the front I'm going to say uh if one uh is a number, how do I say? I'm gonna I'm gonna v code that too because I don't want to wait around. Write the bash that checks if first arg is a number only and if so does something. It's I it's like it's going to be if blah blah blah. Yep. It's just going to use a reg x. That's why I wanted that. I can write that reg x. I didn't want to look it up. I know reg x. I just don't want to bother. So uh r equ= 1. If ar equals one then argument is a number. Uh if if the first argument is just a number then I want to do all the rest of this stuff. So by putting produces verbose ugly code. Yes. But I don't care in this case. I don't care. That's that's what is really good about rapid prototyping. Um I'm going to call this I'm going to call my cell. Okay. So change it so that it calls itself the same script. Uh but after getting the GitHub issue or that uh number and adding a gear in front There we go. Look at how fast I did that. That's insane. It took me how many seconds? I couldn't have even typed it that fast. All right. So, uh, our one, we don't need this issue equals one. If one equals a number, then do this. So, let's try it. So, now we can do uh All right. So, we're going to say G status 7. Oh, damn close. Invalid value. Message type. Message of type should write it invalid value. No. Okay. So, wait, where's my exec? Oh, okay. Here we go. So, exec0 title and then all the rest of the arguments. Why didn't that work? I wonder. Let's go ahead and echo it first. Oh, wait, wait, wait. Um, I didn't deploy it. Derp. I didn't I need to start making a deploy script status. Quick and dirty deploy. Okay, here we go. Excit users G status. Uh gear add support for issue of chest number. Oh, actually no. You know what we can do? We can do this instead. We can say I wish I wish we could tell whether it was a if it's a bug or a a new thing. Regular space patterns. Yeah, it's good. Reges are good for the right thing. Grab kill API rate limit already exceeded. Why is that? Because my server is like pinging it all the time. [ __ ] I think it is. I think it's because my server is slamming it. I do. I think I think it I think it slams the API too hard. Yeah, it does. Um, I might want to change this. I did it this way so that it would fetch it from GitHub. I could just change the GitHub status anytime and have it work. But I can't send an event for that. So I have to pull. And the polling is what's killing us. So uh interesting. Yeah, GPD knows me. Um, so this is I need to make a workaround for this. First of all, I should not be pulling this. I should not be hitting the API once every 5 seconds. That's like not okay. That's that's because it got vibe coded. Uh, I would never have done that. Uh in the past when I've done this I've just used a file and and if the file changes I pull the file and if the file changes I go to do it and then when I change status I just write change what'sever in the file. Uh and then you know I can create any number of things that allow that file to be changed. I cannot do that with a get status change though. So, if I do the if I change the code that I'm thinking about doing, uh, I won't be able to change my status on the road, uh, by just changing the GI status. But the truth is, I don't need to do that anyway because it wouldn't be a GitHub status change. That would be a change to my IRL stream title, which is really something I already have on my phone that I can do. So this the entire premise of this like having everything synchronized against the GitHub change uh is probably wrong. Uh so I might actually just v code this. This is one of those cases where it's like hey do we like redo it? What I should just be doing, I should just be pulling this off of off of a file and then I should be appending I should be writing new new statuses to the file and then presenting a menu of like well which what are you working on, right? Uh and maybe not calling it GitHub status, maybe maybe calling it like title or something or like I used to have a program called current. I wonder if I still have that uh like you know get current project or something like that and that might actually be better. Uh the thing about if if you do if you do a command like that then you could just look at what whatever was last written and uh you don't need a server. Yeah, you do still need a server because in order to have it update in the overlay, so it updates in the in the GitHub OB and OBS overlay. Oh god, look at that big little long line. That's really funny. Uh, so yeah, I did not like that. I I just noticed it went it got written on the overlay as well. So what are we going to do there? I think I got to go lift here in a few minutes. Uh I think what we're going to do is yeah we need to make an issue. So get an issue if just the number. We need to make I we need to actually make a a program from scratch that does all of that but does it based on a command and a single file. Yeah. What would be even better is if we made it do if we made it do completion. If we made the if we made the current due completion and then it used the list of all the stuff that we've all the statuses we've already had in the past. That would be so cool. I kind of want to make that. How much time I got? Yeah. This This is actually going to work. It's just our API thing is over. It's ready for some boost. Watch. If I If I turn this on again, it's going to fail. The crazy thing is I actually this is this is completed. The code is actually finished now. So, thank god I vibe coded it. It would have taken me way much longer. This is the greatest thing about vi coding. So, let's say you do a major architectural arc and it goes wrong. You can you didn't lose any time. No, it's it's really great for that kind of thing. So, uh yeah, this in the background really quick. I I want to see if my my API is uh Yeah, it's already exceeded API is exceeded. Yeah. So, uh actually if we I'm going to just hack this program right now. I'm going to come back and fix it. Uh if if we have we don't we don't want to do any of the other rate limiting stuff. Oh no, we can't even get the current status. We can't even look it up. Are you telling me? Wait, I don't think I don't even think I can do GH status through the API. I don't even think I can use the gem command. Yeah. [ __ ] Oh, that sucks ass. Okay, so note to self, don't don't go with the GitHub again. Uh, not on that. Anyway, look at this. I can't even use issue command. It won't work. Watch. That means I can't do any of my GH development. It's Windows specific. Some people had that issue. We haven't been able to find it. I can't even use it now. [ __ ] You know what? It must have been adding all my rate stuff from one o'clock in the morning to the other stuff I just did. Now I'm like really screwed. I can't do any development on this. I usually get a command tool for everything. Um, I wonder if she can tell me how how long I'm going to have to wait. GH has a rate limit. Yep, I know because it's all API driven and the token uses it has no remaining quarter right now. Uh, use the rest API instead of always graphql entirely. Thank god. What if you are already in the repo directory? You can do gh api repo. I don't understand. So the API doesn't have a a limit. GH API rate limit. That's what I was looking for. This I think is hallucinating. I don't think that's a thing. Oh, I guess it is. Used zero resources search GraphQL. So, my GraphQL is only 4,000 integration manifest. I did 5,000. That means it's five. That was 5,000. Wait, what is this? What is this? Is that the reset time? Is that the the date time temp? What date is that? I need to convert that into ISO. Uh March 5th. What? Never mind. Definitely has rate limit though. SCIM. What's that about? actions code auto effects n code search. So I killed the graphql one the exact second one get a will replay. Nice. 35. Why does it say it says March 5th? It's already March 7th. This is stupid. What? Wait, did I say May? It's March. I said it wrong. Sorry. It does. It It says It says March 5th. It's March 7th. What am I missing? It's a bug. I found a bug. You simply get a new a new rate render the next time you make a request. This is this is this like lying then? What am I doing wrong? Oh, I'm on BSD. I'm on BSD. How you doing? So, a couple of questions and BST's data is not the same. Well, my my machine is wrong. So, well, no, it's not. It's 8 o'clock. That's right. Huh. So, how do first of all, how do I do it on BSD? What is the BSD version update? I think it's at something. Is it R? Yeah. Okay, there you go. So, I must have did it wrong. I don't think it did in real time. Conquesting. I think you're on to something. That's definitely what happened. Okay, so that's not too far away. That's like what in five minutes something. Does that mean I get 5,000 API quota all over again or is it just going to give me a little bit, you know, because I mean, okay, there's two ways I can fix this. I can have Well, I think I think I think the answer to this is we need to rethink the status updater and we need to make the centralized status something is a text field on the machine and not and not use the GitHub status as authoritative because the only way to get that is to pull. There's no way to call event hook when that changes. I mean maybe there is. Just ask is there a uh can I let's see does GitHub produce an event that could call a web hook when the status changes. We need to know when the status changes with a with an event instead of polling. Uh second github does not emit web hook events for user profile status changes. Uh the future is only accessible through the graph change user status and there is no web hook for it. However, GitHub does emit events for many other things that can and those can trigger web hooks. Things you can do with web hooks issues push pull release discussion checkin deployment. Okay, so that answered the question. I'm glad because those other things are pretty awesome. Uh so uh things do not do work status events. Uh so your command like GH status or JHPI graph change status cannot trigger my book directly. Uh pull the status periodic. That's what we're doing. We're pulling the pulling. The problem with pulling is that the granularity of the change is really low. if I want to remain under my quota and I definitely do not want to screw with my GH quota because I use it for all kinds of other things. It would stop me from anything with GH. I don't want to screw with that. So, that's not worth it. Uh this is the polling example that we used. So no more polling which means uh we're going to then therefore instead of making GitHub status authoritative we're going to make whatever is on disk authoritative and that gets into I already wrote a program to do this years ago and I'm I'm going to have the a I'm going to v code it again this time. So we just probably need need to make a re uh we just need to make a new one uh using the other code. Plus, it's probably probably time for me to clean up the code a little bit. Uh, I probably should make a GitHub repo for this. Uh, yeah, I I probably should I probably should make a little mini project. A mini I always have I'm always torn about whether I should have a mini repo or I should, you know, make a uh, you know, a common monor repo for all these kind of little tools. But in this particular one, I think we probably do want to put it all all in one place. And I think we just want to call it current. Uh, you know, I could push put in my dot files and manage it that way. But then when it's when it's this big a program and it is just a little hack, it's kind of nice to have it self-contained into a repo. So we'll break that out into its own repo. And that should take us uh a few minutes uh 10 15 minutes or so. So, I'm actually going to go uh uh lift and uh do some follow-ups and stuff and I will come back and I'm going to take a take a break and uh when we come back I'm actually going to write the current uh the the program called current and we'll integrate that with recording events in OBS. So, uh, actually that's also going to be a part I think I'm probably going to make an OBS tools, uh, repo for that for that for that purpose. Uh, I don't know if I have I don't remember if I have that. I have OBS config. OBS config is like all my settings and everything. I should probably do do it in there. What else do I have? Man, I haven't updated my OBS config in forever. Yeah. The problem with OBS config, I think OBS config is private. Did it say private? Yeah, because it's got like my keys and everything in it. So, I don't want that. Um, I should put OBS tools. Did I get sleep? Yeah. I went right to sleep. Uh-huh. Uh, okay. I know. I'm still wearing the same shirt. I slept in this shirt, though. You must know. Yeah. That's why it's all janky and weird. I'm going to go lift and have a shower and everything. I was just waiting around for the for my um my collagen to kick in. You guys take collagen an hour before take it with vitamin C. It's a good idea. Okay. So, when we come back, let's do that. We'll make a thing. I'm going to leave this on the screen. Uh, I'm actually going to go ahead and shut down the uh shut down the server really quick. There's somebody else. I don't I'm not going to raid because I I can't talk to anybody. All right, see you guys later. I'll be back in I don't

Preparing content for Beginner Boost focused on getting a Tech Career. #techjobs #livestream #coworking