The handling of errors in go is weird if one only returns or breaks on errors. But it works fine if one does something on error, in almost every error check in

The handling of errors in go is weird if one only returns or breaks on errors. But it works fine if one does something on error, in almost every error check in my go code I have a log.Println with a human readable text like "could not read from the application configuration file." much nicer to get errors like that than a stack dump and a message like could not read from file $filename.