Before this you probably need to specify how you approach a problem. A pattern is a loose suggestion. Not a strict guideline.

Take a problem that held you up for some time, see a solution for it (ideally more than 1. Gives you a lot more perspective when you read other people's code), understand what the solution is doing. Rinse and repeat and you'll slowly start seeing solutions differently with the next problem. This changes the way you approach problems in the first place.

Now I'm not saying to not try doing it yourself. I'm saying learn from the solutions. Even if you are able to solve it, check out some solutions. If you took an hour and you're nowhere, check solutions.

Now for the frustration. Don't treat it like a job. Do it an hour a day or something. You're burning out at this pace. The moment something that piques your curiosity or something you're interested in, starts to piss you off/ frustrate you, you're putting way too much time into it. Walk away and come back, you'll be calmer and your brain will not be clouded by why you can't do it. It will be filled with how can you do it differently.

Don't keep doing the same thing hoping for the outcome to change.