> Go's error handling is boring in a bad way. Manually clicking through screens again and again because you failed to write UI tests is boring in a bad way.

Go's error handling is useful if your system needs to be correct more than it needs to be available, and you should be manually clicking through screens even if you wrote UI tests.

Looking at why something is boring and who it's boring for can be helpful, especially in a team setting. It's entirely possible to automate away a bottleneck that exists for a good reason while sitting across from someone who'd love to handle the issue correctly.