Strongly agree with your second point, too many times I had to figure out issues caused by code trying to handle errors but actually hiding them and making it so much harder to debug. The typical antipattern: catching SomeErrorType just to log "error of that type occurred", thus hiding the associated error message and the stacktrace. Even worse: trying to catch every error types.
Don't catch errors unless doing something actually useful with them. Even then, it's often a good idea to re-raise.
Don't catch errors unless doing something actually useful with them. Even then, it's often a good idea to re-raise.