Another voice, from another fellow user and long-time bugfinder: Finding problems is great! It's especially good when it's a low-traffic day to start with (this being Easter Sunday, there are a lot of people doing non-internet things, and while I don't know how DW users stack up against the internet-use-in-general profile, it's got to be somewhat less than typical weekend traffic), during a low-traffic time of the week (all the stats I've heard have said it's lower-traffic on weekends in general), not during the seed account sale, and found by someone friendly rather than someone with any sort of malicious intent.
In the IRC channels where many of the developers hang out (I am not a developer, but I make bad puns with many of them) there is a bot that lets the whole chat know when a new public bug has been filed in the bug-tracker. Occasionally, not as often these days because there aren't as many good ones, but sometimes, there is cheering, actual cheering, when a new bug is filed. This is because the bug getting filed means that there is enough information about a problem to formally enter it in the system, and because filing the bug is the first step to getting it fixed, and having it fixed means that no one else will ever be able to (deliberately or accidentally) do the same thing and cause the same problem ever again.
This is definitely a \o/ YAAAAAY!! \o/ bug.
I don't know if you've ever had the experience when writing fic, where there's something, and you're working on making it the best writing you can possibly manage, and you hand it off to a beta, and the beta points out something that screws everything up, but when you fix it, it is going to make things more awesome than you dreamed was possible? And you're a little sorry that you made a mistake, but you know no writer's perfect so it's not like you're the only one who's done something similar, and it's going to be a lot of work to fix, but once you fix it, it's going to be better than you had thought you could write, and it's exciting and the writing to fix it will be the fun kind of challenge? I would compare some bug report experiences to that. And in this analogy, you would be the beta who pointed it out, not the writer who made the mistake or the writer who's going to have to fix it.
no subject
In the IRC channels where many of the developers hang out (I am not a developer, but I make bad puns with many of them) there is a bot that lets the whole chat know when a new public bug has been filed in the bug-tracker. Occasionally, not as often these days because there aren't as many good ones, but sometimes, there is cheering, actual cheering, when a new bug is filed. This is because the bug getting filed means that there is enough information about a problem to formally enter it in the system, and because filing the bug is the first step to getting it fixed, and having it fixed means that no one else will ever be able to (deliberately or accidentally) do the same thing and cause the same problem ever again.
This is definitely a \o/ YAAAAAY!! \o/ bug.
I don't know if you've ever had the experience when writing fic, where there's something, and you're working on making it the best writing you can possibly manage, and you hand it off to a beta, and the beta points out something that screws everything up, but when you fix it, it is going to make things more awesome than you dreamed was possible? And you're a little sorry that you made a mistake, but you know no writer's perfect so it's not like you're the only one who's done something similar, and it's going to be a lot of work to fix, but once you fix it, it's going to be better than you had thought you could write, and it's exciting and the writing to fix it will be the fun kind of challenge? I would compare some bug report experiences to that. And in this analogy, you would be the beta who pointed it out, not the writer who made the mistake or the writer who's going to have to fix it.