Software that is taciturn about it’s personal problems does not make excuses about why a technical failure has occured. Instead, it informs that a failure has occured and informs the users of the consequences and the course of action to fix it, as well as what is or will be done to prevent future failures.
Software that is taciturn about it’s personal problems increases the users confidence that corrective action is possible. It also does not confuse the user with irrelevant, often technical, information.
In order to design software that is taciturn about it’s personal problems we must consider how to be as robust as reasonably possible. Since failures are inevitable elegant recovery must also be considered and how impact will be minimized.
Confident software often does not share it’s problems with the user but handles them internally.