If you are an aspiring developer and you're about to embark on the journey of becoming a web developer, or you're just flat out stuck right, you're really discouraged with a 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. In this episode, i'm going to 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. It's a very affordable path, right, and i want to make sure that i give you as much advice as possible to make it work, so let's go ahead and dive into it. A lot of aspiring developers start out with false expectations. They watched a tick-tock video telling them that they're going to 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 taking 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, now i'm running out of money. I financially planned i might have quit my job, or i financially planned or play 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 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. But i don't even feel like i'm making progress because 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 going to get a job and 100k job as a developer in three months, like that's ridiculous.
You talk to any experienced software engineer. They're going to say that's right. Obviously there are going to be exceptions to the rule, but 99.9 percent of people are not going to land it that quickly with that much money.
It's not going to happen, right. So a lot of people start out with that unrealistic expectation it's going to take a while. I know you're not going to want to 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-taught 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. But you have to expect you're going to 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 because 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 want to talk about some things to really help reinforce this knowledge and try to make that path more linear. But number one key thing: a lot of self-taught developers make- 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. 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 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. You know, one flaw of a coding bootcamp- it's 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 slower pace, you can take the con out of that and essentially learn all that information and just spread it out over time and that can definitely help you reinforce a lot of the concepts.
You can't cram this 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. 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 tests. We take the test and we pass, 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 going to 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 tick tocks youtube videos that say, yeah, three months, 100k. Stop watching that creator. I promise you stop watching that creator. So a lot of people, when they do dive into the curricula, big complaint is: i don't feel like i can build anything. Right. So you go through a course but they're like: i don't feel like i can build anything. 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.
Of course makes them feel like they're progressing and they're learning things and remembering things because they're getting, you know, they're passing the challenges on the course, etc. 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 want to 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 got to 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 going to 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 out of the course, build something small, something slightly different, change it in a little bit of a different way, or even think about a project you want to build. Maybe you take that course and you think about, like okay, maybe at the end of this course i could build this kind of- or this is the kind of project that i want to build. How can 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 that, you start forming this knowledge of how you start, you're able to piece together this project and your mind, you're able to conceptualize it 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 going to help you reinforce a lot of what you're learning. So don't get stuck in tutorial hell. I don't know how many self-taught developers are stuck here- i. 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 can even go to websites that you 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 going to 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 and i'm gonna try to build it, reinforce it, and things just aren't clicking. You just you're like this day i don't, i really don't wanna do this and guess what you do. You do it 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. That motivation will waver. It don't believe anyone that tells you otherwise. That motivation will waver, it'll go high, it'll go low. Do not depend on that motivation. What you do depend on 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. There is no way i can even see myself navigating through life without a calendar and a schedule and a to-do list. It's. It has changed my life entirely. I'm telling you it is.
It can really make the difference between someone that is 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 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, but it's it's incredibly important that you just set a schedule like, if it's monday, wednesday, friday, two hours, right, my, my wife's willing to take the kids when i get home from work, or something like that, and just get them out of my hair so i can code. If talk to your family members to be able to have that set schedule to to code and do what you need to do. Do that for as long as possible and then try to get more efficient with how you use your time during those two hours and you can 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, ten 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, you're just learning to code. I'm telling you: don't spend a lot of time at courses learning. You spend a lot of time practicing, getting your hands dirty, reinforcing the implementation, but that motivation will wane.
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, water, not loading yourself with caffeine and then just crashing at the end of the day like, or the middle of the day, often getting a good night's sleep, making sure things are in order, 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 that and a lot of people get jobs with it as well. The reason, like i said, the reason self-taught developers- most of them- don't get jobs is because they give up. That's it. 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 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 self-taught developer. The amazing thing i'm telling you, the amazing thing about self-taught developers: people go to coding. Okay, first of all, people go to coding bootcamps 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 that 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 aspiring developers- they get lost because they don't really have the right support system. They don't join any online communities. You could look for discord communities with your favorite content creators. You can look at meetups. You can look at eventbrite. You can look at tons of like online hackathons, in-person hackathons, whatever you want to do. A lot of those are out there and if you're in a 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 people. I keep bumping my mic, i'm sorry. Go in there, engage with people. You're going to build relationships you're going to build people that also want to respond to you when you do have a question. That's one thing a lot of 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 want to be that developer.
So try to find that support system. I think it's going to 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, picking up this library. I hear 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 job postings with us. I'm also trying to learn this right. Like, even that little bit of feedback can help.
But you also want to get a breadth of feedback and experiences, because you know you're all aspiring developers at the end of the day and you got to 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 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, a big thing. I think one more big thing with the motivation is a lot of people don't know how to self-assess their progress as an aspiring developer. Like what, how do i actually know that i'm actually getting better and what i want you to do? A 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 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- experienced software engineers- constantly go back into their own code and they're like: did i write this? Ugh, okay, this is 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. They 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 could 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? 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 want to also try to seek out advice from software engineers that also help and mentor junior developers, because 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 i'm not trying to be offensive, but like dumb things down for people that haven't 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 going to emphasize this: your motivation. Your motivation will not get you through yourself. Discipline and resourcefulness will another thing. Have fun, everyone i the number of times i'm like: okay, well, what projects do i need to build for employers to want to hire me? What do you want to 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 going to 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 past, a previous profession where you probably would have loved the software that you could build. If you could build something for your old self and your old profession, what would it be? Don't 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, 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 got to have fun and build some quirky stuff, like, especially your first few projects. Who gives a if employers are going to hire you for it? Because the beauty of it is. It's like i know you want to get hired as soon as possible, but you're actually delaying that by not having fun with coding and exploring and building what you want to build and tackling the challenges you want to 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 sounds like the most boring, long path ever. Most people aren't going to be successful. Most people are going to give up on that path. Have fun. If you want to explore a little library- maybe it's not the most marketable library like this is kind of cool. I want to play around with this. Take a day to 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 do, even in their current profession, is work on a personal project that they want to build. Right, they're like it would be cool if i built this thing. Or i always want to pick up this library. I always want to pick up this framework. Do it. You're going to learn and grow from it. But, more importantly, you're going to start.
This is actually a big boost in 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, because you're expanding your variety of frameworks and libraries that you're working with. But you know it, it's sometimes it's just fun to break things and build things, even if no one's going to use it. 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.
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 side. That's having fun as a software engineer. That's going to help. It's definitely going to 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 like, if you're just obsessed with fitness, obsessed with diet, right? You just want to build this little health tracker app. If there are two candidates- one that has never worked on a fitness app in their entire life and one that said 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? Who do you think is gonna gain that advantage in who they select? It's gonna be you. Companies want to hire especially junior developers that sync with what they're trying to do and the types of solutions they're trying to build, 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 going to be pretty basic and eventually you want to 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 come up with this. 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 going to find that 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 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 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 going to 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 like then it starts getting reinforced, or are you just always lost with this set of courses, with the specific author? Maybe 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 going to play as a self-taught developer. Everyone plays it. It's really tough. It's one of the toughest things about being a self-taught developer. But as long as you're building and supplementing and building and supplementing and building, that's eventually going to 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 i'll touch on this briefly because 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 far as the problem you're solving with the portfolio? You're just displaying projects. It's just a gallery for the most part, maybe some contact information if you really want to put it on there. 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, even just documentation- putting up a readme for your, your project- and on your portfolio, just displaying relevant information, having a live link, having a link to your source code.
I highly recommend github for that and then you could you know a little about me with it, with the technologies used. It's like the bare minimthat you could do, but get that portfolio up. At the very least have your resume full of the projects that you did work on and send that out. You're going to do a lot of cold applications. A lot of people here's. Here's a big thing that self-taught developers get stuck on. They don't hear anything back, right? A lot of coding bootcamps are going to share. You're going to get tons of rejections, tons of rejections. And this is how you analyze your resume and change it. I notice there's a lot of bad advice for self-taught developers on 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 templated 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 way. Usually it's hr and the recruiters that are going to see that cover letter.
And again, it should make sure, 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 going to contribute towards that mission and build up the company right. You are a software engineer that's going to integrate- kind of sounds like a creep. You're going to integrate essentially into the culture of the company and your values align. So you're going to help build up that ultimate mission, that ultimate destination of the company right, and that can help align a lot of your like if you can align a lot of your cultural values, with people on the team especially. That's going to be pretty huge. But usually that cover letter gets viewed by the recruiter, not so often by software engineers and ctos and people that are going to 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 networking a lot. I have videos- i i believe i should have videos on that. I've like pieces of it. But a lot of developers get discouraged because they're just not finding jobs. I went through 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 six, we're going to 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 going to 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 going to be doing a little company research. You're going to be getting rejected a lot. A lot of people get stuck here. When they're applying. They get 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 hiring manager. Have have someone even just analyze your linkedin profile.
Have someone analyze your, your portfolio, etc. 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 going to fail. I'm just going to be blunt with you. This is where you're probably going to 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 quit and i went to cody 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 going to 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 going to be rejected more with this job search, with becoming a software engineer- probably more often than you've ever had 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 personally. That's why most people give up. They think they're not hireable or they went the wrong direction, wasted 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 improve, always things that you can improve, but ultimately it just it's kind of a numbers game at that level.
It's going to take time and you can use the other feedback to that i 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 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'm telling you: be patient with yourself. You're probably closer and we're in a recession right now. 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 want to 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. I have tons of specific advice in my other videos. I do. I have a lot of other advice. Looking, 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 story 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 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've mentored 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 that position myself.
It's so crucial. It's so crucial that you recognize that you are fully capable of getting this position and you are close. Please don't give up on yourself. Hopefully, this advice was helpful. 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 want to see more of that, you want to hear it. If you're listening to the audio podcast, let me know. I'm happy to dive into this. My heart goes out to people that are struggling low motivation down on yourself. I get it. I've been there. I almost gave up myself. Trust me, i do get it. Just keep pushing forward. [music] just.