A friend of mine has been talking a lot about a game project he’s been working on lately. In general, I love talking about coding projects, even when they aren’t mine. I find it sets my mind spinning in fun and interesting ways. When I’m not talking about one of my own projects, I mostly hope that I am a useful source of ideas for the person I’m listening to. There is another side effect though.
Talking about other projects, and sharing in the excitement that other people have for their projects is great, but I end up missing my own projects that have stalled. I describe this longing for my own coding projects as “itching to work on them.” Thankfully there isn’t any actual physical itching involved, but conversations spawn ideas. Ideas in turn spawn problem solving. Problem solving causes a desire to put these theoretical solutions to code.
The last time I posted anything here was nearly a year ago now. In that time I’ve worked on several other projects and as a rule, I’ve stalled out on all of them. I’m not sure why I do this, but I think it has to do with getting to a part of the code that is hard or boring or otherwise just not something I want to work on. The solution is to simply stop until I wish I was working on it again. That time is fast approaching again.
To that end, I’ve updated my development tools to their latest versions for probably the 3rd or 4th time since I stopped work on QubeKwest. I’ve done some thinking about my library choices and I’ve devoted enough time picking over the code I’d already written that I found some things to correct about my project documentation. The itch is returning in full force, and I expect to resume working on the project soon. Hopefully, “soon” really means soon this time.