Reply to post: Check for "errors" and make sure!

Stick to the script, kiddies: Some dos and don'ts for the workplace

Herby

Check for "errors" and make sure!

Yes, they are wonderful, but scripts should be through. Many a time I have looked at scripts only to find out that the writer is lazy n the third degree. Some examples:

Routing stderr to /dev/null

chmod 777 <file> just because it solved the "problem".

Leaving temp files floating around

Such things as "cat file | command"

No explanatory comments on what is going on.

Scripts that say "Doing xxx" when they are actually "Doing yyy".

scripts that mimic standard commands in weird ways with errors themselves (see above)

right

Unfortunately this happens with all to much regularity, and the "clean-up" usually find an error undiscovered that will really much things up if executed in the wrong/right way.

So we all fix them drawing from experience, and life goes on. (*SIGH*)

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon