Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #11140 > unrolled thread
| Started by | Roedy Green <see_website@mindprod.com.invalid> |
|---|---|
| First post | 2012-01-09 14:02 -0800 |
| Last post | 2012-01-15 12:45 +0100 |
| Articles | 5 on this page of 45 — 18 participants |
Back to article view | Back to comp.lang.java.programmer
please coin a term for a lower order bug Roedy Green <see_website@mindprod.com.invalid> - 2012-01-09 14:02 -0800
Re: please coin a term for a lower order bug Peter Duniho <NpOeStPeAdM@NnOwSlPiAnMk.com> - 2012-01-09 14:18 -0800
Re: please coin a term for a lower order bug bugbear <bugbear@trim_papermule.co.uk_trim> - 2012-01-10 09:18 +0000
Re: please coin a term for a lower order bug George Neuner <gneuner2@comcast.net> - 2012-01-10 11:46 -0500
Re: please coin a term for a lower order bug David Lamb <dalamb@cs.queensu.ca> - 2012-01-10 16:00 -0500
Re: please coin a term for a lower order bug markspace <-@.> - 2012-01-10 13:38 -0800
Re: please coin a term for a lower order bug Gene Wirchenko <genew@ocis.net> - 2012-01-10 15:14 -0800
Re: please coin a term for a lower order bug Peter Duniho <NpOeStPeAdM@NnOwSlPiAnMk.com> - 2012-01-10 18:01 -0800
Re: please coin a term for a lower order bug markspace <-@.> - 2012-01-10 08:52 -0800
Re: please coin a term for a lower order bug Lew <noone@lewscanon.com> - 2012-01-10 17:52 -0800
Re: please coin a term for a lower order bug Peter Duniho <NpOeStPeAdM@NnOwSlPiAnMk.com> - 2012-01-10 19:44 -0800
Re: please coin a term for a lower order bug Gene Wirchenko <genew@ocis.net> - 2012-01-10 20:35 -0800
Re: please coin a term for a lower order bug Roedy Green <see_website@mindprod.com.invalid> - 2012-01-11 10:54 -0800
Re: please coin a term for a lower order bug Ian Pilcher <arequipeno@gmail.com> - 2012-01-09 17:29 -0600
Re: please coin a term for a lower order bug Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-01-09 21:26 -0500
Re: please coin a term for a lower order bug glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2012-01-10 02:43 +0000
Re: please coin a term for a lower order bug Lew <noone@lewscanon.com> - 2012-01-10 07:01 -0800
Re: please coin a term for a lower order bug Leif Roar Moldskred <leifm@dimnakorr.com> - 2012-01-11 03:23 -0600
Re: please coin a term for a lower order bug Wanja Gayk <brixomatic@yahoo.com> - 2012-01-15 13:21 +0100
Re: please coin a term for a lower order bug Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-01-15 08:39 -0500
Re: please coin a term for a lower order bug Patricia Shanahan <pats@acm.org> - 2012-01-15 06:39 -0800
Re: please coin a term for a lower order bug Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2012-01-10 06:45 -0400
Re: please coin a term for a lower order bug Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-01-10 07:54 -0500
Re: please coin a term for a lower order bug Lew <noone@lewscanon.com> - 2012-01-10 07:13 -0800
Re: please coin a term for a lower order bug Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2012-01-10 18:17 -0400
Re: please coin a term for a lower order bug Gene Wirchenko <genew@ocis.net> - 2012-01-10 15:23 -0800
Re: please coin a term for a lower order bug Leif Roar Moldskred <leifm@dimnakorr.com> - 2012-01-11 03:30 -0600
Re: please coin a term for a lower order bug Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-01-11 08:08 -0500
Re: please coin a term for a lower order bug Leif Roar Moldskred <leifm@dimnakorr.com> - 2012-01-11 14:38 -0600
Re: please coin a term for a lower order bug Gene Wirchenko <genew@ocis.net> - 2012-01-11 15:48 -0800
Re: please coin a term for a lower order bug Roedy Green <see_website@mindprod.com.invalid> - 2012-01-11 11:01 -0800
Re: please coin a term for a lower order bug glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2012-01-12 01:45 +0000
Re: please coin a term for a lower order bug Gene Wirchenko <genew@ocis.net> - 2012-01-11 18:05 -0800
Re: please coin a term for a lower order bug Jim Janney <jjanney@shell.xmission.com> - 2012-01-10 09:52 -0700
Re: please coin a term for a lower order bug markspace <-@.> - 2012-01-10 09:51 -0800
Re: please coin a term for a lower order bug Lew <noone@lewscanon.com> - 2012-01-10 18:08 -0800
Re: please coin a term for a lower order bug Gene Wirchenko <genew@ocis.net> - 2012-01-10 19:30 -0800
Re: please coin a term for a lower order bug Lew <noone@lewscanon.com> - 2012-01-10 22:11 -0800
Re: please coin a term for a lower order bug Gene Wirchenko <genew@ocis.net> - 2012-01-11 15:52 -0800
Re: please coin a term for a lower order bug Jim Janney <jjanney@shell.xmission.com> - 2012-01-11 13:38 -0700
Re: please coin a term for a lower order bug Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-01-10 14:05 -0500
Re: please coin a term for a lower order bug v_borchert@despammed.com (Volker Borchert) - 2012-01-11 20:59 +0000
Re: please coin a term for a lower order bug Gene Wirchenko <genew@ocis.net> - 2012-01-11 15:53 -0800
Re: please coin a term for a lower order bug Fredrik Jonson <fredrik@jonson.org> - 2012-01-12 06:59 +0000
Re: please coin a term for a lower order bug Wanja Gayk <brixomatic@yahoo.com> - 2012-01-15 12:45 +0100
Page 3 of 3 — ← Prev page 1 2 [3]
| From | Eric Sosman <esosman@ieee-dot-org.invalid> |
|---|---|
| Date | 2012-01-10 14:05 -0500 |
| Message-ID | <jei26o$vln$1@dont-email.me> |
| In reply to | #11182 |
On 1/10/2012 11:52 AM, Jim Janney wrote:
> Roedy Green<see_website@mindprod.com.invalid> writes:
>
>> What would you call a flaw in a program that had no effect on the
>> results, but needlessly made the program slower or confusing?
>
> What about one that makes it more confusing and needlessly faster?
That, we call "Progress."
--
Eric Sosman
esosman@ieee-dot-org.invalid
[toc] | [prev] | [next] | [standalone]
| From | v_borchert@despammed.com (Volker Borchert) |
|---|---|
| Date | 2012-01-11 20:59 +0000 |
| Message-ID | <jekt6p$qnl$1@Gaia.teknon.de> |
| In reply to | #11140 |
Roedy Green wrote: > What would you call a flaw in a program that had no effect on the > results, but needlessly made the program slower or confusing? As always, that depends. Examples: - If "slower" means that realtime requirements are not met, the bug is a "blocker". - If "slower" means that application sluggishness annoys my boss while he's playing around, the bug will probably become "critical" sooner or later. - If "slower" means that application sluggishness annoys users enough to start them nitpicking on other issues, the bug is at least "major", depending on the importance of the customer. - If "slower" means that an quarterly job takes two hours three seconds instead of two hours, the bug is probably "not-a-bug". -- "I'm a doctor, not a mechanic." Dr Leonard McCoy <mccoy@ncc1701.starfleet.fed> "I'm a mechanic, not a doctor." Volker Borchert <v_borchert@despammed.com>
[toc] | [prev] | [next] | [standalone]
| From | Gene Wirchenko <genew@ocis.net> |
|---|---|
| Date | 2012-01-11 15:53 -0800 |
| Message-ID | <j68sg71ql6lr276m6ogid1kfa9f6gck0s6@4ax.com> |
| In reply to | #11244 |
On 11 Jan 2012 20:59:05 GMT, v_borchert@despammed.com (Volker
Borchert) wrote:
>Roedy Green wrote:
>> What would you call a flaw in a program that had no effect on the
>> results, but needlessly made the program slower or confusing?
>
>As always, that depends. Examples:
>- If "slower" means that realtime requirements are not met,
> the bug is a "blocker".
>- If "slower" means that application sluggishness annoys my
> boss while he's playing around, the bug will probably become
> "critical" sooner or later.
>- If "slower" means that application sluggishness annoys users
> enough to start them nitpicking on other issues, the bug is at
> least "major", depending on the importance of the customer.
>- If "slower" means that an quarterly job takes two hours three
> seconds instead of two hours, the bug is probably "not-a-bug".
No. Each of your examples does affect the results.
Sincerely,
Gene Wirchenko
[toc] | [prev] | [next] | [standalone]
| From | Fredrik Jonson <fredrik@jonson.org> |
|---|---|
| Date | 2012-01-12 06:59 +0000 |
| Message-ID | <slrnjgt16g.iij.fredrik@scout.jonson.org> |
| In reply to | #11140 |
In <fqomg7ltgtddv3one61ei9c33755duu9ec@4ax.com> Roedy Green wrote: > What would you call a flaw in a program that had no effect on the > results, but needlessly made the program slower or confusing? A performance bug or a usability bug. Performance and usability can be as important as correctness. As others have pointed out in this thread it all depends on what quality requirements you have on the system. Now, to answer the question in the subject of your post: A buglet. https://en.wiktionary.org/wiki/buglet It interesting that the word buglet sounds a bit corny - at least to my non-native english. Almost as if it was intended, to point out that buglets really doesn't always need fixing and might almost as well be characterized as a part of the personality of the system. -- Fredrik Jonson
[toc] | [prev] | [next] | [standalone]
| From | Wanja Gayk <brixomatic@yahoo.com> |
|---|---|
| Date | 2012-01-15 12:45 +0100 |
| Message-ID | <MPG.297cdaad30a09fd39896df@202.177.16.121> |
| In reply to | #11140 |
In article <fqomg7ltgtddv3one61ei9c33755duu9ec@4ax.com>, see_website@mindprod.com.invalid says... > > What would you call a flaw in a program that had no effect on the > results, but needlessly made the program slower or confusing? You just named it: A "flaw". If it's supposed to be weaker than that maybe "inconvenience" or "annoyance" would be a better term, where I think the latter is the better one. Kind regards, Wanja -- ..Alesi's problem was that the back of the car was jumping up and down dangerously - and I can assure you from having been teammate to Jean Alesi and knowing what kind of cars that he can pull up with, when Jean Alesi says that a car is dangerous - it is. [Jonathan Palmer] --- Posted via news://freenews.netfront.net/ - Complaints to news@netfront.net ---
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | comp.lang.java.programmer
csiph-web