Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Fredrik Jonson Newsgroups: comp.lang.java.programmer Subject: Re: please coin a term for a lower order bug Date: 12 Jan 2012 06:59:22 GMT Lines: 20 Message-ID: References: X-Trace: individual.net bgkzwAr+ocatPcboIqdfwg7CCdh79F7FO7D03M1LIvM4LIDO0= Cancel-Lock: sha1:Kn2AEkSijYC5wIUqSHVxRtdi93w= User-Agent: slrn/pre1.0.0-18 (Linux) Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:11259 In 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