Version 1 of Tips for writing quality software

Updated 2003-03-20 19:15:58

THIS PAGE IS BEING EDITED. DO NOT EDIT! THIS MEANS YOU! HEHE ;)

  1. Keep procedures short Why you may ask? Because rather than seeing 200 lines of stuff that does X, you see a command call saying do X.

2. Use descriptive names for variables and procedures