Plan "B"

I just got another call from one of my customers. I write programs for use internally in my company. Then, I get to support them for the rest of my natural life. I suppose if I got hit by a bus, they'd hook me up to tubes so I could support my applications. BTW, nobody else could do it because I'm lousy at documentation. Too busy.

So, I get these frantic phone calls every once in a while, "The system's not working! The system's not working!" They continue like this...

Me: "What seems to be the problem?"

Them: "The system's just not working."

Me: "What do you mean 'not working'?"

Them: "I mean I can't do anything."

Me: "What were you trying to do?"

Them: "I was just trying to log on, and it doesn't work."

Me: "Do you get an error message?"

Them: "Yes."

Me: "What was the error message?"

Them: "I don't remember. The system's not working!!!!"

Me: "I need to understand what the error is, so I can fix it. So, if you can reproduce the error, I'll have a better chance at fixing it."

Them: "Well, every time I try to log on, the error happens, and I can't do anything."

The lightbulb goes off. I'm 99.9% sure I know what the problem is now. The problem seems to be between the keyboard and the chair.



Ultimately what happens is the user locks themselves out of the system, and has no hope of reentering even with the correct password. I make my error messages short on purpose - in the hopes that they will read this short little message