def programming

#bugs

Not all eyes that notice bugs in Open Source code belong to saints who will report or repair them in the interest of the public good.

If McDonald's were run like a software company, one out of every hundred Big Macs would give you food poisoning, and the response would be, "We're sorry, here is a coupon for two more."

No matter how slick the demo is in rehearsal, when you do it in front of a live audience the probability of a flawless presentation is inversely proportional to the number of people watching, raised to the power of the amount of money involved.

on beta, bugs

"That hardly ever happens" is another way of saying "it happens".

on bugs

The longer it takes for a bug to surface, the harder it is to find.

on bugs

Law 1: Every program can be optimised to be smaller. Law 2: There's always one more bug. Corollary: Every program can be reduced to a one-line bug.

Without requirements or design, programming is the art of adding bugs to an empty text file.

The standard rule is, when you're in a hole, stop digging; that seems not to apply [to] software nowadays.

The trick is to fix the problem you have, rather than the problem you want.

At the source of every error which is blamed on the computer you will find at least two human errors, including the error of blaming it on the computer.

Any non-trivial program contains at least one bug.

on bugs

There are two ways to write error-free programs; only the third works.

on bugs

It's not a bug - it's an undocumented feature.

on bugs

Each new user of a new system uncovers a new class of bugs.

Built with using

Source code available @ githubpull requests are more than welcome ;-)