Older blog entries for robocoder (starting at number 0)

30 Nov 2002 (updated 27 Dec 2002 at 21:21 UTC) »

We, humans, are notoriously imprecise. Do you always agree with what someone else calls an anomaly, a bug, a defect, a deficiency, an error, an exception, a fault, a problem, or an issue? When was the last time you matter-of-factly said:

  • That's not a bug.
  • That's a "feature".
  • That'll be an enhancement (or change request).
  • We need to reset the customer's expectations.

That a reported problem may meet with any (or all) of these responses, leads us to consider the need for more concise operational definitions. I originally explored that here, and formalized into into an e-paper, "What is a bug?"

And after considerable literature review, analysis, and refinement of my thoughts, I arrived at the following definitions:

any deviation between the customer's expectation, the specification, and/or implementation.
any observed event or detected deviation between the specification and the implementation.
a deviation between the specification and the implementation, detected after release to the customer.
Maybe now I can get a normal night's sleep.

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!