 In this video, I'm going to show you not to screw up on your first week on a programming job. You reached the right video. Let me explain. This video was brought to you by DigiLink Academy, your number one source to learn programming fast and get to that six-figure salary you desire. Our academy have a wide range of courses, including our 30-day developer lunch pad, our programmer interview course, also our mentorship program and much, much more. When you sign up for our free community, you get access to like-minded professional developers who want to take your career to the next level and will provide you with access to all the resources that our academy can provide. So let's take the next step and sign up for our seven-step free programming guide to really start to take your career to the next level. So let's click the link below to get started. I'll see you guys in the guide. All right, guys. I want to give you some details on your first week of programming. A lot of you guys trying to get ready to start learning how to program and you're getting your first job. You just want to have a better understanding of what to expect your first week or you just don't want to screw up and cause people to, or cause you to lose your job and now you're back at square one and give you some reasons, well, some things you can do to really make this process, this experience a whole lot better for you and to really put yourself in a position. I made some notes here so everything will go good and then we can kind of go from there. So guys, let me tell you a story. First of all, when I first start programming, I used to come in and just think, Hey, I can solve every project. I can solve every project. I'm going to be that person. Y'all need to be successful, needy, needy, needy, needy, needy, needy. Don't do that guys because at the end of the day, you want to go with the flow. You want to just fit in and just go with the flow. Normally when you first come in that week, you're going to have your hiring manager or somebody on your team kind of giving you the general consensus of everything and really putting things in perspective for you. So as you gather this information, if they actually do something specifically, then yeah, and then go from there. Don't volunteer yourself for stuff too much. This could lead down a path that we'll talk about in a later video, but you want to just take it all in first and just really kind of fit in. Lay it be laid back, but helpful at the same time. Find that really good balance guys. It's nothing like a needy person coming in, trying to take over the whole department saying, I can do this, I can do this, I can do this. Either one, you're going to find that team member who's going to take advantage of you or number two, you're going to alienate everybody. Because they're going to think you kind of come in and check their job. A good balance is somewhere in the middle to where they know, Hey, if they really need you, they'll come at you, come and get it from you. But they don't want to just take advantage of you too. So guys, it's very important that you guys kind of have that in perspective in your first week as a SQL developer and really put things in perspective for you. So number one guys, day one. Day one is probably going to be a ton and ton and ton of paperwork. HR department. This is who you're going to probably see most of your day one. When you are working with the HR department, tons of paperwork, tons of questions. Some people do questionnaires. Some people do your health stuff, as far as social security numbers, all that. So day one, bring your social security cards and identify the information. You should have your driver's license, your birth certificate, any records that you have that you think you may need, social security card, birth certificate, even your spouse information so that you can already have that stuff on site. Most of the time they get you to bring it home and you can fill it out at the house, but, you know, just have the information on you that day, just so that they at least they can get their copies and all that stuff. And you'll be good to go. And another side of probably the second half of day one, introduction to your coworkers. You're going to be around these people, hopefully for the long term. And, you know, you're going to be in the restroom or the break room and they're going to see a new person around. You're going to be getting some introductions, people from your department, people from other departments. So this is mostly what you're going to be getting into your day one. If you're working for a good company, they just do a general introduction with everybody to just take you around. And whoever's there, hey, this is Rod. He's our new developer. He's going to be helping you guys out. Hey, hey, hey, you're not going to remember half of the names, which is okay. You know, just put a good face with a name so that if you guys see them or they see in a break room, they don't, they don't know if you're a complete strain. They know you're the new guy. So that's probably what you're going to be doing day one. So let's fast forward to day two guys. Day two is actually where you're going to start getting into some, what, of some computer coding stuff. You're going to actually get access to the system and also discover your team workflow. So just say, for example, you're going to get access to ticketing system. They're going to have your AD account, email accounts, give you access to the test environment, things like that. So you can start to really figure out which tools they use and kind of get a chance to at least generally look around to kind of assess what everything they have that you can work with. Workflow is critical guys, especially with your team. And I'll get into this in a later point, but it's good to have that general understanding of what tools we have to work with and really kind of put things in perspective for you. So kind of be aware of that. Day two is, I would suggest you in day two, just to kind of, it's more of a discovery day. And you're going to over, you're going to be looking over somebody's shoulder, probably, especially if you're a junior developer, even if you're a senior developer, you're probably going to be working with somebody there to say they're going to be, you're going to be over looking over their shoulder saying, do this, do this, do this. Hey, could you do this little part of it? And then kind of work from there. So you're going to be primarily working with somebody else. I talk about this in my seven step guide. So go ahead and pick this up guys. When you start to get into the real world situations and other characteristics of a developer, it's important that you guys know this because you have proven that you know how you've learned a level of code that they're comfortable with. You got through the job prep. And now, since you got to start to advance your career, other characteristics are going to come into play. We talk about that in my seven step guide. So get that. And if you haven't, if you already have signed up for my seven step guide, check out the premium courses guys. I got a 30 day lunch bag course that's going to help you take your career to the next level. So day three, we're sitting in here where we're coming in, day three is actually going to be the day that they let you kind of have a little bit of independence. This is the day that you two days in, they got a chance, the introductions you met probably most of your actual IT team members. Now it's time to actually get into the ticketing system. This is where if they have a good ticketing system, this is where you can kind of get a general idea of what's coming in as far as just requests. And then you can kind of mentally know, hey, I need to learn more about this or I need to learn less about this and kind of have a general idea of the actual flow. This is also where you can start looking at the project management system. Hey, what tasks they have out there, whatever they're doing, what type of projects they're currently working on, what have they worked on in the past. You should have access to search current projects, past projects, and sometimes they do future projects. It's pinned on the company, but you know, future projects, you're not going to have a ton of information out there, but you should have a general idea of what's coming, at least on a project based as far as tasks guys. So this is very critical this day because this is the day where you start to split the high value developers and the low value developers because low value developers are just going to sit there and just get their current tickets and wait on somebody to feed them work. And then they kind of go from there. High value developers going to assess the situation, going to really figure out, okay, they get X amount of tickets. I think I'll be working on this, but we'll see. And I'll just be proactively learning this because I see they get at least eight tickets on this every week. So it's a high chance I'll be working on this. This West separates the high and high value developers from low end developers guys. This day three right here is going to be critical in the same with the project management system guys. And you're going to start getting to smaller tickets to just solving small things. Maybe, hey, I need, I need this column added to a report. Or, hey, I need access to the test environment. Could you check this door procedure just to make sure these lines of codes not fell and could you go through that little stuff like that net and major just something just to kind of get your feet wet and make sure you're comfortable moving around in the tools and the ticketing system and the project management system. Number four, this is where it's going to be a people day. You're going to learn through your ticketing system. They assign certain tickets to certain people. So you're going to be like, okay, he's the web developer. He's the sequel developers. These are technicians over here. This is the boss. You don't assign him anything, unless it's just something from a contractual's perspective. This weird guy over here don't do anything. So don't assign him anything because he got 12 tickets. This is where day four is going to be the people. And also, as you can do in these tickets, you're going to notice that you're going to have a requester on these two. These are typically your end user who either submit the ticket or it's going to be the stakeholder on the project. So you got to get to know these people. And that's the good thing about IT. You're going to, over time, you're going to work with a lot of people if you are a high-vary developer. So it's good to know who's the key power users are. What we call them in most companies, that's going to be helping you move your projects forward. Day five, guys, just have a really good understanding of the entire workflow of your team, your company roles, the key areas, just having a good general understanding of the actual workflow in general. I think that's a good successful week one for somebody. So we, too, come in. It's no, hey, let me learn how to get into the system. Let me, it's going to be more specific as you go, as you work on specific projects and specific tickets. And over time, you're not going to learn everything about everybody, but you should have a general understanding. Let me start here first and then go from there. Or let me start there. You shouldn't be in a dark at this point. You should be able to identify where you need to go and all that good stuff, guys. So at the end of the day, guys, don't try too hard. Don't be that person who come in and just trying to, well, first of all, don't don't operate in the extremes. Don't be the lazy person who don't want to do shit. But you want to do the you want to be the person who you don't want to be the person who come in and just let me help them help them help you don't want to be on the extreme. So that's why I mean about that. Find a good middle ground. Be laid back. The work's going to come to you through the tickling system or through somebody just needs some general help. So like, subscribe to the content. If you guys agree with me, comment below. If you disagree with me, comment below. Let's start a conversation. If you haven't already, go check out my premium courses, that 30 day lunch pad course, guys. Go get that. Take your career to the next level and I'll put a link right here for my seven step free guide. If you haven't got that already, I'll see you guys in the courses. Peace.