But our errors are different in two fundamental ways. The first is that they contain information - as much information as you want. The second is that when they occur, you have a lot of flexibility as to what to do about them. They're like the Marine Corps of code-branching statements; when something unanticipated crops up, just stand back and let the specialists take over. Errors aren't mistakes, they are solutions.
None of which you can say for your math assignments.
But who wants to be delving into error handling when we could be animating the transition of a table view cell into a web-browsing-enabled emoji? Are errors not inherently unattractive? Does error handling mean that we're lousy developers really? Can we just leave this for later and get on with using the Core3DAugmentedSocialVideo framework?
As a result of their understandably less-than-stellar image, errors...
