Aside from the last two, I would say the Script Guys' suggestions are unequivocally bad advice. Why? Because they are advocating a) relying on "default" behaviour; b) failing to make explicit their code's behaviour - for the purpose saving a line or two of code; or c) removing information from the script that would allow the script compiler and interpreter to help you out by throwing useful compile-time and run-time errors.

Beowulf's Script Standards:

  1. Always use WScript.Quit at the end of your script to explicitly show the reader of your code that you intend to quit now. However, never use WScript.Quit to prematurely dump out of a script to save yourself the trouble of properly structuring your code to test for abberrant conditions.
  2. Always define Option Explicit, meaning you must dim all your variables. Also, don't be lazy and dim 8 variables all on one line. One dim per variable is nice and easy to read.
  3. Always set objects you're done using to Nothing. Why? It explicitly declares your intention to both the run-time environment and to your loyal code reading fans. It also frees the memory immediately, rather than whenever the object goes out of scope. Also, it will allow the interpreter to do some work for you by throwing a run-time error, if there are inadvertant references to the no longer used object.
  4. Always indent code blocks, but never define a tab to be more than 4 spaces. I prefer 2 spaces myself.
  5. Comment your code as much as you want. If the next person to read/use the code finds it to be too much, it is easily removed. More often than not, the problem is not too many comments, but rather a dirth thereof.