Sometimes, I have that issue also. What I'm doing right now is sorting the problemset by number solved, and decide to solve the problems going down with no hesitation whatsoever. In my opinion, I think the reason why we don't want to write the code to a solution, etc is because we only want to choose problems that seem satisfying when complete. With this method, you're able to just blindly do problems and not think about the satisfaction that you get from completing the problem. Anyways, that was just my opinion, so see what you think. Hope this helps.

Take it like a game. I assume you like getting high ratings at Codeforces. That's why you get motivated to write codes for problems in a round. To keep myself motivated in offline practice, what I do is, I keep a google sheet where I update all the problems every day. By all I mean the problems where I feel a sense of achievement after solving it. Like I have learnt a new trick or I have gained more confidence by solving it. I try to keep the average number of problems solved each day to be 1.5 . So the days, where I solve 2 or more than 2 problems, I feel like that was a good day. The days where I solve 1 or 0 problems, I feel bad about myself and the next day I get more motivated to make up for the last day.

This is my game. I am competing against myself. The average value of number of problems solved is the "rating" for me. And I believe, if everyday I'm solving 2 problems that are slightly above my comfort zone, hopefully my comfort zone would shift upwards in a good pace.