3,853 reputation
1425
bio website
location
age
visits member for 3 years, 7 months
seen Jan 17 at 13:39

Feb
20
answered Content of Project Wiki
Feb
10
awarded  Citizen Patrol
Feb
6
answered Formatting PHP, what works more efficiently?
Feb
3
comment Is “as long as it works” the norm?
+1 I strongly believe that to rewrite something there should be clear evidence why do we need this
Feb
3
comment Is “as long as it works” the norm?
I especially like this line: The problem is that perfectionism leads to procrastination and procrastination leads to mediocrity.
Feb
3
revised Is “as long as it works” the norm?
added 1 characters in body
Feb
3
revised Is “as long as it works” the norm?
edited title
Feb
3
answered Is “as long as it works” the norm?
Jan
20
revised Do computer glasses work?
This isn't an essay/paper. There is no need for the leading "tabs."
Jan
17
comment Optimizing lifestyle and training
While we're at it, here are two links useful to someone curious about the characteristics of dyslexia: dyslexiamylife.org/signs_dsy.html and dyslexia.com/library/symptoms.htm
Jan
17
comment What are developer's problems with helpful error messages?
@moo The crux of the problem is that it isn't always obvious how much information is useful. The examples you provide seem rather obvious. However, it isn't easy to extend that to the general case.
Jan
17
comment What are developer's problems with helpful error messages?
@jon Contrast a generic error message for login errors versus more specific error messages that actually tell you what went wrong. e.g. "We couldn't find that username/password combination" vs "You entered an incorrect password."/"That username does not exist." I seem to recall a vulnerability in ASP.NET where the error message was actually useful in cracking encryption keys.
Jan
17
awarded  Nice Answer
Jan
17
comment What are developer's problems with helpful error messages?
@moo Ultimately, what I'm saying is that it's easy to criticize. (I know, I do it often.) However, I try to keep in mind that isn't necessarily easy to tell how much information you should include in an error message. There's plenty of times when I've had to back and output more detailed information than I originally anticipated while debugging. Also, there are plenty of times when an error message wasn't as useful as I had anticipated when creating it.
Jan
17
comment What are developer's problems with helpful error messages?
@moo You're certainly correct that context is important. i.e. developers would want to seem more details. However, even there it isn't necessarily cut and dry. A stack trace is most useful to the developers of the application, who are familiar with the code. While I do appreciate seeing that level of detail, such information isn't necessarily very useful to me as an end-user of the application, despite the fact that I'm a developer. It's the same basic thing with your library example. I would want more information that a layman, but there is still that possibility of having too much info.
Jan
17
comment What are developer's problems with helpful error messages?
Ah, yes, good point. That ever present concern of cost.
Jan
17
comment What are developer's problems with helpful error messages?
I suggest deep breaths, maybe some yoga & meditation. :) (That said, I know exactly how you feel.)
Jan
17
answered What are developer's problems with helpful error messages?
Jan
17
comment What are developer's problems with helpful error messages?
Wow, that's quite a rant.
Jan
16
comment The Singleton Pattern
+1 Generally speaking, globals are bad.