Aug. 15, 2022

Mistakes That Prevent Self-taught Developers From Landing A Job

If you are struggling as a self-taught developer or just want to increase the chances that you'll land a developer job with this path, this podcast episode is for you. Unfortunately, most self-taught developers give up before ever landing their first position. In this episode, I'm going to dive into some of the main mistakes people make while going down this path and how to avoid them. By the end of this, you'll have strategies that'll greatly increase your chances of success as a self-taught developer.


🤝  Join our junior friendly developer community:

🔥  Want more personalized help from me? Here are the paid mentorship and review services I offer:

❤️  If you find my content helpful, please consider supporting me by becoming a channel member and get access to additional perks. Every little contribution helps and is actually used to pay my bills.


Disclosure: Some of the links below are affiliate links. This means that, at zero cost to you, I will earn an affiliate commission if you click through the link and finalize a purchase.

📚  Web development books and other products I recommend:

The Master Delegator Podcast
Learn how to delegate effectively and become the CEO of your business not an employee!

Listen on: Apple Podcasts   Spotify


Don Hansen:

If you are an aspiring developer and you are about to embark on the journey of becoming. A web developer or you're just flat out stuck. Right? You're really discouraged for the self-taught path. You don't have a lot of confidence. You don't feel like you're making progress. You can't find a job. This podcast episode is for you this episode, I'm gonna talk about some of the main mistakes I see aspiring developers make I've mentored thousands of aspiring developers and helped hundreds get jobs. And it's a very, very tricky path to go down and it's a very affordable path. Right. And I wanna make sure that I give you as much advice as possible to make it work. So let's go ahead and dive into it. Um, a lot of aspiring developers start out with false expectations. They watch the Tove video telling them that they're gonna get a developer position within three months, right. No problem. And what happens when they don't get it within three months? Okay. Maybe it's taken me a little bit longer. uh, oh, we're at the six month mark, right? Is it me? Am I not smart enough to become a developer? Why is it taking me so long? Well shit. Now I'm running outta money. I financially planned. I might have quit my job or I financially planned or planned my family around getting a job within six months is not happening now. I'm getting pressure from other people right now. I'm getting financial pressure in my own situation. Um, And, you know, at least if I saw progress and I felt like I was trying to get a job, I could finally get that position. Like I, I would have that motivation. Right. I could explain to my family, my friends what's going on. Um, but I don't even feel like I'm making progress cuz no employers are calling me back. Right. I'm telling you this experience. It's really common and it might vary based on your situation, but a lot of people start out with really false expectations with really, really bad advice that you're gonna get a job and learn a hundred K job, um, as a developer in three months, like that's ridiculous. You talk to any experienced software engineers. They're gonna say that's bullshit, right? Obviously they're gonna be exceptions to the rule, but 99.9% of people are not gonna land it that quickly with that much money, it's not gonna happen. Right. a lot of people start out with that unrealistic expectation. It's gonna take a while. I know you're not gonna wanna hear this, but I tell people if you're going to self-taught path and you're doing it full time, give yourself at least two years of a financial backing to be able to do that. That's huge, right. Two years is a long time. We have to realize a self top path. Isn't very linear. It's just not right. That's what a coding bootcamp or even traditional education will help make that a little bit more linear. And those aren't perfect either. And they cost a lot of money and maybe they're not worth that money to you. And. But you have to expect you're gonna be all over the place and you're going to doubt yourself. And you're going to all of a sudden have to refresh on fundamentals cuz you forgot these fundamentals and you haven't used them in a while. And then it makes you feel frustrated because you're not reinforcing these. So I wanna talk about some things to really help reinforce this knowledge and try to make that path more linear. But number. Key thing. A lot of self-taught developers make, uh, or the mistake that they make is having those false expectations from the beginning. And that just might mean you had those false expectations. Now let's build some more realistic expectations and a lot of people self-taught right. Um, maybe you just kind of do self-taught because you want it self-paced, you're willing to pay a little bit of money, but like you got work, right. You have family responsibilities. So, um, it might take a little bit longer. That's okay. and in fact, when you can go at this path and give yourself a little bit of time and patience, You give your brain more room to let things sink in and get reinforced. Um, you know, one flaw of a coding bootcamp. It it's pro and it's con is the intensity of it, of a full-time program. Like you're learning so much knowledge. It's like drinking from a fire hose. And if you can give yourself a little bit of leeway to learn things at a, um, a slower pace, you can take the con out of that and essentially learn all that information O and just spread it. Over time. And that can definitely help you reinforce a lot of the concepts. You, you can't cram the stuff in you. Can't. I had someone that wanted to study for 14 hours a day from the military, right. He's military. He has a self-discipline to do it, but I'm like. You know, dude, you gotta, you gotta take a little bit of a break. Um, it's not gonna it's you can't cram this information in software engineering is weird. It's not like our traditional education where we just cram before a test, we take the test and we passed or we don't. Right. Or we get an, a, B, C, like software engineering. Isn't like that. You have to build, you have to get your hands dirty. It's not a linear path all the time. And like, you're gonna go back to the material. Then go back to building projects, send the material, then building projects, and you have to. Give yourself time for these concepts to solidify and implement them in more complex projects. That's how a lot of this is going to get reinforced again, be patient with yourself, give yourself time that false expectation. A lot of developers give up because of that. So you watch any TikTok, YouTube videos that say yeah, three months, a hundred K stop watching that creator. I promise you stop watching that creator. So. A lot of people when they do dive into the curriculum, a big complaint is, um, I don't feel like I can build anything. Right. So you go through a course, but, uh, they're like, I don't feel like I can build anything. Well, like what does that mean? Have you tried building something what happened? Right. And so, but what it usually comes down to is they go through the course, the course makes them feel like they're progressing. And they're learning things and remembering things, cuz they're getting, you know, they're passing the challenges on the course, et cetera. And so that's why they keep going forward with the course. But then when they try to build something, their mind goes blank. And how do I do this? And oh, maybe I do have an idea. Maybe I wanna build a calculator. I have all these concepts on my mind, but I don't know how to bring them all together. A lot of times people spend way too much time in the courses, even in the beginning, this is a really weird. Concept to understand, but even as a beginner, as a beginner, aspiring developer, you have to get your hands dirty. You gotta build almost right away when you take your mind and yourself and you put it into a different context. And let's say you try to build something slightly different. You tweak what that challenge was in your course. that's going to help reinforce the concept, just using that concept, implementing it in a slightly different way. Outside of the course is something that is crucial and so many aspiring self-taught developers do not do this. They get stuck in what's called tutorial hell, because they're just, they go through a course it's rated high and it makes them feel like they're learning stuff. And then all of a sudden they don't know how to build anything. They don't know how to apply that. Apply it early. You get them with a little module you code on the side. I'm gonna say is like, as many times as I need to say this, but this is crucial. Get your hands dirty. As often as possible, get outta the course, build something small, something slightly different, changing in a little bit of a different way. Um, or even think about a project you wanna build. Maybe you take that course and you think about like, okay, maybe at the end of this course, I could. This kind of, or this is the kind of project that I want to build. How could I use these concepts to start building pieces of this project? And as you learn how to code, as you learn more complex concepts and how everything integrates together, you start getting, you start forming this knowledge of how, um, you start, you're able to piece together this project in your mind, you're able to conceptualize. More, as you learn a lot more fundamentals too, right? So maybe you don't have to jump into that big project right away and build pieces, but keep it in the back of your mind, because like start trying to figure out how you can build little components, little parts of that project, because if you can take what you're learning those fundamentals and you can apply it to an actual practical project, that's huge. That's really gonna help you reinforce a lot of what you're learning. Don't get stuck in tutorial. Hell I don't know how many self-talk developers are stuck here. I it's, it's a huge number. it's a huge number. It's super common and it's so easy not to get stuck. . And so if you are someone that's been going through courses and then you can't apply it to projects, try it. You can start at any point in your learning journey. And sometimes that might mean going back to some of the fundamental stuff and then building some fundamental features, right. Or identifying, you could even go to websites that use on a daily basis and identifying how they're making certain elements appear in that way, on that page, based on what you learn, right? The trick is get out of your courses. Put it into the real world, put it into practical projects. That's gonna help you escape. Tutorial. Hell it's so, so crucial. Now another thing that holds up self-taught developers is motivation. Motivation to stay consistent. It's a long journey. I get it. Your motivation is going to die. You are not going to be consistent with that motivation. You are going to wake up one day feeling like you're just spinning your wheels, not making any progress. You set your schedule. I'm gonna code a little bit this morning, or I'm gonna, you know, take, do this module in my course this morning, then I'm gonna go ahead and code in a project. Um, and tr I'm gonna try to build it, reinforce it and things just aren't clicking, or you just you're like, fuck this day, I. I really don't wanna do this and guess what you do, you fucking do it. Fuck your motivation. There is no way any developer becomes a professional developer and takes that long journey and stays motivated the whole time. That's complete bullshit. That motivation will waiver. It don't believe anyone that tells you otherwise that motivation will waiver. It'll go high. It'll go low. Do not depend on that motivation, what you do depend. Is consistency. When you set your schedule, try to be a little bit. I always recommend like, first of all, a lot of people don't like schedules. They don't like putting things on their calendar. I didn't either, until it started giving me results. I, I, I, there's no way I can even see myself navigating through life without a calendar and a schedule on a to-do list. It's like, it, it has changed my life entirely. I'm telling you it is, it can really make the difference between someone that is, uh, going to build like consistent habits and a structure to actually get that job. And someone that's just all over the place. Scattered. I don't know what the fuck to do. Focus on a schedule, focus on your to-do list. Plan something and then try to do it. Even if you fail at it, if you feel like, if you don't feel like coding that morning, wake up and do it anyways. And maybe that means like I had a horrible day, you get to your schedule, then the next day, what you plan is, okay. You know what, maybe I'm feeling like I don't really have a lot of direction. How do I fix that? How do I talk to someone that can help provide that direction and that structure, right. We can get into that a little bit later. Um, But it's, it's incredibly important that you just set a schedule. Like if it's Monday, Wednesday, Friday, two hours. Right? Um, my, my wife's willing to take the kids when I get home from work or something like that and just get 'em outta my hair. So I can code, um, if, if talk to your family members to be able to have that set schedule, to, to code and do what you need to. do that for as long as possible. And then try to get more efficient with how you used your time during those two hours. And you could change your schedule. But the point is don't just go in, wake up. I'm gonna code a bunch. I'm super motivated today. Eight hours, 10 hours. I'm blowing through this course. First of all, like when you go through a course course should be like maybe two hours of your time. And then project work is like eight hours. If you had to do like an eight hour day or something like that. And you're just learning to code, I'm telling you, you don't spend a lot of time in courses. You spend a lot of time practicing getting your hands dirty, reinforcing the implementation. But that motivation will wan it's. Okay. It doesn't mean this position, this type of career isn't meant for you. I promise you. That's not what it means. It might mean maybe you're low on energy. Like people don't think about this. Maybe you don't work out enough, working out, especially cardio will give you energy. Good diet of water. Um, not loading yourself with caffeine and then just crashing at the end of the day, like, or the middle of the day often, uh, getting a good night's sleep, making sure things are in order. And like I said, talking with family and making sure that you can have some sort of quiet time and try to get that quiet time to be able to focus. It's tough. It's a really tough path, a self-taught path. It's okay. A lot of people struggle with it and a lot of people get jobs with it as well. The REA, like I said, the reason self-taught developers, most of them don't get jobs is because they give up. That's it they're, it's not like they're not smart enough, but I really think, I really think it'll help to try to improve your self discipline, get on a, a schedule, get on a pattern, even if it's not a schedule, just focus on self discipline. Even if it's just today, this is what I'm gonna do. Do that thing that day. Don't let yourself get distracted by Netflix. Don't let your put your phone down right. Only allow emergency calls through or whatever, and just focus on the material and get it done. That is going to build a phenomenal habit of, of, of self-talk developer. The amazing thing. I'm telling you the amazing thing about self-talk developers. People go to coding boot. Okay. First of all, people go to coding boot camps because they want structure. They don't have that self-discipline or they don't have that sense of direction. They need someone on top of them. They need that guidance, right? You are a self-taught developer, figuring out all of this on your own. You are highly desired by employers. If you can get to that finish line, highly desired, don't ever forget. One foot in front of the other and keep moving forward and then seek out that external direct or seek out external support as you need it. But that's another thing, a lot of, of aspiring developers. Um, they get lost because they don't really have the right support system. They don't join any online communities. Um, you could look for discord communities with your favorite creators. Um, you can look at meetups, you can look at event, right? You can look at tons like online hackathons in person hackathons, whatever you wanna do. A lot of those are out there. And if you're in an area where you don't really have that in your local space, you could, there are a lot of online opportunities get involved in online discord communities, but don't just go in there and ask a question, go in there and engage with. I keep bumping my mic. I'm sorry. Um, go in there, engage with people. You're gonna build relationships. You're gonna build people that also wanna respond to you when you do have a question. That's one thing a lot of, uh, aspiring developers fail with is they go into a community, just ask a bunch of questions. They essentially ask for a bunch without giving any value back. Don't do that. Don't be that developer. You never wanna be that developer. So try to find that support system. I think it's gonna be really helpful, even if it's just other aspiring developers. They can give you that little boost of motivation, right. Or you can ping something like, Hey, you know, I was thinking about doing this, um, picking up this library here, it's pretty marketable. Right? A lot of companies are asking for, what do you think about this? Oh yeah. I actually saw a lot of Jo job postings with this. I'm also trying to learn this, right? Like even that little bit of feedback can help, but you also wanna get a breadth of. Feedback and experiences because, you know, you're all aspiring developers at the end of the day, and you gotta take each other's advice with a grain of salt. It really helps to talk to professional software engineers, but you talk with enough, enough aspiring developers that can't actually build a pretty good support system. And usually there are professional software engineers lingering in those communities that can't help when people truly get stuck. But yeah, um, a big thing, I think one more big thing with the motivation is a lot of people don't know. Self-assess their progress as an aspiring developer. Like what, um, how do I actually know that I'm actually getting better and what I want you to do? Little exercise, really simple. Look at your code two months ago is actually, I'm just gonna say like how bad is your code compared to what it is now? Would you do something differently? Would you build this function differently? Would you even just word the variable names differently? Would you even build this feature with different types of functions and, and a different type of implementation? Would you do any of that? If you would, and you would change something you're making progress and it's okay to laugh at your old code software engineers experience software engineers constantly go back into their old code and they're like, did I write this. Ugh. Okay. This was only like three months ago. Wasn't it? I can't believe I wrote this like software engineers constantly grow a lot of aspiring developers say just fail to assess their own growth. And it's a tough thing. Sometimes again, it helps, you know, Building relationships with experienced software engineers. You could do that within communities you'd even get paid mentorship. That can be a great thing. So a lot of self-taught developers can save a lot of money. They don't have to pay, you know, 15, 20,000, even 10,000 for a coding bootcamp. They could just pay a software engineer, a fraction of that cost to just check their code, do a little bit of a code review. Am I heading in the right direction? Um, what would you recommend? You know, like if you were considering me for that position, what would you recommend? What would I need to learn? So. You wanna also try to seek out advice from software engineers that also help and mentor junior developers, cuz some senior software engineers can kind of get caught in their own patterns and rhythms and they don't really, sometimes it's hard to. essentially, um, I'm not trying to be offensive, but like dumb things down for people that haven't, um, haven't, don't quite understand a lot of these advanced concepts. Sometimes software engineers need to work on how they talk to people that aren't technically proficient as much as them. Right. So you gotta find the right mentor and that can take a little bit of time as well, whether it's paid or free. I think that's still super valuable. Try to get that support system, try to evaluate your progress. That's huge, right? And again, I'm gonna emphasize this. Fuck your motivation. Your motivation will not get you through your self discipline in resourcefulness will. Um, another thing have fun. Everyone wa I, the number of times I'm like, okay, well, what projects do I need to build for employers to, uh, wanna hire me? Well, what do you wanna build? What do you mean. okay. Well, you're, you're a person that is becoming a software engineer. You're not just some code monkey. You're not just gonna build some random thing. You are you, so you can do that. But those kind of software engineers, they're not super marketable. Believe it or not. What you are is a human being that had a, a past, a previous profession where you probably would've loved a software that you could build. If you could build something for your old self and your old profession, what would it. don't tell, like, don't even tell me that you haven't worked with shitty software at a previous job. Right? How could you improve that software? And if like, if you're really gonna tell me that. Okay. I, I hear you. You're really gonna tell me that you haven't worked with any tech, right? All of your jobs are archaic. No tech whatsoever. Sure. I believe you. If that's the case, what even got you excited about coding? What did you, you probably thought about? Like, it would be really cool if I could build this. What would that thing be? What are some of the applications that you have built? that or not, uh, that you use on a daily basis. Could you build smaller versions of that? Do you wish they had a feature that you could build? Right. And so those are some ways to come up with project ideas, but more importantly, you gotta have fun and build some quirky stuff. Like, especially your fir first few projects who gives a shit. If employers are gonna hire you for it. Cause it, the beauty of it is it's like, I know you wanna get hired as soon as possible, but you're actually delaying that by not having fun with coding and exploring and building what you wanna build and tackling the challenges you wanna tackle. Right. It kind of goes back to motivation too. People are just going to the motions and learning what they have to, to finally get that job. And that's sounds like the most boring, long path ever. Most people aren't gonna be success. most people are gonna give up on that path. Have fun. If you wanna explore a little library, maybe it's not the most marketable library, but you're like, this is kind of cool. I wanna play around with this. Take a day, play around with it. Take a couple days to play around with it. Have fun as a software engineer. I think one of the most healthy things software engineers can't do even in their current profession is work on a personal project that they wanna build. Right. They're like, it would be cool if I built this thing or I always wanted to pick up this library. I always wanna pick up this F. Do it, you're going to learn and grow from it. But more importantly, you're going to start this. This is actually a big boost of motivation. If you're seriously lacking it, like you're going to start figuring out, first of all, the things that you do like working with, cuz you're expanding your variety of frameworks and libraries that you're working with. But you know, it, it, it, sometimes it's just fun to break things and build things even if no one's gonna use. uh, to me like the, when I always lacked motivation, I would always think about the projects. I always had like a list of projects that I wish I could build, or I wanted to build. So, or even technologies I wanted to explore. It's okay. Not to learn every marketable language. So I'll give your front and okayl CSS jobs script get pretty good with all three, build some landing pages, build some front end apps and then expanded, uh, react. And we're gonna build some apps, so to react. Cool. Okay. Yeah. That's kind of the path to go, right? If it like, there's no, nothing exciting about that. That sounds like a chore. That sounds like the most boring path ever. And like, is this what being a software engineer is like, no, it's not software engineers explore all the time and they have fun with it. You can't always do that at a full-time job, but a lot of software engineers will do a personal project on the side, or they'll pick up another library on the. That's having fun as a software engineer, that's going to help is definitely gonna help boost that motivation and push you towards that finish line. So once in a while, explore, even if it's a portfolio project, let that be your portfolio project. The interesting thing is those types of projects that you have fun with can intrigue certain employers if you build this weird, um, like, like if you're just obsessed with fitness, obsessed with diet, right? You just wanna build this little, um, health tracker. if there are two candidates, one that has never worked on a fitness app in their entire life. And one that said, fuck it. I'm gonna try to build this thing. This would be cool. If I could even just log some of my stuff. Like who do you think they're gonna boost a, uh, who do you think is gonna gain that advantage in who they select? It's gonna be you companies want to hire, uh, especially junior developers that sync with what they're trying to do and the types of solutions they're trying to. And you can showcase that unique side of you through these little quirky projects that you explore. And you can, you can put those on the portfolio right now. Some of these projects are gonna be pretty basic and eventually wanna build more complex applications, but those projects are still valuable on your portfolio. So. a challenge of being a self-taught developer is trying to piece all these courses together. And one thing you'll realize is you don't have to take these giant courses and try to piece them together to tr uh, to come up with this, uh, all the knowledge that you need to become a software engineer, you know, even going through a course that focuses on really good fundamentals, right? You're gonna find that in a lot of free courses, you can take that and then try to build your application. And then when you come to a feature where you can't quite figure it out, you can supplement with just a single page article. Maybe it's you kind of understand authentication, but you haven't really implemented it yet. Maybe it's an article talking about session based authentication with node. You use that article, you try to implement it on your own. And maybe you look up another article that can help, uh, understand, or maybe look up the API documentation, which is a really healthy thing to do. But, you know, being a self-taught developer, it's about piecing all this information together and. You can make it work as long as you're building on the site, as long as you're reinforcing what you're learning build, and then supplement that knowledge that you still lack, even if it's a small article and course, but I'm telling you your priority should be building and reinforcing everything that you're learning. Try not to spend too much time with tutorials. You can't eventually piece all this together and it gets easier. You start, you're able to figure out which courses are actually better for you. The further you get into it, if you're building, right. Because you're gonna be constantly testing what you're learning too, from those courses, when you build, like, am I able to remember this stuff? Can I at least look up API documentation then like, I look up as, you know, a method on an array and I'm like, oh yeah, I learned that in the course. And then it. That it starts getting reinforced. Or are you just always lost with this set of courses with the specific author, maybe you, that means move to another course. That's gonna resonate with you where you're gonna understand it more thoroughly. So that's the juggling game that you're gonna play as a self-talk developer. Everyone plays it. It's really tough. It's one of the toughest things about being a self-talk developer, but as long as you're. And supplementing and building and supplementing and building that's eventually gonna push you towards the finish line. Keep pushing forward with that. Last thing is how do I get a job? There are tons of questions. So, um, I'll, I'll touch on this briefly, cuz I have so many videos, career advice, videos that you could check on, but you know, make sure that I, I would highly recommend that you have a portfolio portfolio projects, your portfolio itself. Isn't that valuable. like, as, as far as the problem you're solving with the portfolio, um, the, it, you're just displaying projects. It's just a gallery for the most part. Maybe some contact information, if you really wanna put it on there. Uh, it's not that interesting of a problem to solve. What's interesting is your specific projects that you chose to build and display, right. So really focus on. your code conventions, your code quality, um, even just documentation, putting up a read me for your, your project and on your portfolio. Just displaying relevant information, having a live link, having a link to your source code. Um, I highly recommend GitHub for that. Um, and then you could, you know, a little about me with it with the technology is used is like the bare minimum that you could do, but I'm get that portfolio up at the very least, have your resume full of the projects that you did work. And send that out. You're gonna do a lot of cold applications. A lot of people here's, here's a big thing that self-talk developers get stuck on. They don't hear anything back. Right? A lot of coding, boot camps are gonna share. You're gonna get tons of rejections, tons of rejections. And this is how you analyze your resume and change it. Um, I notice there's a lot of bad advice for self-taught developers on. Um, having just one standard template of a resume, which that's not terrible advice, but if you have like a dream company, you're gonna tailor that resume towards that dream company. For most of the other jobs, you're gonna have a template of resume, but you should be submitting a cover letter with every single application, really bad advice for developers. Like if you're gonna be doing cold applications is don't submit a cover letter. That's horrible advice. I hear it all the time. I know it's a controversial thing. Submit that cover letter I'm telling you, it goes a long. Usually it's HR and the recruiters that are gonna see that cover letter. And again, it should make sh make sure in that cover letter, you are. showing that you understand the values and the mission of the company, and also how a lot of your technical skills and your own values are gonna contribute towards that mission and build up the company, right? You are the software engineer that's going to integrate, uh, kind of sounds like a creep. You're gonna integrate essentially into the culture of the company and your values align. So you're gonna help build up that ultimate mission, that ultimate destination to the company, right. And that can help align a lot of your, like, if you can align a lot of your cultural values. People on the team, especially that's gonna be pretty huge, but usually that covered letter gets viewed by the recruiter, not so often by software engineers and CTOs and people that are gonna potentially hire you on that team. So that's just something to keep in mind. I highly recommend you submit it, but you should be on LinkedIn. We talk about it now working a lot. I have videos. I, I believe I should have videos on that. Uh, I have like pieces of it. a lot of developers get discouraged because they're just not finding jobs. I went through, uh, probably close to 200 applications before I got a job seven years ago. How long has it been? Five years ago? Seven years ago. I think maybe it's five. I'm. I, uh, six, we're gonna say six years, it's been a long time, right? We're in a recession right now. It's going to take a little bit longer. And so I would highly recommend you put a system in place. I'm gonna apply for maybe 15 jobs per week. If I'm doing this full time, 15 jobs per week, I'm telling you that's a lot of jobs. You're gonna be doing a little company research. You're gonna be getting rejected a lot. A lot of people get stuck here when they're apply. they a lot of aspiring developers that are self-taught. They get stuck. They give up because they're not getting any calls back, have your resume scanned by a software engineer, a hiring manager have, um, Have someone even just analyze your LinkedIn profile, um, have someone analyze your, your portfolio, et cetera. And these probably should be people with experience in the industry. Don't just like get a recruiter that has no experience as a software engineer to look at some of this stuff, but get someone that does help aspiring developers to help software engineers with this, with these career related things. And has experience as a software engineer. I'm telling you, there's a huge difference between the advice of both individuals. So this is where people get stuck. This is where you're probably gonna fail. I'm just gonna be blunt with you. This is where you're probably gonna give up. It's a job search. You have a few projects. You are so close. I am telling you most aspiring developers are closer to getting that job than they thought a huge mistake of me almost wanting to. and I went to coding bootcamp. And the only reason I didn't quit is because I did just take one final chance at a coding bootcamp. Didn't think it was gonna be worth the money. And I did finally get that job. You don't need to do that, but I'm telling you most aspiring developers are closer to getting that job than they think. And it, you almost, here's kind of advice everyone handle handles this differently, but you almost have to take, take your emotions out of the job search. Dealing with the rejection is one of the hardest things to deal with. You're gonna be rejected more with this job search with becoming a software engineer probably more often than you've ever had an experience in your entire life. It is a very grueling and defeating challenge to go through. I am telling you be prepared for it. Don't take it person. That's why most people give up, they think they're not hireable, or they want the wrong direction, waste it all that time and money. And like they're so close and they take that rejection way too seriously. It's there are always things that you can approve, always things that you can improve, but ultimately it just, it's kind of a numbers game at that level. It it's going to take time and you can use the other feedback to that. Shared in this video to help push you a little bit forward and provide that motivation. It's just going to take time. And this is where, when you come in with re unrealistic expectations and you don't give yourself that year or two to be able to achieve this, this is where most people drop off. Right? So I, I'm telling you be patient with yourself. You're probably closer. And we're in a recession right now. Um, I, I don't care what other people say. Some people actually deny that we are we're in a recession right now. It's going to be a little bit tougher. You are hireable. You are smart enough. You are someone that, you know, plenty of teams are going to wanna work with. It just takes time to find that right connection. And you just have to treat it, be systematic about it and do it week after week after week after week until it happens. I know that sounds robotic. You have to be able to handle that emotion of that rejection, continue doing it, building your projects and alongside of that, applying for jobs, networking, et cetera. So. That's it. Um, I have tons of specific advice in my other videos. I do, I have a lot of other advice looking. Um, if you go to my home page on YouTube and look at the career advice section, that's the current playlist, just scroll through those, even go through the self-taught videos. You're gonna hear people share their stories as a self-taught developer. It's grueling. It's really grueling. It's it's heartbreaking. And the only people that eventually become developers are ones that don't give up. That's it? That's the only difference between people that don't become developers and people able that become developers, the ones that actually got that job, they just think of up. It sounds stupid. It sounds silly. It sounds like I'm just bullshitting you, but that's, I'm telling you, like I said, I'm, I'm not bullshitting you. When I say this, I mentor thousands, thousands of aspiring developers for the last seven years. It's been a very long time. Even. I was mentoring people, even when I was trying to get to position myself. It's so crucial. It's so crucial that you recognize that you are fully capable of getting this position. You are close, please. Don't give up on yourself. Hopefully this advice was helpful. Um, there are. Definitely more bullet points I could cover. There's a lot of advice I can give for self-taught developers. So if you wanna see more of that, you wanna hear it. If you're listening to the audio podcast, let me know. I'm happy to dive into this. Um, my heart goes out to people that are struggling low motivation. Down on yourself. I get it. I've been there. Almost gave up myself. Trust me. I do get it. Just keep pushing forward.