Re: Delphi 2005 upgrade 2... not recommended

From: Brian Moelk (bmoelk_at_NObrainendeavorSPAM.FORcomME)
Date: 03/29/05 

Date: Tue, 29 Mar 2005 14:10:33 -0500

> I see my comment on it really got your riled up :-) I did not "pounce"
> on your posting, however when I offered my opinion on the quote itself,
> you did rather "pounce" on me, making it sound as if I was doing a
> disservice to my customers, without even considering what I was
> actually saying.

Indeed, poor customer service and software that sucks do get me riled up.
Excuses and justifications make it worse.

> All I was trying to do was provide another
> perspective to that particular well-worn quote, which might have
> sounded sarcastic, but was not intended to be so.

David, you sound like you have a decent command of the English language, so
I don't understand how your intention was not conveyed exactly how you wrote
it. I would have been more happy to hear that you were being sarcastic
rather than seriously embracing such nonsense.

> I was mererly
> pointing out that, in the real world, one can be overwhelmed with bug
> reports that are not actually bugs and all reported bugs have a process
> to go through that may not always be what a consumer would want to hear.

Then why didn't you just "merely point that out"? Instead, you said
something dumb (IMO). This "merely pointing that out" stuff smells to me
like backpeddling...but whatever.

> If you had the resouces to immediatety open and assign an issue on
> every single report, that would be fantastic, but in the real world one
> could be out of business very quickly. As an example, many of my
> customers are not very computer literate. I have had new users
> complain that my program caused their hard drive to crash, the colors
> to change on their monitor and they email to stop working, none of
> which are remotely related to our software. Unless I get enough
> reports on a single issue I simply cannot spend the time to trace each
> report. So, when one of our cusotmers makes a bug report we prioritize
> it (doesn't everyone?), if it sounds as if can even be remotely related
> to our product. When it is tested it is tested on a clean test
> machine/network, not on our development machines. If we can not
> duplicate it then we do indeed tell the customer that "it is working
> on our test machines". If we get additional reports about the same
> issue it then bubbles up in the priority level. I don't think this is
> much different then most development houses handle reported bugs.

Of course and if you simply said that, I would agree. But even after
agreeing, it still doesn't change the fact that many D2005 customers are not
happy with the product, and in particular, that I am not happy having a
bloated, slow and unstable IDE.

But go back to the original context and exactly what you said. It is clear
to me that you were being a smart ass or provoking intentionally or
defending excuses("works on my machine"). All of which I don't appreciate.

> Somehow this got turned around into a D2005 conversation, but was
> actually more abstract then that, and my comments were concerning the
> quote itself, not anything to do with D2005.

Well, the thread is about recommending D2005 and the context of the quote
was about D2005....but regardless I still think your comments were stupid.

> I stated specifically
> that as of now,, I have no opinion regarding Borland's chosen timeframe
> to release D2005. I just don't have enough information to make a
> credible statement on that.

That's great, but I do have an opinion and all the information I need to
make a credible statement, IMO, is my experience with the product.

> I do believe we have beat this issue to
> death. :-)

Indeed. 

--
Brian Moelk
bmoelk@NObrainendeavorSPAM.FORcomME
http://www.brainendeavor.com

Relevant Pages

  • Re: Decompiler.NET reverse engineers your CLS compliant code
    ... Please identify them again for me since I don't know what you are referring ... The 2 bug reports being left are minor sure but they have only been ... >reported to show that your tool has bugs because you claimed it doesn't. ... customers reported them to us. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Decompiler.NET reverse engineers your CLS compliant code
    ... There are 2 fundamental issues reported for your tool and 3 bug reports. ... > identified two tiny bugs which we have already fixed. ... > We do not actively search our competitors web sites looking for their test ... Our customers agree that our product is the only one ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Delphi 8 common quality
    ... I do not find that forcing your customers to have to do things ... What about poor email reports? ... > from customers by any means when they are reporting bugs or issues. ...
    (borland.public.delphi.non-technical)
  • Re: Overview of Paradox database structure and architecture
    ... multiplicity of customers and reports and libraries? ... Special customer reports are all stored in a folder with customers name, ... method CutToSize(s string, len smallint) string ... method CutToSizeAndAllign(s string, len smallint, right true) string ...
    (comp.databases.paradox)
  • Re: Pentagon reports no longer quote Bible
    ... Pentagon reports no longer quote Bible ... the Bush administration seemed oblivious to the damage that this would cause. ...
    (soc.retirement)