For solving hard problems there is the Rubber duck debugging methodology. But instead of a rubber toy, think of someone who can solve it. The catch is that tha

For solving hard problems there is the Rubber duck debugging methodology. But instead of a rubber toy, think of someone who can solve it. The catch is that that person is too expensive, so you will explain the problem so well and concise that it wont cost that much. Soon you will wake up a solution, or perhaps another approach, or better understanding of what you need to learn. The thing is don't switch to another complex problem. When tired, switch to easy tasks, documenting, or refactorings.