News for hackers. Stuff that matters.
Re:Judge: Citibank isn't entitled to $500M it sent to variou... by hinkley on Thursday February 18, 2021 @04:51PM (#26186171)
I rediscovered this effect myself and it’s why I harp on people for flaky tests. Eventually you discover the build has been broken for hours, everyone assumes they’re just the same old errors, and pushes rebuild without even looking at the error messages.

Everyone does it. I’ve caught myself doing it. So I move to the previous domino and work on that.

Re:Judge: Citibank isn't entitled to $500M it sent to variou... by zimpenfish on Thursday February 18, 2021 @05:13PM (#26186436)
Same goes for log output - if you get thousands of lines every day, no-one ever looks at the logs and things get missed. If you only get log messages when things are really broken, people actually notice.
Re:Judge: Citibank isn't entitled to $500M it sent to variou... by Macha on Thursday February 18, 2021 @05:42PM (#26186828)
I mean, this is what log levels are for. My personal standard is log level error is for things raising an alert over that you need a human to look at, warning is for stuff that can raise an alert if it goes over a threshold, info is only for looking at when a problem has already been identified, so that you can try understand the lead up to the problem, and debug is incredibly spammy stuff only turned on when the above gives insufficient details to recreate the problem locally.
Re:Judge: Citibank isn't entitled to $500M it sent to variou... by hinkley on Thursday February 18, 2021 @06:00PM (#26187041)
Stats are good for things that may be a problem or may not. It’s hard to get a sense of rate with log analysis. You can, but comparing several stats to each other at once is painful.