The Shareware Industry Conference gets underway.

Today, the premier conference about marketing software online, the Shareware Industry Conference, got started in Denver, Colorado, with a reception sponsored by Protexis. SIC 2006 officially runs from Thursday, July 13th [tomorrow] through Saturday, July 15th, but with this opening event and a breakfast on Sunday morning, it actually encompasses at least part of five days.

The Shareware Industry Conference is presented by the Shareware Industry Awards Foundation (SIAF), and this is the 16th annual event. The SIAF Board of Directors consists of five people: Michael “Doc” Callahan (Dr. File Finder), Gary Elfring (CD Ship), Harold Holmes (Lincoln Beach Software), Sharon Housley (NotePage), and Paris Karahalios (TRIUS). They put on a great event each year.

I arrived in Denver after 20 hours of driving, straight through, with my wife/partner and our two kids. We could have (possibly) made it a couple hours sooner, but toward the end of the journey we were stopping frequently in order to keep our circulation active (and my eyes open). The timing was just about perfect, as we checked in at the hotel immediately and had enough time for a nice lunch before registration (foregoing a nap).

Registration went fairly smoothly, despite a small, yet amusing, communication problem caused no doubt by my lack of sleep. We received our badges and “goody bags” and proceeded to our hotel room for much-needed showers. Getting registered before the conference officially begins is always more convenient, and it is especially nice when everybody at the desk knows you and has your stuff ready before you get there.

At the reception, we spoke with many friends and acquaintances (some call it “networking”) and generally had a good time. Protexis was a good host, allowing everybody a forum in which to actually talk, with good food, and at least in my case, ample drink tickets. I also got to meet for the first time, in person, a few online acquaintances: Dan Hite (Auction Sentry), Jean Cyr (Dillobits Software), and Association of Shareware Professionals Director Henk Devos (Whirling Dervishes), who made the trip over from Belgium. As usual, I ended up talking with somebody (Henk, in this case) until we were last ones at the party.

The SIC is truly underway now. I am looking forward to the whole conference, and am especially anticipating my presentation (Practical Interface Guidelines: Things they did not teach us in programming class) on Friday and the Shareware Industry Awards Banquet on Saturday night, when Pretty Good Solitaire is nominated for an SIA in the ‘Best Non-Action Game’ category.

Today is recognized as the 230th birthday of the United States of America.

This mostly content-free Fourth of July message was brought to you by the proud folks at Digital Gamecraftâ„¢ and SophSoft, Incorporated, which has been working to develop quality games for more than 10% of the lifetime of its host country.

Enjoy the fireworks!

I just got bitten by another Microsoft interface bug.

Since my laptop is not my primary development machine, I have it configured slightly differently than my other systems, to give me a better feel for the way that our customers would normally experience Windows. I left it setup mostly as it came from the manufacturer, albeit with much of the automatically launching software removed.

One of the things that is different with this system is that Windows Update is configured for Automatic Updates. When I turn on the laptop in range of my wireless router, it connects and retrieves any updates that Microsoft deems important. This is the standard behavior for many, if not most, Windows users.

Last night, I turned on my laptop and started a large file transfer. Of course, Windows Update decided that it needed to update my system at the same time (slowing the transfer). That was to be expected, and it was not really a problem. However, the system update required a restart of Windows to be complete, and that exposed another design flaw.

During the file transfer, a dialog box popped up:

Automatic Updates
Updating your computer is almost complete. Your computer needs to be restarted
for the updates to take effect. Windows will restart your computer automatically in
m:ss minutes.
Do you want to restart your computer now?

The m:ss was a minutes and seconds countdown, starting at 5 minutes. After I noticed the dialog box (having been working on my main development system), I ignored the ‘Restart Now’ button, since I was still transferring a file. I pressed the ‘Restart Later’ button.

Lo and behold! After only 10 minutes, the same dialog reappeared. The expectation of my previous selection was that it would go away and not bother me again, and I would restart it on my schedule. Since I was still in the middle of the file transfer (I told you it was large), I was forced to repeat my previous action, and to do it within a specific time period.

One of the fundamental rules of interface design is to maintain consistency of behavior and not act contrary to user expectation. A ‘Restart Later’ button on almost any other software update, including those from manually using Windows Update, dismisses the dialog permanently and puts the onus on me to restart the system. This action violates that principle.

It is not too difficult to guess what happened next. The transfer continued for ten more minutes before having the dialog popping up again, demanding unwarranted attention. At this point, I was very annoyed. In my mind, all I can hear is the sound of an obnoxious child from the back seat, repeatedly asking “Are we there yet? Are we there yet? Are we there yet? Are we there yet? Are we there yet?” You get the idea.

Another very important rule is to never perform a potentially destructive action without explicit instruction or confirmation from the user. This rule was also seriously violated…

If somebody in the above situation is using the computer for a time-consuming task, such as a large file transfer, and he is called away by, say, nature, Windows Update causes trouble. After dismissing the dialog box several times, one failure to be in the room for whatever reason results in the system rebooting, thus invalidating the process in progress. One may be forced to completely restart the task after having it aborted by an unwanted reboot, which hopefully does not corrupt anything.

