Re:Ask HN: What is your best advice for a junior software de...
by Agathos on Wednesday October 03, 2018 @12:34PM
(#18131947)
Raise your hand if you've ever created an insert/update database trigger that explodes when that it sees that one bad value you've been investigating, just so you'll have a traceback that points to the offending code.
(Hopefully only in your development environment.)
Likewise, I think adopting a "how can I create a stack trace/error message" mindset is incredibly important.
Can you add a breakpoint to a certain piece of code? Could you add a try/catch statement somewhere to catch the error?
Far too often good engineers do not have an "active" mindset in hunting for stack traces/error messages, instead, they wait for them to fall like manna from heaven.