|
|
|
|
|
by jeffreygoesto
24 days ago
|
|
So much this. I tell my juniors: To a beginner programmer, errors are 'the end'. They feel they did their best, it is not their fault and that is the error message they print. Experienced programmers know the user struggle, for them an error message is 'a beginning'. The first step of the user striving to solve the problem. They gave that command and they did not give it to fail. They (the users) still want to teach their goal. Pro tip: Don't just print the return code, also print the call and it's arguments that failed, even without a stack trace. |
|