I just read this article by Raph Koster about self-promotion in game development over on Gamasutra.
You should check it out - it's good stuff. You know, if you're a game developer.
What struck me most was the section about being kind to fellow developers. Sharing in successes and failures and generally being a nice person to the other people around you. So, I'm beginning a development blog to share in my success, failures, and interesting things I've found or am thinking about.
Raph says, "...there’s almost no advice as good as a signpost that says 'watch out, a flood washed out this road.'" Here's a little nugget of advice that I learned between the time I wrote the title for this post and the time I wrote this sentence:
Sometimes, you'll discover a huge bug in your game that you've already released. This might be a major, hard-to-fix bug, but, more likely, it'll be something stupid that takes two seconds to fix. It's really nice if you have the capability to fix it whenever, wherever you are, because otherwise you'll be pounding your fists against your head, berating yourself for not playing it through THAT FINAL TIME. So, even though I was at work, I was able to sync my latest build version of The Sinking Feeling from github, turn the script that I'd stupidly disabled back on, and re-up the builds to GameJolt. Then, I felt way better.
So, there's a little signpost for you. I'm not saying that you ALWAYS have to play ALL THE WAY through EVERYTHING you do EVERY TIME you change anything, but, by golly, it wouldn't hurt.
"...there’s almost no advice as good as a signpost that says 'watch out, a flood washed out this road.'"