2 ms·
IMO this is a worthy language agnostic topic, modeling and managing execution tree error cases has ever been an issue for my brain.
by agumonkey 6y ago
IMO this is a worthy language agnostic topic, modeling and managing execution tree error cases has ever been an issue for my brain.
- _ix 6y agoI’m a bit of a pythonista, but I haven’t worked on anything very complex for a couple of years. Maybe my experience is still a little shallow in SWE topics, but can you reify this a bit? What kind of situations have you run into where handling multiple exceptions would have been handy? Maybe it’s telling that I’d have to admit that I’m not sure how big a difference there is between error code returns and exception handling.
- agumonkey 6y agoIt's just that the diagram shown in the article/blog were more inspiring than 99% what I heard about error abstractions on any language (and yeah it's not about python only). I just wished to read more about very general solutions on nested/stacked calls with exceptions and how to reduce the perimeter and make things more readable (honestly most of the time exception handling for me was logger.error or wrap/rethrow.. nothing exciting)