day in the life of a software engineer | 5 hour productivity | debugging with my junior

A recorded coding session and day-in-the-life vlog by Phil Choi (with junior developer Jocelyn) focused on wiring a React Native frontend to an existing backend for a skills-matching app. They discuss app structure (admin panel, backend endpoints, frontend), debugging live (fixing findMatches/fetchUsers, handling missing user images), tooling choices (using Yarn for React Native CLI vs npm), and implementing protection for server endpoints using JWT authentication and later CORS restrictions. The session mixes practical setup work, mentorship, and meeting logistics (follow-up sprint planning).
Chapters
Fit check right here. Dude. My. My intern's ready for my concert. Dude. Here we're gonna do our first like scrum. So now inside of this auth stack we can do import initial screen. All right, so if you guys pull main, it should all be there. I think Jocelyn and I will be back in like an hour and a half or so. We'll talk about the design and we'll do another sprint planning on Friday. Is it okay? All right, so I know the setting up is taking a long time. Let's just do everything carefully. All right, later. All right.
Seriously.
I'm going to have some food real quick. Really? Yeah. Everyone's starting their own channel inspiration. Dude. I know. If I can do it, you can do it too.
Yeah, I know. Dude, that was definitely more than a four minute break.
I know, I'm sorry. I think we need to go back. This looks like a dating app now. We need to kind of hook up the back end to the front end. Right. So with Jocelyn, we've been working on the project. There's three pieces. We worked on the admin panel in the back end first and the front end line. And then we went back to the back end to fill out some end points. So like you have to have like a skill you want and a skill you can provide. And then we made some kind of matching where you can only look at people that need your skill and you can provide that skill. So now we hook that up so we can see all that. But now we need to hook up like the part where you can like request and then respond to the request. We already did that in the back end so we have to hook that up. Sh. Hey, what do you think of the app so far? It's a lot more work than Expo. Right? Because Expo, you have all the navigation and everything set up, but actually setting it up from scratch is.
Yeah, it is. I actually, I was wondering why you're using Yarn instead of npm.
A lot of the documentation for React native, they like suggest using Yarn, so I just use Yarn because it. I don't know, it has a little bit better performance too. A lot of React native documentation on the cli side of what we're using is using Yarn. Yeah, I'll like walk you through, but right now is not like the really fun part. I guess it's like the more setting up part. I mean that's a. That's a big learning experience anyways. Yeah, I was, I was like so frustrated with that bug for a second. Minnie said, I get mean, like I just stopped caring about what people are saying.
Don't talk to me. I'm trying to do something here.
Yeah, let's share your screen and give me a live share in the back end when you log in. Right? Hold on users, we don't need the front, right? We're going to work on the front end today, right? Because last time we got to the respond respond. So I want to get that step done on the front end today and then we'll call it a day. Can you try to add skill provided to someone and then they can. We should probably put a limit of how many skills they can add. You know what I mean? But now can you go to add skill provided. That's the one right underneath the put request. Now we got to do the same thing with add skill wanted. Can you get, can you take a crack at it right now?
Yeah.
So this is adding like put protection to our server, right? Like without this token, without you know, logging in, you cannot use our server. This seems to be a lot more safe and like it protects the server. If so like if someone doesn't know the token or you know, if someone has not hit the login user before, right? And they have to, you know what I mean? They can never use our server because our servers needs to be authenticated, right? That's like our, our scheme, like our protection scheme. Like the server's job should be to like you know, protect the database, right? And communicate with the database. So we need some kind of layer of protection, right? And later on we can install like cores and make sure only like our domain is able to hit the server. You know what I mean? Like a whole bunch of these things. So now what do we have to do here? Cool. Didn't they just press edit?
No JWT user.
Oh nice. JWT Nice, nice, nice. Now we just have to intercept the request. I'm happy with what we're doing now. So the JWT log has the log, right? Ey, okay, can we just make a export find matches. So now inside of this fetch users function instead of using this function, right we're going to do like this. I'm trying to get into that mode. Gen Z mode like bet no cap no cap Bet no cap Refresh. It's going to be on God. On God. Living rent free. Crap, I can't even do it. Dude.
It's all America.
Nobody else has like you this code. Living rent free in my head. No cap is lit Skibidy. This user that I'm seeing is skibidy Riz toilet I'm good. Right?
I know what riz means.
Dude, you sound like a. Like a grandma here. Like, we're saying, like, all these, like, slang words, and you're like, well, I know what riz like. Like, everyone's like, saying like, oh, why? Why W, Y, D. Oh, yeah, like, oh, R, L. And then you come in, you're like, oh, I know what lol. Can you take the. The login user and then go to find matches, add in the token inside of find matches, and then remove the user ID from the end of the endpoint?
Oh, what? The user not found.
User not found. How is the user not found all of a sudden? Oh, sorry. Find matches. Oh, my bad, my bad. I know where it's going wrong. Ctx meta user id. There you go. My bad, my bad. So you see some users in here, right? I want you to, like, use that data to create, like, a card. I know you don't have a picture right now, but what I want you to do, inside of chat, GPT or whatever, image loader, you have logo thing. I want you to make, like, a skill sphere logo. Like. Okay, and then. And if they don't have an image, because we do have a picture, that's null right now, right?
Yes, we do.
So if they don't have a picture, I want you to display the. The logo as their.
The default.
The default photo.
Okay.
Is that okay? And then just work on this page a little bit, and then let's check back in tomorrow. I'm quite booked. But Friday morning, we're gonna meet, like, booty and song, you and me. So let's meet up then and let's see what we can do. Is that okay? Yeah.
What time on Friday? Which is my Thursday. Bye. See you guys.
You can do like. We can do like this. Watch this. Watch this. Watch. Wait. Watch this. Wait, watch this.
Put his song on.
Wait, Nikki. Like this.
Oh, it's closed. A little bit closer. J. The other way.
No, the other way.
Like a.
No, no, no. That was the right way. You got to. You got to bring. Pull your hand back.
Yeah, keep going, keep going, keep going.
Okay, perfect. Stay. Stay there.
Stay there.
Yep.
Okay, Phil, you have to move back or you have to go closer now.
There you go. Damn. Look at that.
That's so much effort.
That is a lot of effort, dude. All right, all right. Later. Oh, that was so hard. All right, all right, all right, all right. Take care. All right, later.
More from Phil

day in the life of a software engineer | 5 hour productivity | building my dev agency 🔥

day in the life of a software engineer | 3 hour productivity | coding my 6-figure community startup

day in the life of a software engineer | 5 hour productivity | coding our sns startup app LFG

day in the life of a software engineer | 5 hour productivity | creating apps that makes big money