With a company as large as Microsoft, and a product as comprehensive as Windows, it is not surprising that there are some areas of brilliance and some areas that are just lousy. It is, however, quite disappointing when one finds the latter, and worse when it has a negative impact on productivity. The best an independent game developer can do is to learn from both.

Well, that and complain.

Jon Stewart has taken notice of the absurdity of anti-game hearings.

Recently, on Comedy Central‘s The Daily Show, Jon Stewart had an amusing segment about the attempts to vilify video games by our government. In particular, he focused on the hearing held by a House of Representatives subcommittee on June 14. Individual clips of comments by legislators are shown (with appropriate commentary).

The entire segment is available for viewing here. (Thanks to Gamasutra for the link.)

I find it rather telling that in one of the clips where a legislator, the “father of three young boys”, expresses concern about video game content, he seems to actually struggle to remember the ages of his own children. Stewart’s commentary at this point is dead on accurate. It would be even funnier if people did not seem to take these idiots seriously.

Seriously, the House of Representatives is filled with insane jackasses.
— Jon Stewart

The shareware industry’s premier conference is just around the corner.

On July 12, the Shareware Industry Conference gets underway in Denver, Colorado. This will be the second year there, as it traditionally stays at the same venue for two consecutive years. There are rumors that it will be in Denver in 2007 as well, which would be the first time that a city has had it more than a couple times since the original Summer Shareware Seminar left its Indianapolis home. Of course, we will only know that for certain once we check in and read the back page of the conference booklet.

This will be my sixth time attending SIC, now in its 16th year. I mistakenly decided not to go to the very first one (back in 1991) for silly reasons, and I now seriously regret having failed to attend. I recommend this conference to anybody who has an interest in marketing and selling software online, regardless of whether or not he or she uses the term “shareware”.

It appears that, for the first time, I may be speaking at the conference. I am tentatively scheduled to give a presentation entitled, Practical Interface Guidelines: Things they did not teach us in programming class. I am not really sure that this will happen until the SIC 2006 Schedule of Events lists my talk (presumably on Friday at 3:30pm). We shall see.

Anyway, for anybody attending SIC, I should be wandering the lobby areas and attending sessions for the duration. I should also be at all the official events, including the ASP luncheon, as well as the unofficial AISIP offsite lunch. I look forward to seeing friends and meeting new people, so be sure to say “Hi!”.

The “beautiful game” looked pretty ugly today.

After watching the United States vs. Italy game in the FIFA World Cup 2006, I am stunned at the lousy officiating in the game. The referee was probably the worst I have seen, including when I coached soccer in a youth recreational league. There, the refs were high school kids who were still learning, and we coaches sometimes had to help with finer points of the rules, but any of them would have done better.

For those who were not watching the game, the referee gave an Italian player a Red Card (game ejection) for deliberately elbowing an American player in the face (and drawing blood). This was well deserved, and it left the Italian team with only ten men. However, at the end of the half (last minute), the ref gave an undeserved “equalizer” to a US player for a common foul (if that), taking one of our productive players out of the game. Then, only two minutes into the second half, he removed another US player on a questionable call, dropping the team to only nine.

Despite the fact that we were (undeservedly) a man down, and the statistic that no team with only nine men has ever scored a goal in World Cup history, the Americans managed to bury one in the back of the net to take the lead on the scoreboard, 2-1 over the Italians. Unfortunately, the referee decided to make a late offsides call against a player not involved in the play, taking our “go ahead” goal away.

When my players used to complain about a poor referee or bad calls, I always advised them to take the refs out of the game by scoring goals. After all, if a game is not close, then a bad call or two cannot make the difference. However, when a referee blows three major calls, taking a team from having an extra man to being down a man and denying a legitimate goal, it really is too much to overcome, especially at this level of play. The United States team played valiantly, but had to settle for a 1-1 tie.

After the match, American television revealed its discovery that this particular referee was not allowed to officiate in the last World Cup because of unspecified “irregularities” that were so egregious that other refs complained about it. So, not only were his calls terrible (and, in my opinion, deliberately biased), but he has a history of such problems.

The big problem with this whole thing is that everybody loses in this situation. The United States was robbed of an excellent chance to win this game, and the Italians, too, were denied a fair fight. The fans were ripped off, as the outcome of the game has more to do with one incompetent referee than anything else. FIFA takes a major credibility hit when they were already on the defensive about the poor officiating (and too many cards, in particular).

I believe that a very exciting game was marred by the malfeasance of one individual, and I am looking for FIFA to take swift and decisive action against the referee. There is nothing that can be done about the game outcome but to move on. The United States played very well this game, and every team in the group still has a chance to advance to the next round.

The situation is this: Both remaining Group E games will be played simultaneously on Thursday, June 22 at 16:00 local time (10:00am Eastern US). The United States must win against Ghana (who scored a major upset today) to have a shot. If that happens and Italy wins over the Czech Republic, then the US advances. If the other game is a tie or a loss, then the US has to completely crush Ghana, by five or six goals. That is highly unlikely.

