Wow, great topic, John. One could write (and some have written) entire books on this.

Bugs, or flaws, should always be revealed. Hiding a bug or hoping it'll never be spotted is inviting future problems or loss of business.

IMHO, remedies depend on the nature of the flaw. If it's a syntax or coding error, I think you own up to it and fix it. Immediately. The clients should have some reasonable expectation of workmanship.

OTOH, if the flaw is traced to an invalid understanding of the underlying business logic, it's important first to figure out how the misunderstanding was introduced. A good developer is like a good private detective and can usually smell flaws in business logic before the code has been written. But, sometimes, you're just not on the same page as your client and a misunderstanding makes it's way into the application. The burden in those cases is still on the developer because your job is to translate their business into our processes and not the reverse.


>Hi,
>Should we tell the truth of our program bugs to our client? Or, we make a story/other excuses ?