# # Useless Error Messages
APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

Useless Error Messages

I've removed advertising from most of this site and will eventually clean up the few pages where it remains.

While not terribly expensive to maintain, this does cost me something. If I don't get enough donations to cover that expense, I will be shutting the site down in early 2020.

If you found something useful today, please consider a small donation.



Some material is very old and may be incorrect today

© July 2003 Tony Lawrence

We accept this as ordinary: error messages are nearly useless.

We don't even expect that the error given by some misbehaving system is accurate. I'd guess our confidence level in that hovers around 80% or so: it's pretty likely that whatever we got will eventually lead us to a solution, but there's no guarantee, is there?

We certainly don't expect that the error display will help us solve the problem. We've all been through Microsoft's near useless "troubleshooters" and we know they are NOT going to help us. No one else is any better. Maybe, if you are very, very lucky, the programs Help system might lead you to an answer, but we don't get outraged when it doesn't help us at all, do we?

Nope. We are conditioned to accept that error messages aren't particularly reliable or useful. When an error message actually is spot on, and tells you what you need to do to fix it, we are (quite naturally) mistrustful. In this case, the error gave the specific remedy, but the recipient went to the newsgroups, either to double check (and who can blame that instinct?) or because they barely even read the message at all, which is another habit that useless messages instill in us.

It's hard to write good error messages. After all, if the programmer EXPECTED this bad thing to happen, they'd usually do something to prevent it. Still, I think we could do better than we do. Programmers do have more than simple numeric messages to choose from, and if they are going to use numeric messages, should at least tell us whether this is a system error number (we could look that up for a clue; see Numeric Unix Error Messages) or something they made up. If they are using their own errors, give us a pointer to a web site that lists them: at least give us a chance.

Wouldn't it be nice to be suprised if an error message WASN'T helpful?

See Numeric Unix Error Messages also.


If you found something useful today, please consider a small donation.



Got something to add? Send me email.





(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

->
-> Useless Error Messages

1 comment


Inexpensive and informative Apple related e-books:

Take Control of Parallels Desktop 12

Take control of Apple TV, Second Edition

Take Control of Upgrading to El Capitan

Take Control of High Sierra

Photos: A Take Control Crash Course





More Articles by © Tony Lawrence




---January 19, 2005

I agree! The bad error messages transform what should have been a half-hour bug hunt to a full-on head-smashing two day marathon of wasting your life away and asking "WHY!!"



------------------------


Printer Friendly Version

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us


Printer Friendly Version





It is difficult to free fools from the chains they revere. (Voltaire)




Linux posts

Troubleshooting posts


This post tagged:

Blog

Linux

Programming

Troubleshooting

Unix



Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode