brain storming

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