The fact that people take their time to give someone guidance on the struggles they went through and pave their path. And someone dislikes this😒. Thank you for this video. I've honestly stumbled on this channel and I enjoyed it. Thank you again❤️. I've recently started with LeetCode, I hope it gets me where I want to be.
hey, thank you so much for the kind comment. i'm glad to hear that you enjoy the content! i'm wishing you the best of luck and hope that i can continue to make relevant videos :)
leetcode is one component of the interview - unless you're going to work at FAANG or some really high end job it's likely not going to be the most important part of the interview. That's going to be the behavioral questions and whether they see you as a good fit longer term.
hey Matt - I totally agree! this is also something that I stress in some of my other videos covering the interview process but it is a great thing to add for this video too :)
Are you sure? Cuz technically interviews is what really scarring me rn and I’m not good at taking a problem description into a solution but I can write code just fine.
Girl just recently unknowingly I started something similar strategy But after listening to your version I guess I will improvise my reinforcement practice 😮and try that out Damn
Thank you so much for this video many other videos just droned on and on about things i didn't understand. Thank you for breaking it down and I'm also adding codewars to help with recalling and repetition.
thank you so much for the feedback! i'm so glad you found this video more accessible - that's definitely something I have in mind when creating my videos :) best of luck!
Honestly I don’t agree with grinding leetcode to get interview ready. I have a buddy who just got a job making 6 figures as a software developer and he didn’t get asked a single leetcode question. For me, I am interviewing for C# and Java jobs, and I honestly think doing these problems are not very useful. I’ve been making API’s and business applications, and that experience is so much more useful. Granted I can solve a lot of leetcode questions from easy to medium but anything hard would probably take me over 2 hours or just not possible for me right now. I think that’s ok too I’m not going to grind any more than that. I’d rather be more well rounded in my GIT, familiarizing myself more with my IDE, SQL, and the various technologies I want to work in. I think going the approach of just solving leetcode problems is kind of defeating the purpose of programming, which is to build applications. Anyway not trying to take away from your video, but I am going to start my job search soon for being a Java or C# developer (hopefully C# lol). So I may seem like an idiot in 3-4 months when I am unemployed haha. But I’ll be fine because even when I get a problem in an interview I’ve never seen before because I don’t grind leetcode, I’ll be able to brute force it, explain my code, and explain the time complexity. I think even if you code something that is O(n) when O(log n) is possible, as long as you can explain your solution cleanly and show you can code, it doesn’t matter to an interviewer. If an interviewer really thinks I should know how to do a data structure or algorithm that is barely or never used in real world applications, I don’t want to work for that company. I don’t really want to work at a place like google or Amazon right now anyway. I’d rather build up experience in the industry and use that to build my career rather then grinding my ass off to work for a specific company. Anyway not trying to take away from your video I don’t think it’s bad advice, but I do think there is too much leetcode hype on the internet when most people looking for good coders don’t care about how many leetcode problems you can solve: they care about how well you can code. How well you code and how many leetcode problems you can solve are not the same imo. Granted if u can crank out hard leetcode problems you’re probably pretty good haha but being able to solve all the easy ones the most efficient way possible isn’t an accurate depiction of how well you can code.
hey there! not offended at all and i appreciate the discussion that you're bringing up. i totally agree that how good you are at leetcode isn't a true indicator of your ability to be a strong software engineer because it's true that your day to day coding tasks are usually unrelated to the nature of leetcode. i think there are certainly knowledge areas that cross over and do have applicability (strong fundamentals skills of solving slightly more complex problems, data structures) but they don't necessarily appear in leetcode-like format. it sounds like you have a solid foundation and may not need to invest time into leetcode - which is great! i know there are plenty of companies that don't hire with leetcode, but even if it isn't your cup of tea, there are unfortunately plenty that do as well. if you can look at a few problems and feel okay about them, then this probably isn't a video you need :)
@@LauraJiang I wrote that 3 months ago, and yesterday I just got my first job offer! But I’ll be honest I did spend some time on leetcode, probably 5-7 problems a month. I actually got some certificates on HackerRank, and that is why I got the job I did because a recruiter saw it on LinkedIn and reached out. My interview had no leetcode questions, but they did ask me about a lot of programming concepts. I made that comment because your video was probably the 20th I had seen talking about leetcode, and I felt like nobody was really talking about actually programming (at least videos geared towards people getting their first jobs). I live in the Midwest, and most companies here don’t ask any leetcode questions, which is another reason I was frustrated with seeing so much content about it on RU-vid. I think it definitely depends on area too. Midwest companies are much more conservative and care more about the person they’re hiring and your passion for software development. Anyway I appreciate your video and I appreciate your reply too! Best of luck to you, thanks for replying!
using python is litterally buying you comfort with how fast you can solve things, ya you could argue the speed of it or whatever else, but i'd rather solve something in 5 lines over 15 lines
Just a beginner (tempted) question - Does anyone knows how to get the LeetCode 50 days badge??..Is that by solving daily challenge problems for 50 days or solving any problems for 50 days??
hi Kamila! it'd be great to ask your interviewer! something like "I think I know the optimal solution here, but would you like me to briefly walkthrough the brute force one first?" that helps them get more insight into your thinking process :) hope that helps!
hey! it really just comes down to practice. when I first started, it definitely took me a while, even for easy problems and especially for medium problems (I didn't even try to solve a hard problem!). as you start to recognize patterns in questions, it'll get easier and a great way to build this pattern recognition is through the themed questions or blind 75 list that group problems for you already. when you think about interviewing, you'll be thrown into a 30 minute or 45 minute interview and realistically only have 20-30 minutes to solve a problem that they give you, so as you slowly get better, you'll likely see your time to solve come down as well.
honestly, start small! start with 30 min sessions that feel achievable. if you feel like you are progressing well with 30 min a day, then you can keep it at 30 min, or move up to closer to an hour. but i recommend keeping it shorter than you'd think to help build up your leetcode habit first then see if you need to increase or decrease how long you practice each day for!
hey Lorena! it can be a little bit of both - it can help with general programming fluency and your awareness of algorithms, patterns, etc. but you should have a feel comfortable with the basics of coding prior to jumping into to leetcode!
@@LauraJiang indeed. I'm following the "python crash course", and once I learn for instance, list, I have tried to solve one easy question on leetcode and I felt miserable :(
