News for hackers. Stuff that matters.
Re:Ask HN: What is your best advice for a junior software de... by fhood on Wednesday October 03, 2018 @11:52AM (#18131459)
What about, log_panic("If we have somehow managed to hit this code path, this project if FUBAR. I would recommend giving up and starting over.")
Re:Ask HN: What is your best advice for a junior software de... by btschaegg on Thursday October 04, 2018 @02:02AM (#18137539)
Somehow reminds me of Aliens:

  I say we take off and nuke the entire site from orbit. It's the only way to be sure.
:-)
Re:Ask HN: What is your best advice for a junior software de... by m_samuel_l on Wednesday October 03, 2018 @06:05PM (#18135231)
That's annoying but fine as long as it's unique and you can grep it in the codebase.
Re:Ask HN: What is your best advice for a junior software de... by fao_ on Wednesday October 03, 2018 @07:18PM (#18135615)
You can forgo something being unique if you just append line and file information to the log. Literally any logging framework (even homerolled ones) should give you this by default.
Re:Ask HN: What is your best advice for a junior software de... by fhood on Thursday October 04, 2018 @11:00AM (#18140486)
yup