Hacker News Reader

I 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'!!!

Quickly 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.

I’m not even talking stack traces, this case was literally someone not reading a line of text.

> 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.

Some stack traces / error messages are less than awesome though