Bullet Proof Programming is top on our priority list.

We feel that a program which works, and accomplishes the task, but is not reliable, (i.e. it sometimes *fails* at the task), is not much better than no program at all.

What is required to make a program "Bullet-Proof"?

• Making sure that the program understands what the user using it, wants to happen.
• Making sure that the user understands what the program is going to do, *before* it does it.
• Making sure that the program "Error Checks" each and every functionality, and this involves:
  • Checking to see that each action was accomplished perfectly
    • It must be assumed that each and every action on a computer system may fail
    • Most programs fail to error check properly, as it more than doubles the amount of work, programming-wise
    • Any other course of action is playing with fire, in our opinion.
  • Having a plan of action if the "checks" did not pass with flying colors, i.e.
    • Reporting to the user if there were any unexpected results
    • Possibly emailing the System Administrator of a system failure
• Finally, the program should test the results of the task with a real-time test, to show the user that the "job was done successfully (i.e. if creating a web site, the web site should be accessed in real-time at that moment, by the program).
• This way, the user can stand up after using the program, confident in the knowledge that the job was not only "done", but "tested", and it "works perfectly".

This uncompromising approach to program design ensures many hours of reliable use, free from questions and "failures".

Please email or call for more details.

Back to Previous Page