https://carrion.dev/en/tags/error-handling/Recent content in error-handling on Carrion.devHugo -- gohugo.ioenignacio@carrion.dev (Ignacio Carrión)ignacio@carrion.dev (Ignacio Carrión)©{year}, All Rights ReservedFri, 29 Aug 2025 08:00:00 +0100https://carrion.dev/en/posts/kotlin-24-rich-errors/Fri, 29 Aug 2025 08:00:00 +0100ignacio@carrion.dev (Ignacio Carrión)Fri, 29 Aug 2025 08:00:00 +0100https://carrion.dev/en/posts/kotlin-24-rich-errors/Kotlin 2.4 Rich Errors: What They Are and How to Prepare Kotlin 2.4 introduces “Rich errors” — a more expressive, structured way to represent and propagate failures. The goal is clear: make error flows visible and composable across your codebase and platforms, without losing Kotlin’s ergonomics or its great interop story. This article explains the problems Rich errors solve, how they relate to today’s exceptions and Result, what to expect in terms of mental model and interop, and how to prepare your codebase to adopt it smoothly.Ignacio Carriónfeatured imagekotlinerror-handlingexceptionsresultkotlin-2-4https://carrion.dev/en/posts/runcatching-result-pattern/Fri, 20 Jun 2025 08:00:00 +0100ignacio@carrion.dev (Ignacio Carrión)Fri, 20 Jun 2025 08:00:00 +0100https://carrion.dev/en/posts/runcatching-result-pattern/Elegant Error Handling in Kotlin: Using runCatching and Result Exception handling is a critical aspect of writing robust applications, but traditional try/catch blocks can lead to verbose, nested code that’s difficult to read and maintain. Kotlin offers a more elegant approach with the runCatching function and Result type, which allow you to handle exceptions in a functional way while maintaining code readability and preventing crashes. This blog post explores how to effectively use these features to improve your error handling strategy.Ignacio Carriónfeatured imagekotlinerror-handlingfunctional-programmingresult-patternexception-handling