go to the list of problems and sort them by the highest acceptance rate. you'll find the objectively easier questions there. the easy/medium tags are not as accurate More on reddit.com

Please ensure that: Your code is properly formatted as code block - see the sidebar (About on mobile) for instructions You include any and all error messages in full - best also formatted as code block You ask clear questions You demonstrate effort in solving your question/problem - plain posting your assignments is forbidden (and such posts will be removed) as is asking for or giving solutions. If any of the above points is not met, your post can and will be removed without further warning. Code is to be formatted as code block (old reddit/markdown editor: empty line before the code, each code line indented by 4 spaces, new reddit: https://i.imgur.com/EJ7tqek.png ) or linked via an external code hoster, like pastebin.com, github gist, github, bitbucket, gitlab, etc. Please, do not use triple backticks (```) as they will only render properly on new reddit, not on old reddit. Code blocks look like this: public class HelloWorld { public static void main(String[] args) { System.out.println("Hello World!"); } } You do not need to repost unless your post has been removed by a moderator. Just use the edit function of reddit to make sure your post complies with the above. If your post has remained in violation of these rules for a prolonged period of time (at least an hour), a moderator may remove it at their discretion. In this case, they will comment with an explanation on why it has been removed, and you will be required to resubmit the entire post following the proper procedures. To potential helpers Please, do not help if any of the above points are not met, rather report the post. We are trying to improve the quality of posts here. In helping people who can't be bothered to comply with the above points, you are doing the community a disservice. I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns. More on reddit.com

I strongly advise against learning Algo+DS or technology/language without reading up some theory first. As for algos, using "combat mode" trying to brute force the problems will only worsen the situation. You're not gonna know what to do and frustration will start to settle in. Learning technology by "diving straight in" often leads to using it completely against the intended purpose. Simple example, I've seen junior programers comparing Java strings using equality operator (==) instead of equals() method. When I asked why they do it this way, it turns out they haven't learned the 'equals' thing yet. If you try to learn a complex framework that way, things can go off the rails very quickly. A lot of those algorithm problems are daunting to you because you don't have enough exposure to them yet. Read Algo & DS Book, I recommend Algorithm Design Manual, it isn't as "mathy" as the CLRS. Google it, second link ;) Work through it, even if you won't understand everything, at the very least you're gonna develop anchor points in your mind that you can refer to later. You're gonna see a problem and realize "hmm... I think I saw similar problem in the section about bitwise operations". I'm not fond of youtube tutorials, especially if I intend to study a complicated subject. I want to jump straight in, instead of having to listen to drivel like "HEY GUISE IT'S STEVE "GoFuckYourself1337" SUBSCRIBE TO MY CHANNEL. WELCOME TO ANOTHER VIDEO TUTORIAL. TODAY I'M GONNA TALK FOR HALF AN HOUR COVERING MAYBE A ONE FUCKING PAGE OF DECENT ALGORITHM BOOK. BTW I DIVIDED THIS WHOLE TUTORIAL INTO ONE MINUTE SEGMENTS, EFFECTIVELY DESTROYING YOUR FOCUS AND FLOW. I HOPE YOU'RE ENJOYING WASTING YOUR TIME! YOU LIKED THIS TUTORIAL? DON'T FORGET TO FOLLOW ME ON REDDIT, TWITTER, INSTAGRAM, FACEBOOK AND MEDIUM. DON'T FORGET TO BUY T-SHIRTS WITH MY NEW MOTTO: "COLLEGE IS LIKE A TOILET, YOU GO THERE ONLY CUZ YOU FUCKIN' HAVE TO". Maybe I'm exaggerating a little, but I think video tutorials are too vague and general. More on reddit.com

I would just keep doing questions, try to train yourself into thinking more efficiently. Coming up with things like multiple pointers and sliding windows aren't out of the realm of possibility. So as you learn some, make sure you understand them, then see if they fit future problems. If they don't then use them as inspiration for coming up with your own algorithms, you may stumble upon ones that exist already. This way you train your brain to think it out instead of recall previous algorithms. That is ultimately the point, but never seems to actually work that way. There are some bread and butter algorithms you should know going in. Breadth first search, depth first search, sliding window type is good to know as you have seen, as well as unify-find which you will come across less often but is a great solution for when you do. If you get stuck, think of the brute force method, the one that would take the longest time but work. Then see if you can figure a way to make it more efficient, what items can you immediately discard from searching? Could spending O time for a sort help in the long run? More on reddit.com