# Random Scala Tip #534: Adopt an Error Handling Convention for `Future`
7 min read
When working with `Future` be explicit about your error handling convention, and make sure your whole team and codebase are aligned to it.
When working with `Future` be explicit about your error handling convention, and make sure your whole team and codebase are aligned to it.
Before wrapping anything in `Option`, consider whether you should use a more meaningful domain-specific data type instead.
Beware of leaking `Iterator` instances outside the scope you initialized it in.
Avoid using anonymous functions as class dependencies.