Re: Wolfram Alpha claims to be a primary source.

Peter wrote:
VB> ... how many defects are still alive from the chapter
VB> 1 of my draft I reported to Wolfram Research in 2001?
VB> http://maple.bug-list.org/chapter1.txt

D> But your manner of reporting bugs, copying them to endless
irrelevant
D> newsgroups in a dramatic way is not the best approach.

Newsgroups are an important source of feedback for any vendor
and bugs reported there should be taken seriously by the
respective QA-departments. You disagree?


Newsgroups are I'm sure very useful to companies QA departments.

I've reported a few on newsgroups (especially Sun-related newsgroups) and Sun have fixed them.

On occasions where I've found fixes to bugs, I've posted them here, since everyone can benefit immediately.

It's probably not an unreasonable assumption that had Vladimir been professional about the way he reported bugs, he may well have been considered for employment by Maplesoft, Wolfram Research, perhaps Mathworks too. Then, given access to source code for the products, his testing could have been targeted to exercise each piece of the code and probably detect even more bugs. I suspect those companies have faster machines than his too.

I somewhat doubt any of those companies would want to employee him now.

Also, Wolfram Research employees are more likely to look at the posts from people who post sensible comments, than they would from someone who posts numerous stupid statements.

Of course, I'm guilty of a bit of fun some times, with things like the challenge to find the most ridiculous Wolfram Research claim. But I don't do this ever day, and did not copy it to endless newsgroups.

PS
I just noticed sci.math got added to the list of newsgroups this was sent to. I don't know who done it, but it was not me when I first created the thread.


--
I respectfully request that this message is not archived by companies as
unscrupulous as 'Experts Exchange' . In case you are unaware,
'Experts Exchange' take questions posted on the web and try to find
idiots stupid enough to pay for the answers, which were posted freely
by others. They are leeches.
.

Relevant Pages

  • Re: TeamB, bugs and waste of time...
    ... > There is nothing wrong with this idea - of course bugs can be discussed ... But these newsgroups are not just for reporting bugs, ... in this newsgroups are minimal so let's not exxagerate talking about family ... There are tens and tens of TeamB posts in that creepy thread. ...
    (borland.public.delphi.non-technical)
  • Re: 2.6.19 -mm merge plans
    ... I actually expected people to dislike arbitrary rules more than they do, but I've come to believe that people _like_ having rules that they have to obey, as long as it's not a big pain for them. ... So I think that a "odd release"/"even release" rule that clarifies what a certain mid-point in the release cycle actually _means_, even if it doesn't necessarily add anything else, might be a good thing. ... Then after people stop reporting show stoppers, change to rc numbers, where rc versions are actually candidates for release without known major bugs. ...
    (Linux-Kernel)
  • Re: Inheritance
    ... Go hooking to fix bugs in MS code? ... There's no site for reporting bugs in VS ... >> always be using the latest DDK. ... Maxim Shatskih, Windows DDK MVP ...
    (microsoft.public.development.device.drivers)
  • Re: First day with production development on D2005
    ... >> involved in reporting them vs. the benefit of reporting them. ... > The cost is taking some time to write the report. ... bugs are unlikely to get fixed and that show-stopper, ... not bother reporting bugs and if the development environment has too many ...
    (borland.public.delphi.non-technical)
  • Re: Delphi 2007 more Flakey than 2006?
    ... I don't know how difficult this would be - as my bugs are all my own ... Windows has such a reporting system on board - called WER (Windows ... which attaches the stack trace similar to what Windows error ...
    (borland.public.delphi.non-technical)