[prog] How to ease the torment of users and users themselves

Here you write, let's say, some kind of software. Not that you write for yourself, but also for colleagues or for a company. And maybe for sale. Only while you are doing this alone - both the Swedish and the reaper himself - that is, you have to answer user calls as well. That it does not work, it is ...

“Errors”, what users see - he himself into the program and stuff it - messages ie :) not the mistakes themselves. You know that if a place has ended, you must immediately inform the user (out of the kindness of his soul) - “there is no place!”. And then suddenly someone calling you with the words "it wrote something to me here, but I did not read it - in general, nothing works!". You think - really can not remember what they wrote?

Laaadno - insert the number “12312 No place!” There - and you say to everyone - write down the number.
')
Well, the call is again - the situation is better, but we are still guessing what happened to him ...

At the same time, everybody does not always even know what can happen and messages like “Error! The whig knows what, but for some reason, the variable X is not 5! ”- which seems logical in general while you enter it in the program, but completely enrages when it is read to you on the phone (well, you can of course make the dialogue so that “Copy the error to the clipboard” or simply select the text there, but no one does).

So that's what it is all about - it’s very useful (for your nerves) to do progs so that the error message output function is the same. At the same time through it it was possible to set 2 messages - for a person (understandable) and for oneself (detailed). Yes, and the level of debug-nosti - what to write, what is not and in what log. Then write not only errors, but also events (they opened the file, closed it, clicked something).

Now, if something goes wrong - just ask to send a log and everything is clear at once. :)

For the period of software implementation - you leave the maximum logging of everything. Then everything is less with the ability to turn on if necessary, if something is not caught by the tail for a long time :)

ps. Also, do not forget about ... and that your software can be deep to the light bulb to users :) especially when it “prevents work (sleeping at work;)”.
pps. and in general, errors not for users are shown (at least a part), but also for amines or developers - it is better not to forget. :)
ppps first post without kata - to attract