My read on the quote is the problem comes from the "being stuck" part, not the "problem solving" part. For example, finding a corner case bug in a library you

My read on the quote is the problem comes from the "being stuck" part, not the "problem solving" part. For example, finding a corner case bug in a library you rely on is generally unpleasant. Sure, part of problem solving may involve either fixing it, working around it, or choosing another library. Before choosing an option, it makes sense to weigh the costs and benefits. To make a long story short, if enough things pile up at the same time, it can feels unsatisfying because less new user-facing benefit is being created. One solution, if it works for you, is to take a balanced view of productivity means; namely, a blend of short- and long-term value.