Description
Book SynopsisEffectively reading and understanding existing code is a developer's superpower. In this book, you'll master techniques for code profiling, advanced debugging, and log evaluation to find and fix bugs and performance problems. In
How To Read Java: Understanding, debugging, and optimizing JVM applications you will learn how to:
- Determine what code does the first time you see it
- Expose code logic problems
- Evaluate heap dumps to find memory leaks
- Monitor CPU consumption to optimize execution
- Use thread dumps to find and solve deadlocks
- Easily follow a service-oriented or microservices system
- Properly use logging to better understand Java app execution
- Use Java debuggers efficiently
How To Read Java: Understanding, debugging, and optimizing JVM applications teaches code investigation techniques that will help you understand how Java apps work, optimize them, and fix the bugs that break them. You'll go from the basics of debugging to advanced methods for locating problems in microservices architectures. Each new technique is explained with lively illustrations and engaging real-world examples. about the technology Tasks like searching for bugs, working through messy legacy code, and analyzing an application's readiness to support new features consume a lot of developer time. In fact, most developers spend more time trying to read and understand code than they do writing it! In this unique guide, you'll learn techniques like resolving deadlocks by examining thread dumps and locating memory leaks by inspecting the heap that will radically improve your efficiency when working with existing code in JVM languages like Java, Scala, and Kotlin.
Trade Review"I have never seen a book on debugging as thorough as this book. Knowing more about the techniques listed in this book will make development more efficient for any developer." Becky Huett
"This is a MUST-read book for any developer who is serious about debugging apps or software in general." Jean-Baptiste Bang Nteme
"Vital in filling in a gap for the practicing programmer." Atul Shriniwas Khot
