tag:blogger.com,1999:blog-8951904624959546499.post1166077458566260402..comments2008-09-07T08:30:21.259-04:00Eric Jacobsonhttp://www.blogger.com/profile/08216361684596485033noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-8951904624959546499.post-51213085557157972252008-09-06T12:49:00.000-04:002008-09-06T12:49:00.000-04:00Yeah, they do say the darn'dest things. In turn, I came to have a set of default replies, one of which is "Excuses!" Of course, this is said in jest.green2noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-85945898371730035582008-08-27T22:26:00.000-04:002008-08-27T22:26:00.000-04:00desertfox,<BR/><BR/>I suppose you're right. I kid this dev. In all seriousness, he's one of the only devs that actually says "sweet!" when I find good bugs.<BR/><BR/><BR/>I Eat Crayons,<BR/><BR/>Yes, I remember that bug. I learned my lesson and have since cleaned up my bug report wording. Now when I log bugs for your code I spell it like this..."breaks".Eric Jacobsonhttp://www.blogger.com/profile/08216361684596485033noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-28628043674692558272008-08-27T21:25:00.000-04:002008-08-27T21:25:00.000-04:00Don't get me started on what testers say. Remember this one that you mentioned in a bug report for I think Formats a while back:<BR/><BR/>"All hell brakes (sic) loose"<BR/><BR/>We still say that from time to time when things don't work.<BR/><BR/>I don't know how that comment was appropriate in a bug report. (I guess I'm not really qualified to say what is appropriate, but that's beside the point)i eat crayonsnoreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-77343226702003354492008-08-27T13:48:00.000-04:002008-08-27T13:48:00.000-04:00Not exactly true, I think what the developer meant was, yes, there is definitely a bug, but that the functionality wasn't totally broken. When working with limited test data, sometimes things can slip through the cracks, it's unfortunate, but it happens. The statement "it isn't totally broken", implies that the feature was indeed developed, but that it doesn't function 100% as expected, hence, it's not "totally" broken. Many shades of gray, as there are also many shades of broken. In my opinion, your developer might need to just man up about it though.desertfoxnoreply@blogger.com