I have an official Italian team jersey that I would not wear today, but I can assure you that I intend to wear it on Thursday. Go USA! Go Italia!

Ya learn a lot more about life from the things you’re not supposed to do.
— Delbert McClinton

How Not To: Respect Your Customers

A while ago, Microsoft added a new “high-priority update” for Windows XP to their Windows Update site. Note that, since it is marked as a high priority, this particular update will be automatically downloaded and installed on all Windows XP systems configured to use its Automatic Updates feature, so most users will have no idea that it was installed.

This little update is called, euphemistically, Windows Genuine Advantage Notifications, and it is described in KB905474. It is an application that checks to see if you have a pirated copy of XP and, if so, attempts to sell you a legal one. In Microsoft marketing department language:

“The Windows Genuine Advantage Notification tool notifies you if your copy of Windows is not genuine. If your system is found to be a[sic] non-genuine, the tool will help you obtain a licensed copy of Windows.”

According to the web page, if you voluntarily (knowingly or not) download this little application, and it detects (correctly or not) that a copy of XP is not genuine, it 1) notifies you at every logon and tries to sell you Windows, 2) puts another icon in your taskbar (“an icon will be available…”) with balloon notifications, and 3) locks your desktop to display a message about software counterfeiting.

Of course, I spend hundreds of dollars each year to have the latest, and fully licensed, Microsoft operating systems, so assuming this works correctly and recognizes my genuineness, what does this do for me, a paying customer? Let’s see. It runs another application in the background, hidden from me but stealing processing time. Oh, Goody! It also cannot be uninstalled.

In other words, this “update” treats me as a criminal and puts my machine at risk of the whims and mistakes of Microsoft. It provides me nothing of value whatsoever. This may be good for them, assuming that anybody using a pirated copy of XP gives a damn, but a legitimate customer should not be subject to such treatment. Oh, sure, somebody who bought their machine from a dishonest vendor who gave them an illegal copy may get caught, but that does not justify an uninstallable application being surreptitiously added to a system.

The story could end there, but it does not. Yesterday [June 14, 2006], Microsoft updated the application, so even those of us who told Windows Update to quit notifying us of this, now have to do it again (“… until a new release of the Notification Update is released”). I do not use the word “hide” in this respect, because it does anything but hide the update. Instead, every time I open Windows Update, I am greeted with the following message:

“You’ve hidden important updates
You’ve asked us not to show you one or more high-priority updates but your computer might be at risk until they are installed.”

This is a lie. This update is only “important” to Microsoft; it is meaningless (at best) to paying customers. Classifying it as “high-priority” is inappropriate, and suggesting that my computer is at risk without it is simply wrong.

Do not get me wrong here. I despise software pirates, and I would like to see more prosecutions and appropriately severe punishments for willful copyright infringement. I also like Microsoft, earn a living using their software, and have even worked on a game for them, so I am not bent on their destruction or anything like that. However, I cannot help but feel insulted, first, and then just angry at such behavior. This is definitely an example of how not to respect paying customers.

Right now, I am going to work on a Macintosh, writing a game for Apple OSX. I am currently feeling more motivated to do so, far more than to work on any of my Windows games at the moment. Seriously.

It is quite useful to learn from the mistakes of others.

When my business partners and I decided to devote full time effort to our company, we had seen lots of errors in our combined experience in the game industry, as well as from business in general. We thought that we had witnessed enough pitfalls that we could succeed merely by avoiding the many mistakes that we had watched others make. Alas, there are always new and interesting ways to screw things up, and we stepped in a few ourselves.

I have long believed that the best way to learn something is to make a mistake at it, and the greater the disappointment or embarrassment (or even pain), the better the lesson. A child does not necessarily remember all of the words he got correct in a spelling bee, but he always knows how to spell the one word he got wrong to eliminate him.

Of course, it is much harder to get people to take a written or spoken, rather than experienced, lesson to heart. Nevertheless, I will face this challenge and attempt to illuminate some of the pitfalls one may want to avoid to make excellent games, run a successful business, or simply have an enjoyable and respectable life.

Every once in a while, I will post a true “How Not To…” story showing a mistake made by someone, whether an individual or an organization. These lessons will be prefixed with “HNT:” in the title and will describe the incorrect method of accomplishing something. I may or may not change or omit names or details to protected the guilty, depending on my mood. The correct or appropriate solution(s) will be left as an exercise for the reader.

Note that if you recognize yourself in one of these scenarios, remember that it is an opportunity to improve. If people say negative things about you, there are two basic possibilities: 1) they are right and you can learn, or 2) they are full of it and can be ignored. Decide honestly which category applies, and then move on.

Microsoft is a favorite target of many, but one particular recent practice has ticked me off enough that it was time to write the first of these lessons.

Please link to this post. [permanent link]

After a few weeks of quality, here are convenient links to each of the separate articles:

Quality: An Introduction
Quality: The Process, Part I
Quality: The Process, Part II
Quality: The Process, Part III

One can following the links at the bottom of each section to read each article in its entirety.

Whew!