verbosemode

verbosemode

Home
Notes
Archive
About

Why Kotlin’s Result Type Falls Short for Handling Failures

The Kotlin standard library warns against using Result for domain logic—here’s why you should listen.
READ THE LATEST

Recent posts

View all
I’m Changing My Writing Schedule for 2025 🖊️
Reflecting on 2024: Lessons Learned About Writing and Sustainability
If You’re Not Refactoring Every Day, You’re Making a Mistake
Small Daily Refactors Prevent Big Headaches: How Regular Cleanups Save Your Team from Code Spaghetti, Tech Debt, and Customer Frustration
1
Debugging 🔍 - Reduce ✂️ or Rebuild 🔨?
Choosing Between Removing Dependencies or Incrementally Adding Parts to Solve Issues
Scalability Cheat Sheet #2 - When Things go Wrong and Partitioning
Tackling Replication Lag ⏳, Write Conflicts ⚔️, and Partitioning 🧩
2
Scalability Cheat Sheet #1 - From Basics to Replication
Scalability Basics, Vertical vs. Horizontal Scaling, and Introduction to Replication 👥
verbosemode
verbosemode
Kotlin, Google Cloud and the rest.
Top posts
If You’re Not Refactoring Every Day, You’re Making a Mistake
1
Why Kotlin’s Result Type Falls Short for Handling Failures
4
Scalability Cheat Sheet #1 - From Basics to Replication
Pub/Sub and Batching: Optimizing Cloud Messaging Performance
Kotlin Type Aliases: Enhancing Code Clarity - Wednesday's Kotlin Kuppa #1
Recommendations
View all 8
The Engineering Manager
The Engineering Manager
James Stanier
ByteByteGo Newsletter
ByteByteGo Newsletter
Alex Xu
🔮 Crafting Tech Teams
🔮 Crafting Tech Teams
Denis Čahuk
The System Design Newsletter
The System Design Newsletter
Neo Kim
High Growth Engineer
High Growth Engineer
Jordan Cutler
© 2025 Mirco Franzek
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture