# Errors as Part of Interface

DevFeed: [Errors as Part of Interface](<https://devfeed.tech/articles/errors-as-part-of-interface-40684.md>)

Original publisher: [Read original article](<https://radek.io/posts/errors-as-part-of-interface/>)

Published: 2011-09-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [Radek Pazdera](<https://devfeed.tech/sources/radek-pazdera.md>)

Topics: [Error Handling](<https://devfeed.tech/topics/error-handling.md>), [abstraction](<https://devfeed.tech/topics/abstraction.md>), [Exception](<https://devfeed.tech/topics/exception.md>), [client](<https://devfeed.tech/topics/client.md>), [file](<https://devfeed.tech/topics/file.md>)

Tags: [abstraction](<https://devfeed.tech/tags/abstraction.md>), [client](<https://devfeed.tech/tags/client.md>), [error-handling](<https://devfeed.tech/tags/error-handling.md>), [errors](<https://devfeed.tech/tags/errors.md>), [exception](<https://devfeed.tech/tags/exception.md>), [file](<https://devfeed.tech/tags/file.md>)

## AI overview

The article explains that errors should be reported at the same level of abstraction as the unit, class, or routine where they occur. It argues that error reports should describe the actionable problem for the receiver rather than expose low-level causes such as memory-allocation failures.

## Source excerpt

Steve McConnells idea about proper error handling.