Hook

Leetcode study guide
Their other posts in the index, biggest breakout first.
So I'm going to call to all software engineers and computer science students saying if you're struggling to find an internship or a tech job, reach out to me directly I will help you out. This guy did exactly that he asked me how exactly do you study L.C.O.E.A. code pause to read. This is what you do step by step and I mean literally step by step step zero you need to already know introduction to computer science. Like if you don't know what recursion is you have to take an introduction to computer science course. This is unavitable. Step 0.5. I also recommend you take a data structure and algorithms course. Now, you don't absolutely have to. You can learn data structure and algorithms while studying Lean code. So you're someone that's impatient doing courses and you don't need to do this, but I highly recommend it. Here's a great introduction to computer science course. It's Harvard CS 50 is one of the best and it's absolutely free. Same with stants algorithms part one and algorithms part two. If you go in a course, you can get it for free. Then you're going to do this. You're going to take whatever Leo guy you're studying. Whether it's blind 75, Leo 150, whatever guy is the newest guy of the day. You're going to take that guy. You're going to ask cloth to convert it to a spread sheet like this. This is blind 75. You can see all these columns and if you want me to just send it to you, just send me a DM and I'll share you a link. You're going to Google a timer for 20 minutes. It's going to set a timer for 20 minutes. You're going to try your best on a problem as much as you can. Now, you're allowed to give up early. You're not allowed to type a single line of fucking code once this timer goes off. Do you understand me? This is called time boxing. You're not allowed to go over the limits because then you'll spend too much time. There are way too many problems to spend an hour for a question because your ego is too fucking big. Say timer for 20 minutes. Don't write a single line of code when it goes off, you stop. You go to YouTube.com. Wow, this was scary. Did you see that see that? Oh my god. You type in the name of the problem and you go to this one here. Code is the best. There are probably other ones. Feel free to explore. I recommend just just make it easy for you. Go to code. You watch this video and you sort of want to follow along in code as they solve the problem. You submit the correct solution and then you mark here that you didn't solve it in 20 minutes. Then you move on to the next question. Repeat the same exact process, 20 minute timer, mark the column, move on. Mark the column, move on. Do at least four hours per day. It's going to take you a couple of hours, but you have to be consistent. For the first week, you're basically going to get nothing right. Everything's going to seem horrible. have a sense of impelling doom. For the second week, you're going to start getting the easier, right? You're going to feel better, try the mediums. Then you're going to feel horrible, having another sense of impelling doom. And then after the first month, you'll start to kind of understand the common patterns for these questions. That's the full process in the end. If you follow it, you'll get a tech job. Good luck.