Whew! It's been non-stop around here getting ready for my leave for Japan. From preparing to move, getting stuff into storage, seeing friends I will not see for a while, and taking care of my contingency plan for work, I've been busier than ever. This is all good, and especially great that I've been able to spend time with friends I don't see as often as I'd like. The downside of this is that I've had very little time to play the hermit and get in some good work on my game project.
This is killer to the progress of a programmer. When I'm at my peak, I can program for hours. I get inside the code, and understand everything that's going on. If there's a bug in the code, I can generally trap it quickly enough and address the issues there. Not so true when I can barely squeeze in an hour at a time! Since I'm doing all the programming and testing, I'll find that I'm fixing one thing, but without the proper time to check other related items, I've found that this can let leaks and breaks and all the other nightmares of programming out of the bag.
This is all part of the normal programming schedule of the novice: finding out the hard way that your plan wasn't as well thought out as it should have been. Squirrel Eiserloh, technical director at Mumbo Jumbo (Dallas) was quoted on the hiring pamphlet at this year's GDC saying that extra time spent reworking and debugging is a just a result of poor planning. Couldn't agree more! This will become the new mantra for me as I continue to push forward into this field.
More news on the game project will be revealed here over the next few months.
No comments:
Post a Comment