Quote:
Originally Posted by Jinn
I work in software research and development, so my tips are going to relate to computer software.
Tip #2: If you think as program is behaving strangely, try to record what you do before (and after) it starts to act up. Before trying to seek assistance or reporting the issue, see if you can duplicate the error. People like me love to help, but if you can't remember what you did before it happens, it can be almost impossible to help. Things like clicks, mouse movements, keypresses, and even the information you entered is invaluable. Likewise, if you see an error message - copy it down VERBATIM. If you paraphrase it, ala "it said something was null...", it's very little use. Error messages are written so that someone who understands the program will have a better idea what is acting up.
|
To add to this - a screen shot can be just as good, because you can't stuff up copying the error message if you make a screen shot. Pressing the Print Screen button and pasting into a word doc is pretty simply done and can save heaps of time.
On the other side of the coin - if you're pissed off at a colleague, and have drafted an expletive filled email that is likely to sear their skin off, don't send it - go have a coffee then come back and revise it first... to add more expletives (just kidding).