tag:blogger.com,1999:blog-28351195.post8727077726233047365..comments2007-04-14T23:14:17.813+02:00Pawel Brodzinskihttp://www.blogger.com/profile/04369257211504152485noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-28351195.post-67982090210876479912007-04-14T23:14:00.000+02:002007-04-14T23:14:00.000+02:002007-04-14T23:14:00.000+02:00That's not about being lazy. That's about user experience. <I>User</I> experience, not <I>developer</I> experience. <BR/><BR/>Yes, the chances are good that the second message will help me at least a bit to find out what went wrong. But that's only because I used to be a developer once. How many users have experience in software development?<BR/><BR/>Having said that the question is not if I'm lazy but if I care. I don't want to bother why the darn software doesn't work. That's not my job here. That's developer's part of the job. And they better have some logs, crash dumps or whatever to track the bug down. I don't hack my car when I want to drive to my workplace everyday. It just works or lights user-friendly controls when something is broken. The car doesn't dump technical details when it can't be started. I wouldn't understand it anyway. That's the mechanic's job. <BR/><BR/>I expect the same from the software I use. And most users are too.Pawel Brodzinskihttp://www.blogger.com/profile/04369257211504152485noreply@blogger.comtag:blogger.com,1999:blog-28351195.post-33180235680795764022007-04-14T22:52:00.000+02:002007-04-14T22:52:00.000+02:002007-04-14T22:52:00.000+02:00usually the second one allows you to find out how to try again. If you arenot lazy the second one is better.Anonymousnoreply@blogger.com