 What's up guys Mike the Coda here. I have not uploaded a video in a long time. I'm sorry about that I couldn't actually create a tutorial for anything, but I just want to give a good explanation And not explanation. I just want to give a quick video on a thing that I have a huge trouble with a lot I think it's the reason why I was not improving at all When you do math problems, you do do never never ever copy and paste code And I think I've said this in a previous video, but I want to be Iterated again. I think it wasn't the main focus of the video But you really don't want to copy and paste code and here's the reason why cuz like, okay so I've been doing these Cces problem sets, right, which is kind of like they're kind of They're not really basic problems. They're they're standard problems that you would probably see and Most competitive programming problems, right? So in one of the case there was this problem where it's like two nights, right? Basically your task is to count The number of ways two nights can be placed on the k by k chessboard and they do not attack each other so this problem is actually a math problem, right and The thing is that um, I Realize that if you're doing these problems, right and you actually look at the math equation and you just plug it in that's Terrible like the editorial or whatever the thing is you're not gonna learn anything because there's a whole Idea of doing these problems for math problems is to come up with the equation Right because then you're not gonna improve at all even it no matter what you're doing no matter what you're doing Whatever problem if you're going to copy and paste a code you Might as well not even submit anything might as well don't not even attempt the problem because you're not learning anything Like the thing is when you do problem sets right when you need to do these problems There was one time when I literally spent like I don't know How many how many I'd like over a hundred submissions on one of these I don't I don't know where it is But there was there was definitely somewhere. Yeah, look at this. Okay, so I had like a ton of submissions for these, right? Wasn't a hundred, but there was a lot and below literally just kept trying over and over and over again to see like Beautiful permutation, but then later on I was able to get a seed, right? That's that's the that's how you should approach these problems Try whatever the thing you can do because in the end in a contest You cannot just copy and paste code copying and pasting a code. It is a terrible idea Don't even do it in like in production side if you're have a job as like a software engineer or anything don't even copy and paste code because generally Okay When you type out code Like when you type out code, right? You generally remember the code much better when you type it out I think this is the same thing when you do like take it's kind of the same thing as taking notes For the from a textbook, right by hand you generally remember it more when you take notes by hand, but I think it's the same Similar way in that if you actually type out the other person's code You're probably more likely to remember it So if you're gonna copy and paste code might as well type it out first But generally you should not copy and paste code. You should actually read it and try to implement it yourself. So yeah That's basically the thing and there's another thing I have to say is that before you even read the editorial You have to attempt the problem as hard as you can like try literally everything Like one way you try brute forcing if that doesn't work try another thing if that doesn't work I don't know try try coming up with a math equation if that doesn't work Try using a set try using a hash map try using two-point or try using dynamic programming Try whatever it is that you need to do in order to solve the problem and in the end if you still cannot Submit anything is still can't get anything after 10 tries or 15 tries then at that point I think it's the best time to give up and look at the editorial and once you read the editorial Try implementing it yourself. Do not I repeat do not copy and paste other people's codes If you still can't implement it yourself and you've tried at least another 15 submissions Then what you should do is you should go out and read other person's code But don't copy it read the other person's code then close it way today You probably forget the code try to implementing it yourself after another 10 to 15 submissions sooner later You will get a seed and that's just that's just how I think of it. It should You should in total maybe you should take like I don't know 50 submissions Like at worst at worst 50 submissions Ideally you shouldn't take like 50 submissions and I don't mean just like changing a tiny thing and then submitting it over and over again I don't mean by that they actually try like 15 different time different ways to try approach a result because you might be surprised I may be some way you solve the problem and in one way It's not actually the same same as how the solution solved it and maybe your way is better You know, maybe maybe there's ways worse than yours or maybe there was better than yours And then after you solve the problem you looked at it and like wow I could have done it this way instead. So that's the good thing about Why you should never copy and paste code. Just don't don't copy and paste code It's not good for you and even production side If you don't understand what you're copying pasting then what's the point, right? If you just copy and paste maybe you should register write a method or something another function Maybe a new class right in the production wise side. Maybe that's better, but never ever copy and paste code This is just my tip, but anyway, right comment subscribe. I hope you guys enjoyed this video. I Pretty busy right now, but yeah peace