day in the life of a software engineer | 4 hour productivity | uncooking CS degree students

Wow. >> Turbonus. >> Turbo. >> That's what it's called. >> Yeah. It's actually pretty cold today. I hope so. >> Not much, dude. I went to sleep early last night, dude. >> Yeah. Okay. >> Oh, I I overpacked my morning, dude. >> Cuz I got a meeting like right now. >> Yeah. >> And then I have another meeting. >> And then I have another one. And then I had another >> I accidentally overpacked it, dude. Yes, I need you guys to test the payment and signing in and uh Facebook one Facebook login. Uh it's still getting approved, but just please wait a little bit more. Oh, no, no. I'm I'm going to Egypt to drop my kid off. I was going to drive him. Couldn't He said he want to walk. And then the brand pages. Is the brand page done? Yeah. And then that that's a that's Yeah. That's a that's a completed payment, right? And it's just unfulfilled. Yeah. Okay. Cool. Cool. Who uh who tested that by chance? I think uniform picture sizes is pretty important. Like pretty important task to make the job whole job easier cuz before they make the inventory list, they should have the pictures all >> that's uh that's my kid's best friend's mom. >> Oh, really? >> Yeah. We hung out yesterday. >> God damn, hectic morning. But we got uh one of our mentees doing the one of the big projects here for us. Uh we're really proud of him. Got Julian. Special uh congrats to Julian, one of our mentee who just landed a job this morning. Congrats to you. And um yeah, just things are moving, things are popping off. And um so expect more things. Yeah, just if you guys don't want to know more about the mentorship or the link is in the descriptions below. Thank you guys for uh tuning in. Anyways, let's get started. >> Mataz is on his way today. >> Yeah. You really not going to come to the ribs today, dude? >> Wait, are we're going right after, right? >> Yeah, right after. You should come. >> And but we're No rice, bro. >> Who eats rice, bro? We're too >> No, dude. No rice, bro. >> Even even if I smell rice, it's adds to my body. Oh, dude, you're at that level, dude. >> I think so. >> Oh, man. Dude, >> I I do miss rice, dog. >> I miss rice, too. >> Three weeks only. >> Oh my god. You know, Julian, you know, he was like one of the only one-on- ones I accepted over the my trip to Hawaii. >> I remember getting to my Airbnb. >> Yeah. And I was like, I got I got to talk to him for a second. And uh you know, he was he he built a bunch of stuff. He built some like interview helper. He built um you know, a bunch of stuff. He helped me with a couple stuff things. And uh now he has a job, full-time job. We, you know, we helped him try to get some other interviews and stuff, >> but uh you know. >> All right. age-old question, dude. >> You already know, dude. >> All right. All right. Hot one or a cold one. >> That's right. Comment below. >> Got like 20 likes right off the gate. >> That's what's up. >> I think I empowered like everyone, you know. >> That's That's what it's like, dude. All right, dude. Well, a lot of things going on. >> You can overpack your morning sometimes. >> It's okay. You just have to uh get it done. Um I think like there's a feeling of like overwhelmed [ __ ] like when you have too many tickets when you're coding or whatever, but Just I think if you're focused on one task that you have and then you try to get to the next one the next one, you're making some kind of progress. >> Yeah. >> So even if you feel overwhelmed, break it down. >> Yeah. >> Do the one task at one time and uh get it done. You know what I mean? Say I have like five meetings in the morning. >> I can't do all five meetings at once. Stupid. Just one by one get them done, you know? >> Mhm. >> That's uh that's life, dude. That's life. And that's what coding really helps you do I think like um like it's rather than saying hey I got to build this whole app right >> hey I got to build this one module I got to build this >> flexible component I got to build this socket module I got to build you know like yesterday I told Gina right like we're on like a one-on-one the only way you're going to kind of get your uh knowledge up and you're you know is like doing things that you haven't done before sure like there's system design and stuff like you have to do right like you have to learn about load balancing you have to learn about API gateway whatever >> and then you stick all those together and then you can build something with all the knowledge >> but then before you get there you need to get like >> people find other things interesting like yesterday we made a screen share app >> okay >> like uh you know like using the record screen recorder API and then um sending it through a socket through B 64 and then showing it on the other side showing about frames per second and [ __ ] you And it's at first what you don't know it's scary to look that [ __ ] up even >> cuz you start going into a rabbit hole. And I know every single programmer has had the 100 tabs open on a Google Chrome trying to figure something out. >> Yeah. >> But uh I think once you get past that 100 tabs or whatever like you learn how to read the documentation, you get a good documentation, a good tutorial or something. It's all about leveling up, dude. And uh same with anything in life, dude. I don't know how to raise a kid, dude. Doing it every day. Uh >> freestyling it, dude. >> My name is Phil. I wrote my first line of code after the age of 30. If you have any comment about how you're leveling up right now as we speak, let me know in the comments and uh we can figure out how we can help each other. And uh you know, like, comment, share. Really helps the algorithm. Uh subscribe, too. And remember, if I can do it, you can do it, too. Coding saves lives. >> Awesome. Robert. Hey. Sorry. Hey, Bill. >> Hey. How are you? I was so uh sorry I'm a little late. >> How are you? >> I'm all right. So, is it your break time right now? >> No worries. Uh yeah. No, it's uh uh not really a break time. I just have free time right now. So, um >> so this is the Docker desktop, right? And in the top in the top right corner, like uh in the task, uh do you see the whale running right there? That means docker desktop is running, right? So now if we run it, it's going to uh start. >> Oh. Oh my goodness. >> But uh I'm wondering why your um your uh import m config m schema from validation m validation. Why is that a red line right now? is >> so I think that one is because I don't have in front of my in this file name. Go ahead and rename that to that env.idation. Does that fix it? No. >> Well, uh sometimes um just delete it and then retry to type it. >> Okay. Uh >> slash >> validation >> slash >> slash. >> There you go. >> There we go. >> All right. >> Nice. >> All right. So this is uh this is um uploading m um instance of error. So your error does not have errors in the uh code, right? Sometimes like when you when you uh log error, it comes in this object object >> and I think you've seen that before, right? Oh, >> so that's that's why that's why I turn it into two strings. So then it forces it >> so I can actually see the error. That's >> so that's how you fix that. >> Yeah. >> So those are just small little things. Um >> and like cuz usually like on a back end I mean in this instance right here I think error just would work right. But usually at at this point right here instead of just console. error, you're probably going to do something like throw new error error or something like that. And then inside of the error object, you want to take it back to the client and then the client should be able to see it, right? But if you just send error to the client, it's going to be error object object. So the reason why you unpack it to a string is so you can actually kind of start debugging and seeing what that is. >> I see. I see. Okay. >> Okay. That makes that makes sense. Oh, and I I guess like at this point it doesn't matter because this is not not a REST API or anything, but um just get in the habit of it, I guess. So, even if you moved it from location on your computer, it's not really changing anything here, right? >> Oh, yes. Yes. Yeah, I I see that. >> Yeah. Beers. >> But there's Oh, I know. >> Have you heard of uh what is this? The the the Balmer effect. Can you refresh my memory? Yeah. Steve Balmer. >> Steve Balmer. He was the Microsoft CEO, but he, you know, he's known for that one crazy uh thing that he did. He was like sweating profusely on the stage and saying like we need more developers, developers, developers, developers. So they say like um Balmer's Peak is like when you get drunk and you get like overly confident so you just start writing a bunch of code and uh that's called a Balmer's Peak. Oh my goodness. >> Yeah. >> Uh this one like I would just say like sparkles or um you know uh whatever um config. So the way you can do that is um let's just say sparkles and then and then you can say like added configuration files added configuration file for uh for validation and then that would be your that would be your message. Maybe we can just do like this import model from mongus and then maybe we just say model any. Does that work? Okay. Any type this and later on we'll list all the other types here. But what I like to do is I like to do an export default as stocks schema from stock. Oh crap. stock model. Stock.model. Do we have an export default here? And then we just turn it async real quick. And then um each one inside of here, we can do a request. It's going to be the request and the response like this. And then um and we'll just do try catch throw new error method not implemented and then oops and then at the tries we'll do a res send um implement feature. Okay, >> nice. >> So now we have the create list get by ID and then now all we need to do is um let's just say that we need the uh users controller.ts, right? >> Mhm. >> And I here let me actually call this because I think you're capitalizing your first things, right? That's how you want to do it. And then let me just type in model any right here. We'll fix that type later. And then now we can do a res.json on docs if we needed to. And then now let's um let's uh let's try to go to the browser and go to that refresh. So now you have that coming in, right? But you need to design this you need to design this a lot better, right? >> So >> yeah, >> each one needs like pageionation >> and then the API doesn't need just this, right? It needs to you need like a API template or something. So you need to do like uh const total equals like docs.length, right? And then you need to do something like uh const return uh maybe like um I don't know maybe you could do like a res uh status on 200 and then you can do a JSON and then you can do something like the data that comes back is the docs. The total is the total and then um you can add like page um later on you we'll implement this later on um and then you can like page size is going to be like whatever your page size is let's just whatever it is I don't know but uh we'll figure that out later and then now like can you try to refresh the page >> yes >> so now it this looks like an API now right like you have maybe data you maybe you have some kind of message you have total then you have page and then maybe you'll have something like page size and and then you'd have to create this kind of thing now right so >> later on we need to create like that create um uh let's say something like const as much free time as I I have I want to like spend and complete this thing with you so uh let's uh let's get it done and uh hopefully you had fun today. I had fun. Um >> I had a lot of fun. >> All right, cool. I have to get to the next meeting, but um I will take a screenshot real quick and uh is it okay? >> Absolutely. >> Okay. One, two, three. All right. And I'll see you uh very soon. Is that all right? >> All right. All right. >> Yeah, absolutely. Thank you so much, Phil. >> All right. Later, Robert. Hello, everyone. >> Hey, Cash. >> Hey, how are you? >> You want to get Sandy on there, too? >> I'm doing great. I'm going to I'm going to stick servo repo init into the um into doing and then we're going to do init typescript node server and then we're going to do uh we're going to do these two things uh so far. So let's just keep our uh the task like very um streamlined. So let's >> Oh yeah, let's not think about anything else except servo repo initcript node.js server. Is that okay? Uh Ray, >> that's perfect. Okay, I'm sorry I muted. I am muted. >> Okay. Um okay, let's uh can you um start a GitHub repository users.outs.ts and then I'll do import router from express con router equals router. I'll also now I'll import. Oh, I haven't made that yet. Okay. So what I need to do is I need to do redder use the part projects and I'll have users right. So everything's set up here and then I'll just go back to this board. I know I went super fast at the end. Um light rate can you try to do the company's project request notifications email and chat rooms. Is it okay >> right now? >> No, no, no. Like uh over the week. >> Yeah. >> I was like oh my no I can do those. Yeah pretty good. I was like so focused on it. I was like, "Oh, that's how you do that. That's how that works." It was just clicking for me. >> Okay. >> I was I was mo I mostly came from front end. That's fine. >> Oh, but uh I think um you know, if we set it up, it's like a lot of just copy paste and you can kind of like use the code. Yeah, I've noticed it's kind of like uh you copy it for the users, one for the client side, and then >> sorry, client is users, but then like one for other people that are logging in as something else. Who knows? >> Yeah. Yeah. >> Like, oh, cool. That's how that works. >> I mean, minus. >> This is how you separate the like the admins from the clients from just like people who are watching, right? >> Yeah, exactly. And uh you know now we have like the whole like uh like system that we're going to set in place like we have the models that get used by the controllers and then the routes that or the controllers that get used by the routes >> and then it all gets connected. So it creates this like whole like MVC thing how you write code in the beginning. I think uh in the beginning it gets a little bit hard um but later on the systems are in place to keep it very easy >> to add onto another feature or the route like right now I don't need to like touch all the files anymore I just need to create new files and it'll like integrate into the system >> and uh I think that's important and um yeah I'll see you guys in the next one and uh >> thank you guys. >> Okay, >> same time next week. >> Same time next week guys. I'll see you guys next time. and Ray. Uh, message me anytime. I'm I'm always here. >> Okay. >> I will get to talk, so I will. >> Okay. All right. Thank you. >> All right. Later on, guys. >> Later. >> Bye. >> All right, dude. Finished up. Uh, I I think I sped run like the last part, so I feel a little bit bad, >> but uh it's all good. Um, I just have to look through the code and get it done. But, um, I code the same way like all all my projects. So, uh, yeah. Hopefully it was not too hard. But >> anyways, uh Light Light Ray is doing well. Robert's doing well. Um Gina's doing well. >> Um Dong is doing well. >> Yeah. >> And uh you know, we're doing the coding academy like uh we're building projects out there. >> Um we're also doing the mentorship. Yeah. >> Uh if you need more one-on-one or like more hands-on assistance, >> but um you know like uh the help is like right around the corner, you know, >> and um just uh reach out and uh >> it's all you need to do. >> Yep. >> All right. >> Thank you. >> Coding saves lives. >> Yeah, that's right. side.

🤝 Discover how to make $8,000 a month in tech: https://letphil.com/ 🌐 Let Phil's FREE Community Discord Channel: https://discord.gg/RBhnbd3kxv 📸 Follow my Instagram: https://www.instagram.com/letphil.code/