Question

Error messages should be represented in technical jargon indicating underlying technical problem to the user. true or false

Answer 1

Explanation:

I think it's answer is true

Answer 2

Answer:

This is true that Error messages should be represented in technical jargon indicating the underlying technical problems to the user.

Explanation:

Error messages are very important because they indicate where the problem lies in our production code. They indicate the proper line number as well as the type of the problem in the code.

By reading the error message developer can debug the error by modifying the code.

There are two types of errors that can occur at the time of production:

1. Compile-time Errors: These errors occur when there is some syntax mistake in the code or the developer has violated any law of programming language. They are detectable by the underlying compiler.
2. Run-time Errors: They occur when the code starts executing since they are not detectable by the compiler itself.

For example, The developer applied the wrong logic for solving the problem, or the array is indexed out of the bound. They all are run-time errors. They don't stop the execution of the program but they cause a wrong output.

#SPJ2