why do error messages go like “install failure error 0001” instead of telling the user what’s wrong
In: 1812
Someone in your class in school keeps stealing books, but nobody can figure out who.
Your teacher can’t watch everyone at once, especially since everyone isn’t doing the exact same thing at one moment.
Your teacher sets a rule in where you have to put a stamp in your planner whenever you enter the library, you also get a reward **if** you catch someone not returning their book or stamping.
At the end of the day, the teacher checks everyone’s planners and is able to narrow down, who has read a book, and from there who may not have returned their book.
The teacher can do with this information many things one of these is prevent anyone on a particular day from going to the library if a book was lost the prior day and they had a stamp and seeing if anything changes.
Same with a programmer, error codes like that usually have some defined meaning the system architect understands inherently or by reading the documentation; and they thus know where to look in millions of lines of code; to find what needs to be changed.
If the error occurs in multiple places, they can isolate the issue by testing those areas independent of one another or within the same environment while substituting a method/function as a pass-through(it doesn’t actually do anything or it gives a hard-coded response).
Usually errors that are displayed like this are catch alls or pre-defined catch’s, meaning something went wrong somewhere here, but we aren’t particularly sure either what caused it or even rarer what the error is otherwise it would be fixed prior – and potentially have a plain english definition like “Incorrect Password”.
Latest Answers