I’m more concerned about the time sink that comes from writing down what I’m doing and what I’m going to do, instead of just doing what I’m going to do. I’m a firm believer in not micro-managing, and I feel like I’m micro-managing myself when I’m explaining how and why I did something. If I come upon a mechanic that I think is interesting or exceptional, I’ll most likely take note of that, and talk about it and how I came to use it. I feel as though I would be doing it a disservice by not giving it the due attention, and just mentioning it in passing in a development blog post.
That might be complete hubris, but I don’t have that many great ideas, and when I think something is a good idea, I want to note that. When I finally came up with the AI that worked for Crosstown Smash, I made sure to comment the hell out of it so that I knew what I did, and could come back and tweak it as I needed. Seeing as how my marketing budget is nonexistant, development blogs offer the opportunity for folks to see into the store and become invested in a project before it is completed. That’s the kind of interest that would cost millions.
I guess I better get started.