I can think of:

The program works fine but there is one problem.

And that statement is plain wrong because if the program is fine then there shouldn't be a problem. But if there is a problem that means that the program doesn't work fine.

But I want to say that majority of the program works fine and some part doesn't.

How do I say that in a neat way?


1 Answer 1


Others may disagree, but I think "glitch" might fit.

  • "one minor glitch". and if you're sure it's fixable, say "fixable glitch" .

  • If you think the program could be put into use despite the problem, say "it's not a show-stopper".

  • If the problem can be documented around, it's "not a bug, it's a feature" (that's an IT joke; not one you would tell a customer.) But seriously, if users could be trained to work around it, "it's a training issue".

  • If it's a feature that was in the spec, but can't be delivered in this release, say that it "won't be in the initial rollout", but that it (i.e. getting it working) is "on the wish list for Phase Two".

  • "documented around"... interesting turn of phrase.
    – TimR
    May 23, 2015 at 15:30
  • I'm a documenter by trade. And a former programmer. If a program were perfectly reliable as well as intuitive, it would need NO documentation. Therefore, the main point of user documentation is to explain functions that do NOT perform as expected. For example, to warn users NOT to enter certain input (e.g., input that screws something up—maybe not now, but down the pipeline) that the program should trap, but doesn't. May 25, 2015 at 7:16
  • Can I say - "The program works fine except one glitch"? May 25, 2015 at 7:31
  • ". . . except for one glitch." Or . . but there's one glitch." "Otherwise, you are saying the program works but the glitch doesn't. This is a tautology; a glitch couldn't work, because then it wouldn't be a glitch. May 25, 2015 at 9:28

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .