3 ms·
Read the stack trace / error message A lot of the time the answer is there if you read it :)
by chrismatheson 4y ago
Read the stack trace / error message
A lot of the time the answer is there if you read it :)
- ok_dad 4y agoI have no idea the number of times someone has come and told me my code is broken, and when I run it like they did the error message clearly indicates the input was incorrect. Sometimes even when I detect incorrect input and print a message like "input 'manufacturer' must be either 'lexus' or 'toyota'." and they still keep trying to input 'bananna' or '3.14159' or '{'lexus', 'toyota'}' or something that isn't just 'lexus' or 'toyota'!!!
- kelvie 4y agoQuickly parsing / perusing stack traces is sort of a skill that comes from experience (looking at you, large-ass Java stack traces with multiple "caused by:"s). I've noticed this while coaching / working with junior developers, is that this is a still that some haven't quite developed yet, and others clearly have.
- ok_dad 4y agoI’m not even talking stack traces, this case was literally someone not reading a line of text.
- xisukar 4y agoSome stack traces / error messages are less than awesome though
- abdusco 4y ago> Read the stack trace / error message Unless you're using golang. There's no stack trace by default. It's left as an exercise to to programmer to wrap and add context to errors.