backend-jvm-language-review

To review JVM code, analyze Java and Kotlin files for immutability, Optional discipline, null safety, and coroutine patterns that compile cleanly but cause brittle behavior. This audit spots language-level design issues in domain classes and value objects before they become maintenance debt.

Common Java and Kotlin idiom bugs in Spring codebases include unnecessary mutability, awkward exception handling, improper var usage, and non-idiomatic coroutine launching. Code may compile cleanly but still exhibit these issues across domain classes, value objects, and concurrency usage.

Checking Kotlin null safety and data class usage requires auditing source files for proper scope functions, sealed classes, and coroutine launching patterns. This ensures the codebase follows modern JVM design principles and avoids awkward exception handling or unnecessary mutability.

Yes, this JVM code review supports both Java records and Kotlin sealed classes. It explicitly checks these types alongside immutability, equals/hashCode/toString consistency, and data classes to ensure idiomatic modern JVM design across the audited codebase.

You should audit JVM code for Optional discipline and try-with-resources patterns when reviewing Spring or other JVM codebases for language-level design issues. This check prevents awkward exception handling and resource leaks that compile cleanly but cause runtime brittleness.