Kotlin in Action
by Dmitry Jemerov
Reading Profile
Should I read this?
Practical and example-driven, this is a hands-on introduction to Kotlin that emphasizes readable code, safety features, and how to make Kotlin interoperate with existing Java projects. Chapters pair short explanations with runnable samples, notes about IDEs and build tools, and concrete advice for calling Java from Kotlin. What works best is teaching usable Kotlin patterns you can drop into a JVM codebase; the main limitation is a steady Java orientation and tooling detail that will feel dense if you wanted a lightweight, purely idiomatic language tour.
Read this if...
- •Java backend developer maintaining a legacy codebase who needs to introduce Kotlin gradually — because the book shows interoperability patterns and migration-friendly examples.
- •Android app developer starting a new project who wants concise syntax and practical patterns — because sample-driven chapters and tooling notes speed up real app development.
- •Full-stack engineer integrating a Kotlin library into an existing Java framework who must understand bytecode, interop quirks, and IDE/build-tool expectations — because the book focuses on making Kotlin and Java work together.
Skip this if...
- •You’ll likely put it down when chapters dig into Java interop, bytecode/IDE details, and build-tool configurations if you wanted a short syntax tour — those sections are the most common drop-off point.
- •Annoying if you prefer language-theory or design-focused writing rather than pragmatic examples and recipes; the prose favors applied code over abstract rationale.
- •No exercises: frustrating if you want a hands-on workbook or practice problems rather than annotated examples and reference-style samples.
Kotlin is a new Programming, language targeting the Java platform. It offers on expressiveness and safety without compromising simplicity, seamless interoperability with existing Java code, and great tooling support. Because Kotlin generates regular Java bytecode and works together with existing Java libraries and frameworks, it can be used almost e...
Before You Buy
Reading Specifications
Difficulty:hard
Audience Fit
- Java backend developer maintaining a legacy codebase who needs to introduce Kotlin gradually — because the book shows interoperability patterns and migration-friendly examples.
- Android app developer starting a new project who wants concise syntax and practical patterns — because sample-driven chapters and tooling notes speed up real app development.
- Full-stack engineer integrating a Kotlin library into an existing Java framework who must understand bytecode, interop quirks, and IDE/build-tool expectations — because the book focuses on making Kotlin and Java work together.
- You’ll likely put it down when chapters dig into Java interop, bytecode/IDE details, and build-tool configurations if you wanted a short syntax tour — those sections are the most common drop-off point.
- Annoying if you prefer language-theory or design-focused writing rather than pragmatic examples and recipes; the prose favors applied code over abstract rationale.
- No exercises: frustrating if you want a hands-on workbook or practice problems rather than annotated examples and reference-style samples.
Check formats, pricing, and availability options for Kindle, physical print, or audiobooks directly.
View available editions on AmazonKey themes
Why recommended
appears in Kotlin, Programming, and Technology.
Recommendation Signals
Recommendation proof is sourced from public posts, interviews, reading lists, and cited references.
No verified recommendation proof available yet.
Appears In
Not sure if this is the right fit?
Consider Accidental Presidents by Jared Cohen. Recommended by 10 sources.
“Accidental Presidents offers eight narrative portraits of men who succeeded to the U.S. presidency without election, using anecdote-rich scenes and readable context to show how personality and circumstance interact with office power. It’s strongest as a set of self-contained stories that make succession stakes concrete for non-specialist readers; it does not prioritize dense archival argument or exhaustive methodology, so expect some interpretive generalizations and repeated themes across cases. Use it for fast historical orientation rather than scholarly deep-dives.”
Similar books
How recommendation signals are reviewed
Each recommendation is collected from a public source — interviews, articles, or curated lists — and linked to its original URL. Books with many verifiable recommendations from respected people rank higher.