Attack of the Clones: How Kotlin Design Patterns Save the Day (Again)

If you’ve ever had the pleasure of working with generated classes—whether from Protobuf, Swagger, or yet another “magical” schema tool—you’ll know they’re about as customizable as a locked-down corporate laptop. The result? Multiple classes that all do basically the same thing (e.g., PersonA, PersonB, PersonC) but refuse to share a single interface. In Kotlin, this... Continue reading

Taming the Optional Beast When Interfacing Between Java and Kotlin – Without Losing Your Sanity or Null Safety

So you've got a Kotlin codebase that you love more than your morning coffee, and yet there’s still that pesky legacy Java component that’s holding on for dear life. Somewhere in there is Optional<T> – Java's fancy way of saying “maybe it’s there, maybe it’s not,” which Kotlin takes very, very personally. If you’ve ever... Continue reading