Hacker News Reader

My takeaway from the article is that junior developers are intimidated by stacktraces.

The python example stack trace says explicitly what the problem is and somehow it's a problem?

Don't you get it? You're supposed to manually create the same stack trace by wrapping your errors! Isn't this much more readable?

Error couldn't parse data: couldn't read csv : file not found

Manually appending what you're trying to do at each level that checks for errors seems... Error prone.

I know I'm doing something wrong, but trying to programmatically figure out errors in golang always seems to rely on knowledge of a magic string in the error and I find it frustrating

Reply on news.ycombinator.com