I am quite unsure about when it is appropriate to use exceptions or not. Recently, I read an article mentioning that not everything should be handled with exceptions; they should only be used in cases where the system really needs to stop and report the issue. On the other hand, in scenarios such as consuming an API, this might not be the best approach. The code below is an integration with a ZIP code lookup API, allowing the user to enter a value and return the corresponding address. If the `error` property is equal to `true`, this indicates that the ZIP code may be incorrect or that the address does not exist: AddressResponse? address = await response.Content .ReadFromJsonAsync<AddressResponse>(token) .ConfigureAwait(false); return !response.IsSuccessStatusCode || address?.Error == "true" ? throw new HttpRequestException("Address not found.") : address; Next, the code that calls the method above iterates over a list using `Task.WhenAll`. In this case, the question arises: is it wrong to use `try/catch` and add errors into a `ConcurrentBag` (in this example, `errors.Add`), or would it be better to return a result object that indicates success or failure? AddressResponse?[] responses = await Task .WhenAll(zipCodes .Select(async zipCode => { try { return await service.GetAddressAsync(zipCode, token); } catch (Exception ex) { errors.Add($"Error: {ex.Message}"); return null; } })); This is a simple program for integrating with an API, but it serves as an example of how to improve a real-world application. *Note: the C# syntax is really beautiful.*

I’ve been testing the new \*\*ProblemDetails support in .NET 9\*\*, and I think it’s a great way to standardize error responses. Before, each API returned errors in a different format (plain text, HTML, custom JSON). With ProblemDetails, you always get a consistent JSON structure following \*\*RFC 7807\*\*: \`\`\`json { "type": "...", "title": "...", "status": 400, "detail": "...", "instance": "..." } I really like how easy it is to enable in .NET 9: builder.Services.AddProblemDetails(); app.UseExceptionHandler(); More info: [youtube.com/.../watch](youtube.com/.../watch)