Increasingly so, the more experienced I get…
You must log in or # to comment.
Proprietary software be like:
try: whatever() except Exception: print("oops something went wrong uwu") print("also this is purely to get rid of the stack trace because apparently the only thing worse than not handling an exception is scaring the user with anything technical and/or exposing our trade secret architecture")Increasingly so, the more experienced I get…
Knowledge is a curse!
The more you know, the more you realise you don’t know.
Currently implementing error handling for a library I’m building and the process is basically to just throw all of the information I can find into there. It makes the error handling code quite verbose, but there’s no easy way for me to know whether the underlying errors expose that information already, so this is actually easier to deal with. 🫠
I appreciate verbosity. It’s much nicer than the opposite.
Thank you, I hate it when libraries fail and don’t give me good info, like failed to load doesn’t help, failed to load because of syntax error on line 45 of input is soooo nice when that happens.
Maybe one more log output would fix it…
print “error \n”
There, handled.
Welcome to the second part of the Dunning Kruger wild ride of software.
