Exceptions are like landmines in your codebase. Consumers/callers have no idea what you might throw. Top level try/catch aren’t the answer. Start being explicit about the return type of your methods.

πŸ”” Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1

πŸ’₯ Join this channel to get access to source code, demos, and slides!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join

πŸ“ Blog: https://codeopinion.com/stop-throwing-exceptions-start-being-explicit/

πŸ“š Book Recommendations

Domain-Driven Design
https://amzn.to/2QwG8sb

Patterns of Enterprise Application Architecture
https://amzn.to/3d8kMJj

Refactoring: Improving the Design of Existing Code
https://amzn.to/2NVdP5Q

Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
https://amzn.to/3srUuZ6

RESTful Web Clients: Enabling Reuse Through Hypermedia
https://amzn.to/3d8Q96B

CodeOpinon: https://codeopinion.com
Twitter: https://twitter.com/codeopinion

#exceptions #throwing exceptions

STOP throwing Exceptions! Start being Explicit
1.15 GEEK