I place a document comment at the beginning of all my programs.
First I state which probes the program uses.
Then I state what features of what part the program will check.
Then I have setup instructions.
Lastly I have a log of which version of Pc-Dmis the program was created in, when, and by whom. This gets updated as "ran ok version.......date....person" every 6 months or so or more often when there is a revision change to the part I summarize what changes if any to the program along with "version. . . . date. . . who"
This practice allows me to open a program and easily see what probes are needed, what the setup is like, and when the program was last run quickly and without searching.
I also make it a habit to leave a bookmark at every loadprobe command in every program so I can easily skip to them for qualifying before running the program.
I place a document comment at the beginning of all my programs.
First I state which probes the program uses.
Then I state what features of what part the program will check.
Then I have setup instructions.
Lastly I have a log of which version of Pc-Dmis the program was created in, when, and by whom. This gets updated as "ran ok version.......date....person" every 6 months or so or more often when there is a revision change to the part I summarize what changes if any to the program along with "version. . . . date. . . who"
This practice allows me to open a program and easily see what probes are needed, what the setup is like, and when the program was last run quickly and without searching.
I also make it a habit to leave a bookmark at every loadprobe command in every program so I can easily skip to them for qualifying before running the program.
