Automatic Transcript

Hey, everyone. Welcome to AlgoDaily's 60 day crash course, week one part two. As you can see here, I've been working through the course with everyone and, the instructions for the last week or two go from the introductions all the way to fizz buzz. And I'm happy to report that. So many of you, participated, so many of you who participated finished.

Exactly that. So about 75% of people who, said they were going to finish every tutorial wrapped up and got to fizzbuzz. So for that congratulations. And, let's keep chugging along before we dive into what's expected for this week. I just want to give a quick shout out to some people who, Who were participants of the 60 day program and, wrote in and gave feedback.

So real quick, first, I want to highlight. The Maitri Pavlov who, jumped the gun a little bit and started working on the sliding windows, tutorial, gave some good feedback back sliding windows. And, I was, I, saw that and, made an updated video for it, which should hopefully clear up the concept a little bit better.

Then we had some great discussion with, stance, Laos and Tim, for reverse a string, some, things that I hadn't considered, uh, and added onto the tutorial as well. And then.

I also want to shout out, Rudy, Rudy, Becker, I believe. , who's been consistently posting his progress on a hundred days of code, as well as updating everyone on how he's working through the curriculum publicly on Twitter. So I'll make sure you guys check his Twitter feed out. It's a really dope, underscore Rudy Becker underscore.

All right. For this week. I'm going to give a quick run through of the tutorials. And one thing to keep in mind is that I'm going to, keep, modifying some of the orders of the future weeks as we learn from these few, these first few weeks. So, One of the pieces of feedback that came in, from our participating member, Jacob Danner was, that serve some of the tutorials required a, a stronger foundation in certain concepts before you were able to really understand what was happening.

And so we've moved those tutorials and those lessons to later on, in. The crash course. And for now we're going to start off with some more found the fundamental and simpler ones. So if you guys have feedback like that, please do let me know via email. I received about about 15 or 16 emails regarding just the first, half of the first week, this week.

So it's been really great and, hopefully I've been responsive and, and, been able to help each and every one of you who wrote in, so for this week, we're going to cover it. How to get better at approaching coding interviews and this, this tutorial is pretty lengthy, but it's really going to help you learn how to approach, um, coding interviews in a more structured manner.

, we don't have a video for this yet, but if you go to the main focal and. , check out, approaching coding interviews through a recruiters lens. You'll see a webinar that I did with, in conjunction with hack with a hacker earth, about a year ago that covers, most of those concepts as well with a general framework.

What I call the CTB P B O framework, that gives you a step-by-step, direction to, solve any kind of coding problem. So you can check that out after, um, going through how to get better at coding interviews. We have a quick refresher into, um, arrays and strings. So I expect most people participating to be very familiar with the raising strings already, but this is just a good primer, so that you can just play around with a raise and just get a sense of, what they are and what their properties are for technical interviews.

Then we're going to start solving two problems related to a raise. So array intersection, and find missing number of array. I think I told you guys last time that I was going to, I was going to go ahead and update this video and sure enough, here's an updated video that walks you through it. Then we're going to cover, our first of many, um, I first have many patterns for coding interviews.

So the two point technique is one that you want to be able to whip up, at any given time. So array and string problems. , and I S I grouped them together because string problems are usually very similar to a raise. , in terms of how you solve these kinds of problems, but these two groups of, interview type interview question types, can often be solved by using multiple pointers.

So, check this tutorial for a sense of how to solve a problem with two pointers. Then this isn't a requirement per se, but there is a. , data structures, cheat sheet, and this will be a good reference throughout the entire crash course. And so it's as the name makes it to be, it's a cheat sheet for data structures and it contains all of the general data structures, a few of them.

We're going to cover later on in the crash course, but you can go ahead and take a look, starting now just to get a sense of. Uh, how they function and you can, like I said, use this as a reference throughout the crash course. And then finally for this week, we're going to try to solve the isn't and the grand problem, which is also a very common one.

And that'll wrap up week one. All right. That's it for today. If you have any questions or feedback at all, make sure to reach out, via the community or via email. , we'll be in touch. See ya.