Re: good grief
That's the approach some developers take because they don't trust the code they write and there is no proper error management in place. It's the classic "printf()" approach, in languages that fear exceptions and their proper management (there's a reason because C and Go are lame languages), and because a proficient user of debuggers and profilers is unknown. So just wait for the application to do something wrong and then peruse the logs. I've seen application spending more time logging what they do instead of doing something useful, actually, with so many logs statement withing the code it was quite difficult to follow the useful code path. Also logging if not done async can slow everything a lot. Writing robust code is far different than logging everything continuosly - especially since logs can also capture sensitive data and store it in unsafe places. Sure, there may be the need to run an app in "debug" or "verbose" mode sometimes, but that should not be the default. When an error occurs, capture the application state and store it.
Moreover, while applications today log and track everything, doesn't really look nor more performant nor more robust.
Biting the hand that feeds IT
