Think this mostly boils down to the opinion that you should handle errors properly or ignore them instead of just logging them. This article might read better i

Think this mostly boils down to the opinion that you should handle errors properly or ignore them instead of just logging them. This article might read better if you defined what "logging" means up front and make sure it's a well scoped definition. I can also think of a bunch of cases where logging is super important that aren't really covered by any of your arguments. For example, if you have a micro services architecture in production in which many services might be accessed (or not) from a request of a particular origin, then you're going to want to "log" a unique identifier for that request and propagate it across all the systems so that you can tie them back to each other if needed. Another example, you sell hardware to consumers. The hardware is composed of modules and components that all talk to each other (yep, it's a car), and how long those components and modules last is effected by environment variables (how you drive). You've got a couple of million of these things on the road. If you want to learn how to improve quality of your hardware, you need to "log" how your hardware performs in the environment that you don't control, so you can correlate failure with environment variables. Can't do that without "logging".