× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I think that the conflict here is the difference between what I call the vendor mindset, and the corporate mindset. The vendor is an entity writing software for someone else, and getting paid for it. That guy is very concerned about what you call a bug, and what you call a feature because while the label you attach to an issue doesn't change the cost associated with resolving said issue, it does indeed affect the revenue stream. And that revenue stream is the raison d'etre for the vendor. In the corporate world, the difference between bug and feature is far different. You see, if the business needs a particular behavior, it doesn't matter if you call it a bug or a feature request. The business needs it, and it will get done. Jeff Atwood is speaking from a corporate mindset. His website has particular needs, and he isn't deriving any revenue from selling the code for it. There is no difference in his mind between bugs and feature requests. The detractors all come from the vendor mindset. The thing to understand is that either could be appropriate depending on your point of view.

Mark Murphy
Atlas Data Systems
mmurphy@xxxxxxxxxxxxxxx


-----John Yeung <gallium.arsenide@xxxxxxxxx> wrote: -----
To: DrFranken <midrange@xxxxxxxxxxxx>
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: 07/12/2017 05:10PM
Cc: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>, midrange <franz9000@xxxxxxxxx>
Subject: Re: SSL Cipher Support and V7R1... and so it begins


On Wed, Jul 12, 2017 at 10:52 AM, DrFranken <midrange@xxxxxxxxxxxx> wrote:
I'm not trying to say that the instant they declare "Fix only" support that
absolutely zero enhancements would ever be added. I am saying that adding
these ciphers DOES constitute an enhancement, not a break-fix. As such IBM
can say No to adding them. Because it potentially affects a large group
though if it was easy I expect they would do it.

Your tone is conciliatory here, and I appreciate that. But the fact
remains that you're not budging on the notion that reasonable people
can differ on what constitutes a "fix".

The fact that you think IBM would do it if it were easy raises the
question: Why then is it so important whether it's called a "fix"?
Doesn't it (and shouldn't it) really come down to a cost-benefit
analysis? If IBM (or anyone else) feels that it's too much effort for
too little gain, why does it matter which bucket it's in? Why do we
need two buckets in the first place?

Jeff Atwood does a decent job articulating what I'm trying to say:

<https://blog.codinghorror.com/thats-not-a-bug-its-a-feature-request/>

Predictably, a lot of the comments are like your responses to me. They
will probably never understand what the hell Atwood is talking about,
just as I am beginning to feel you will never understand what I am
trying to say.

But there are also a lot of comments that agree with Atwood. I guess
I'll just have to take comfort in that.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.