The topic of this post reminds me of the 60’s Batman narrator.
HamQuest and I have a rocky relationship.
Periodically, I look back at the code base, and see a number of areas in which I can improve things.
I get inspired to do so.
After a while, the things that I want to do to make the game more configurable or better organized or generally more engineered pile up into a insurmountable list of issues to resolve.
Eventually I abandon working on it for a while, and move on to other things.
I imagine the curve plotted by my desire to work on HamQuest (or really, any long range project) might look something like a graph of cos(x).
Since there are endless cycles of this, the graph is really cos(x+k*2*pi), where 0<=x<=2*pi. And k is the number of cycles that have taken place already.
So, I appear to be heading for x=2*pi, which means the cycle will reset, and I will do some work on HamQuest.
Which is actually a good thing, because my “x” value for Island Interloper is rapidly reaching “pi”, or the minima in interest level.
Is it possible to have a few projects that hit peaks and valleys in interest level in such a fashion that I simply need to switch between them?
So, why a decrease in interest in Island Interloper?
A couple of things.
4) I think that the “correct” client to use is SilverLight, with a swappable back end that can either be used to store data to isolated storage or through the web, and this layer would be abstracted so that I could use the iso storage one during development, and the web one in deployment. Plus, C# has a real debugger.