Think about this...

[Snooze]

I found this on another forum and couldnt help think about some of the people in here ..

Don't claim that you have found a bug

When you are having problems with a piece of software, don't claim you have found a bug unless you are very, very sure of your ground. Hint: unless you can provide a source-code patch that fixes the problem, or a regression test against a previous version that demonstrates incorrect behavior, you are probably not sure enough.

Remember, there are a lot of other users that are not experiencing your problem. Otherwise you would have learned about it while reading the documentation and searching the Web (you did do that before complaining, didn't you?). This means that very probably it is you who are doing something wrong, not the software.

The people who wrote the software work very hard to make it work as well as possible. If you claim you have found a bug, you'll be implying that they did something wrong, and you will almost always offend them ? even when you are correct. It's especially undiplomatic to yell ?bug? in the Subject line.

When asking your question, it is best to write as though you assume you are doing something wrong, even if you are privately pretty sure you have found an actual bug. If there really is a bug, you will hear about it in the answer. Play it so the maintainers will want to apologize to you if the bug is real, rather than so that you will owe them an apology if you have messed up.

[Troubadour]

Awesome speech with very nice thoughts!

Regards,
Troubadour

[Snooze]

I thought so too :)

[[NL]Pur]

i can't agree here,

not every script is opensource, so you can't patch,

I think the point about, because other ppl don't have the problem it isn't a bug, is a bit weird to think.

Must i assume now that if only 1 person is having the problem it isn't a bug, and if 50 ppl have it is a bug.
Maybe the 50 ppl do all the same thing wrong. I'm just saying howmany ppl having a problem doesn't have anything todo with the definition of a bug.

About scripters on this forum, i think all of them script with the ''technique'' , trial on error. None (maybe 1) of them are making first Uml models, state diagrams, use cases etc before actually coding.

And think i'm a developer, and i'm not offended when someone says finding a bug and it isn't a bug.

I think it only shows that someone wants to make your program work for them. And there's nothing better then developing a program that is be used widely.

[Snooze]

I agree with your statement, [NL]Pur.

This isn't ment as a guideline .. just something to think about.

Bug reports are important for developers, though I do think that one should think about how the bug is reported.

[Corayzon]

very interesting snooze,

i think it depends on the type of development and the type of program being writin, and sometimes it may also depend if its open source aswell as the developers personalities and integrity.

hmm...i could write so much but i have no time...eheh

ppl can proove me wrong if they wish, and if so, they can have thier name somewhere in the script that they prooved me wrong with if they are correct.

ohh, i will say.

what is a bug?
how can bugs happen?
and what can bugs do?

noza

[NightLitch]

Don't know if this got something to this for writing lua but:

function NewUserConnected(NLitch)
  NLitch:SendData(BotName, "Welcome.....")
end

function DataArrival(uLitch,dLitch)
  local s,e,datastream = strfind(dLitch, "(.*)%|")
end

but of course my point here is not hard changing of course.

This maybe totally out of what you all discussion.

/NL

[Snooze]

Just to add something to this thread..

This IS usefull reading ..

http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

One more..

http://www.catb.org/~esr/faqs/smart-questions.html