A little bit of History, Introduction

All things considered, I guess a lost week is none too significant.

Going to a new accountant, we have recently (up to the present) been going through seven and a half years of corporate paperwork, which reminds us of how long that has been and how much has happened during that time. That extends back to when our association with Goodsol Development involved piecemeal artwork and no programming, and the word “terrorism” was not uttered in every news broadcast.

Thinking back, though, it is somewhat surprising to realize that this company had so many years of history before 2001, with so many projects and stories having already occurred by that time. My personal programming history goes back 30 years (later this year). The history of my company reaches back more than 26 years, and we have been full time for 13.5 years. The corporation itself has been around since March 1996, and we have outlasted almost every employer I previously had, not to mention the vast majority of companies in the game industry.

This has been my full-time employment since I resigned from Spectrum HoloByte in December 1994, which was over 700 weeks ago, so a “lost” week here or there, representing less than 0.15% of this time, is probably not a disaster.

As we all (should) know, though, one cannot make up for a slipped schedule solely by working harder, especially when a deadline has already passed, so we realistically redefine our schedule and continue to work intelligently and diligently.

Next: Part I: The Founding

The Week that Wasn't

Good Riddance to the past 7 days.

Have you ever had one of those days where you seem to be going in several directions, always doing something, but then at the end of the day find yourself unable to pinpoint what you actually accomplished? Have you ever had it extended to a full week? Well, now I have.

This was supposed to be a very productive week, with most of the family out of town, but what started out promising resulted in a whole bunch of… I am not really sure.

Perhaps it was the spam. I received more than 21000 spam messages in only 10 hours. (I stopped tracking it after that point.)

Perhaps it was the slipping deadline. I have been feeling an unhealthy amount of stress lately, which is not exactly conducive to productivity.

Perhaps it was the partially fallen tree. We finally had all the dangerous parts removed, but there is a reason that the sounds of chainsaws and heavy machinery (just outside the office window) are not featured on relaxation tapes.

Perhaps it was the uncertainty. Several things in which I am involved (often peripherally) have had crises arise (some real, and some manufactured), including one that is affecting several thousand of my dollars.

Perhaps it was the damn telephone. Every professional person (lawyer, accountant, etc.) we have had contact with in the last few months, and then some, chose last week to telephone. Throw in five more important calls, some technical support for extended family, and a healthy dose of telemarketers, and I am ready to throw out these phones.

Perhaps it was the lack of my usual support “staff”. The post office box did not empty itself, and the bank failed to anticipate and handle my financial needs alone. Meals required effort on my part.

Perhaps it was my commitment to quality. It seemed like every time I had something almost completed, there was a niggling little issue that required a minor change, and another, and then another… I cannot abide shoddy code. Of course, this is one thing I do not intend to change.

Whatever it was (probably a combination of everything above and more), last week was a wash. I am drawing a thick vertical line right here after the month of June. From this point, I simply move forward.

One crisis at a time…