I think what happens is this: when you're first starting, you tend to get buoyed along by a lot of small victories that give you a big rush. Even something simp

I think what happens is this: when you're first starting, you tend to get buoyed along by a lot of small victories that give you a big rush. Even something simple like getting a program to compile gives you a bit of a high. All those small victories make it easy to keep going, and you have a definite sense of progress. Once you're more experienced though, those victories start being fewer and farther between, and progress becomes less obvious. Nerdy analogy, but it's like gaining levels in an RPG. The first 10 or 20 are easy, and then each progressive one becomes more and more grind. Maybe you could get some of that "rush" back by setting your goals to non-technical things for your technical projects? IE, instead of "learn this", maybe "launch this by X" or "get X many users"? Maybe what you need are small measurable milestones to hit. The other thing is, sometimes it just helps to have some sort of "dumb" activity that can get you into rhythm. Like, when I'm trying to get into coding, a lot of times I'll just sort of start cleaning up code, writing some simple comments, and refactoring things, because it's sort of a brainless activity that can get me going. YMMV, but it helps just to start being active and ease into the hard things.