Comments on: Wherein QA Fixes Its Own Issues

By: Director

Director — Sun, 22 Jul 2007 01:33:31 +0000

Sadly, DarkStar’s comment made me want to justify, to a larger extent, how I fixed the issue. So there’s a little developer in each of us.

Now I am going to resort to the discipline to try to drive mine out.

By: gimlet

gimlet — Sat, 21 Jul 2007 18:28:32 +0000

If you were truly a developer, you would have blamed the issue on the server OS, hardware, and/or webserver. You then would have insisted (in a geekier-than-thou tone) that the sysadmin(s) deploy a trendy, poorly-documented, and/or untested solution that is “better,” at least according to what you’ve read on Slashdot.

By: angelweave

angelweave — Thu, 19 Jul 2007 18:36:32 +0000

That developer that led you down the “wrong” path was your WIFE. And had she been the coder, doubtless it would not have taken two hours.

That developer also cooks your meals. No defects there.

hln

By: Director

Director — Thu, 19 Jul 2007 16:26:01 +0000

Very true. However, I found the solution for the immediate issue adequate, and I was able to fix it quickly and I’m not even one of you highly-paid development professionals.

By: DarkStar

DarkStar — Thu, 19 Jul 2007 16:18:21 +0000

Not to be a stickler… that is your job after all. But as an occasional UI designer who also dabbles in sales, I feel confident in rejecting your solution. Not that you are out of line highlighting the problem, but there is a reason QA doesn’t develop, and developers don’t QA.

How about… breaking apart the string, so that the text ends up wrapping properly? Perhaps with a hyphen? If I’m typing text into your comment box, and the text is very long and ends up getting rejected… I probably won’t stick around to retype or reformat and thus you’ve lost a sale… or comment… or complaint… If its a URL, then you will probably need some code to reassemble the URL in case it is clicked on… Yes, an annoying tidbit of coding work – but beneficial none the less.

And while we are on the topic of QA… which we always are at this site… when a user registers, the confirmation message suggests that an email has already been sent containing the new password and is waiting for the user to simply go read it. Not so. It took more than 5 minutes for my password to show up in my Inbox. The message should probably say… “An email will be sent…” Rather than, “An email has been sent.” While the message may be technically correct, user experience will dominate.