top | item 39282328

(no title)

wmidwestranger | 2 years ago

Almost every software engineering book:

Halting on an error is often best, as is raising the error after catching it, unless you're certain it should be subdued or aware, expect the issue, and have limited risk.

Every dev project:

Hold up, couldn't this raise an exception? That's bad!

discuss

order

No comments yet.