top | item 39943645 (no title) peppermint_gum | 1 year ago My takeaway from the article is that junior developers are intimidated by stacktraces. discuss order hn newest monknomo|1 year ago The python example stack trace says explicitly what the problem is and somehow it's a problem? fireflash38|1 year ago 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 foundManually appending what you're trying to do at each level that checks for errors seems... Error prone. load replies (1)
monknomo|1 year ago The python example stack trace says explicitly what the problem is and somehow it's a problem? fireflash38|1 year ago 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 foundManually appending what you're trying to do at each level that checks for errors seems... Error prone. load replies (1)
fireflash38|1 year ago 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 foundManually appending what you're trying to do at each level that checks for errors seems... Error prone. load replies (1)
monknomo|1 year ago
fireflash38|1 year ago
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.