Sort:  

The FIRST step to a software package is to talk to those who actually use the software. Ask about the problems they see, and bring up difficulties you see, and ask them what THEY think. Sometimes what the programmers see as a problem does Not bother those actually using that program. Correcting a non-problem is a poor use of time. Writing code no one wants; is an even poorer use of time!

Launching it without testing is a terrible way to test software. We always alpha tested our software at a few above average locations; before we repaired problems, and did a limited beta test. One more iteration of problem repair, and we had a version 1 software. This always worked well, and some of the software ran without changes for years.

After I figured out the programming, I was done with the games. They have some now that use a lot more computer power, and it might might be fun to destroy some of the kids with their gaming computers, by brute force, ROFLOL! Hooking it to a big screen TV with a obscene video card, and a chair mounted joystick and foot keys might be amusing.

>:(

hahaha! sir smithlabs! that idea about destroying the kids with your bank of computers is hilarious, that would be a hoot!