I am writing this as an answer, because otherwise my question would be opinion based.

I think that developers write such error messages because they know that a particular operation can fail in a million ways. Most of the time, the code developer writes has hundreds of conditions that can make the operation fail. It is a moment of success for the developers to finally write that "operation successfully completed" message.

If a user is performing a simple task as saving a post as a draft, he should get the messages:

• If it fails: "Sorry, could not save your draft" (and say why: e.g. network outage, required fields missing)
• If it succeeds: "Your draft was saved"

I am writing this as an answer, because otherwise my question would be opinion based.

I think that developers write such error messages because they know that a particular operation can fail in a million ways. Most of the time, the code developer writes has hundreds of conditions that can make the operation fail. It is a moment of success for the developers to finally write that "operation successfully completed" message.

If a user is performing a simple task as saving a post as a draft, he should get the messages:

• If it fails: "Sorry, could not save your draft" (and say why: e.g. network outage, required fields missing)
• If it succeeds: "Your draft was saved"

I am writing this as an answer, because otherwise my question would be opinion based.

I think that developers write such error messages because they know that a particular operation can fail in a million ways. Most of the time, the code developer writes has hundreds of conditions that can make the operation fail. It is a moment of success for the developers to finally write that "operation successfully completed" message.

If a user is performing a simple task as saving a post as a draft, he should get the messages:

• If it fails: "[Sorry][1], could not save your draft" (and say why: e.g. network outage, required fields missing)
• If it succeeds: "Your draft was saved"

I am writing this as an answer, because otherwise my question would be opinion based.

I think that developers write such error messages because they know that a particular operation can fail in a million ways. Most of the time, the code developer writes has hundreds of conditions that can make the operation fail. It is a moment of success for the developers to finally write that "operation successfully completed" message.

If a user is performing a simple task as saving a post as a draft, he should get the messages:

• If it fails: "Sorry, could not save your draft" (and say why: e.g. network outage, required fields missing)
• If it succeeds: "Your draft was saved"