https://prateeksharma.me/tags/error-handling/ Recent content in Error Handling on Prateek Sharma Hugo en-us Fri, 28 Aug 2026 00:00:00 +0000 https://prateeksharma.me/opinions/two-exceptions-not-one/ Fri, 28 Aug 2026 00:00:00 +0000 https://prateeksharma.me/opinions/two-exceptions-not-one/ <p>In the <a href="https://prateeksharma.me/projects/wazirx-connector-java/">WazirX Java connector</a> I split errors into two:</p> <ul> <li><code>WazirxClientException</code> — the caller made a mistake the caller can fix: a bad <code>side</code> value, a missing required field. Thrown before a request is even sent.</li> <li><code>WazirxApiException</code> — something went wrong once the request left the process: a network failure, a non-2xx response.</li> </ul> <p><code>WazirxClientException extends WazirxApiException</code>. That one line is the whole design. A caller who only cares &ldquo;did this work?&rdquo; catches the parent. A caller who wants to retry network failures but fail fast on their own bad input catches both separately. Nobody is forced into a giant <code>catch (Exception e)</code> that swallows bugs, and nobody has to <code>try/catch</code> five specific types at every call site.</p>