Make the error useful, and save the support call
source link: https://ayende.com/blog/195138-B/make-the-error-useful-and-save-the-support-call?Key=bde75f45-7905-49d8-8465-53ceeaea9117&utm_campaign=Feed%3A+AyendeRahien+%28Ayende+%40+Rahien%29
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Comments
18:10 PM
Going on that direction, can you imagine how world would look like if c# NullReferenceException contained variable name?
20:24 PM
React does a very good job of conveying information like this: in the dev builds, when there's an error, there's almost always a phrase like "did you forget to do <something we expect>"
I agree with this completely and have started doing this as practice as well in error messages.
06:16 AM
Rufik,
In almost all cases, just the line number is sufficient, but yeah, that can be a huge benefit. I remember looking at the same error in C++ and C# two decades ago, and NRE vs. Access Violation @ 0x382381 made me switch to C#
06:43 AM
Rufik, the world would look much better and easier. It'S a massive problem that our error reporting infrastructure is so bad - yes we do have exceptions, but they are not realle up to the task in a lot of cases. E.g. in case a NRE with a variable name would help but does not explain why its null. Would be so much better when we would be able do understand the why easier.
Join the conversation...
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK