Skip to main content
added 13 characters in body
Source Link
CowBoy
  • 153
  • 5

Assuming you have a software which you gave to clients.

Now we all know that exceptions can be saved to files, databases, and so on for tracing errors by technicians. As all engineers know, no Apps in first releases will be bug-less, but it must have bugs for either logical or randomly unknown reasons, such as [Hard disk is full] and client try to Export PDF file, or save things to DB.

There's points, which i need to know from seniors :

  1. what really should we do to catch all kind of exceptions without showing any error messages to clients? Is There any OpenAPI or Exception Email-Friendly API for that?

  2. Is it good to show exception messages, or just Red Flag, or some Color that when the client sees, they would contact technicians?

Thats All !

Assuming you have a software which you gave to clients.

Now we all know that exceptions can be saved to files, databases, and so on for tracing errors by technicians. As all engineers know, no Apps in first releases will be bug-less, but it must have bugs for either logical or randomly unknown reasons, such as [Hard disk is full] and client try to Export PDF file, or save things to DB.

There's points, which i need to know from seniors :

  1. what really should we do to catch all kind of exceptions without showing any error messages to clients? Is There any OpenAPI or Exception Email-Friendly API for that?

  2. Is it good to show exception messages, or just Red Flag, or some Color that when the client sees, they would contact technicians?

Assuming you have a software which you gave to clients.

Now we all know that exceptions can be saved to files, databases, and so on for tracing errors by technicians. As all engineers know, no Apps in first releases will be bug-less, but it must have bugs for either logical or randomly unknown reasons, such as [Hard disk is full] and client try to Export PDF file, or save things to DB.

There's points, which i need to know from seniors :

  1. what really should we do to catch all kind of exceptions without showing any error messages to clients? Is There any OpenAPI or Exception Email-Friendly API for that?

  2. Is it good to show exception messages, or just Red Flag, or some Color that when the client sees, they would contact technicians?

Thats All !

Assuming you have a software which you gave to clients.

Now we all know that exceptions can be saved to files, databases, and so on for tracing errors by technicians. As all engineers know, no Apps in first releases will be bug-less., but it must have bugs for either logical or randomly unknown reasons., such as [Hardisk[Hard disk is full] and client try to Export PDF file, or save things to DB.

There's points, which i need to know from seniors :

  1. what really should we do to catch all kind of exceptions without showing any error messages to clients. ? Is There any OpenAPI or Exception Email-Friendly API for that ?

    what really should we do to catch all kind of exceptions without showing any error messages to clients? Is There any OpenAPI or Exception Email-Friendly API for that?

  2. Is it good to show exception messages ? or just Red Flag, or any Color that client when see he contact technicians.

    Is it good to show exception messages, or just Red Flag, or some Color that when the client sees, they would contact technicians?

Assuming you have a software which you gave to clients.

Now we all know that exceptions can saved to files, databases, and so on for tracing errors by technicians. As all engineers know no Apps in first releases will be bug-less. but it must have bugs either logical or randomly unknown reasons. such as [Hardisk is full] and client try to Export PDF file, or save things to DB.

There's points which i need to know from seniors :

  1. what really should we do to catch all kind of exceptions without showing any error messages to clients. ? Is There any OpenAPI or Exception Email-Friendly API for that ?
  2. Is it good to show exception messages ? or just Red Flag, or any Color that client when see he contact technicians.

Assuming you have a software which you gave to clients.

Now we all know that exceptions can be saved to files, databases, and so on for tracing errors by technicians. As all engineers know, no Apps in first releases will be bug-less, but it must have bugs for either logical or randomly unknown reasons, such as [Hard disk is full] and client try to Export PDF file, or save things to DB.

There's points, which i need to know from seniors :

  1. what really should we do to catch all kind of exceptions without showing any error messages to clients? Is There any OpenAPI or Exception Email-Friendly API for that?

  2. Is it good to show exception messages, or just Red Flag, or some Color that when the client sees, they would contact technicians?

distracting noise removed from the question
Source Link
Doc Brown
  • 214k
  • 34
  • 394
  • 603

Assuming you have a software which you gave to clients.

Now we all know that exceptions can saved to files, databases, and so on for tracing errors by technicians. As all engineers know no Apps in first releases will be bug-less. but it must have bugs either logical or randomly unknown reasons. such as [Hardisk is full] and client try to Export PDF file, or save things to DB.

There's points which i need to know from seniors :

  1. what really should we do to catch all kind of exceptions without showing any error messages to clients. ? Is There any OpenAPI or Exception Email-Friendly API for that ?
  2. Is it good to show exception messages ? or just Red Flag, or any Color that client when see he contact technicians.

Thats All !

Assuming you have a software which you gave to clients.

Now we all know that exceptions can saved to files, databases, and so on for tracing errors by technicians. As all engineers know no Apps in first releases will be bug-less. but it must have bugs either logical or randomly unknown reasons. such as [Hardisk is full] and client try to Export PDF file, or save things to DB.

There's points which i need to know from seniors :

  1. what really should we do to catch all kind of exceptions without showing any error messages to clients. ? Is There any OpenAPI or Exception Email-Friendly API for that ?
  2. Is it good to show exception messages ? or just Red Flag, or any Color that client when see he contact technicians.

Thats All !

Assuming you have a software which you gave to clients.

Now we all know that exceptions can saved to files, databases, and so on for tracing errors by technicians. As all engineers know no Apps in first releases will be bug-less. but it must have bugs either logical or randomly unknown reasons. such as [Hardisk is full] and client try to Export PDF file, or save things to DB.

There's points which i need to know from seniors :

  1. what really should we do to catch all kind of exceptions without showing any error messages to clients. ? Is There any OpenAPI or Exception Email-Friendly API for that ?
  2. Is it good to show exception messages ? or just Red Flag, or any Color that client when see he contact technicians.
Source Link
CowBoy
  • 153
  • 5
Loading