Digital List Price:	CDN$ 53.99
Print List Price:	CDN$ 68.31
Kindle Price:	CDN$ 48.96 Save CDN$ 19.35 (28%)
	includes free international wireless delivery via *Amazon Whispernet*

97 Things Every Java Programmer Should Know: Collective Wisdom from the Experts by [Kevlin Henney, Trisha Gee]

Follow the Authors

Trisha Gee

Kevlin Henney

97 Things Every Java Programmer Should Know: Collective Wisdom from the Experts 1st Edition, Kindle Edition

by Kevlin Henney (Author, Editor), Trisha Gee (Author, Editor) Format: Kindle Edition

38 ratings

See all formats and editions

Amazon Price

New from

Used from

Kindle Edition

"Please retry"

$48.96

—

Paperback, Illustrated

"Please retry"

$51.54

$34.68

$44.01

Kindle Edition
$48.96 Read with Our Free App
Paperback
$51.54

14 Used from $44.01 19 New from $34.68

If you want to push your Java skills to the next level, this book provides expert advice from Java leaders and practitioners. You’ll be encouraged to look at problems in new ways, take broader responsibility for your work, stretch yourself by learning new techniques, and become as good at the entire craft of development as you possibly can.

Edited by Kevlin Henney and Trisha Gee, 97 Things Every Java Programmer Should Know reflects lifetimes of experience writing Java software and living with the process of software development. Great programmers share their collected wisdom to help you rethink Java practices, whether working with legacy code or incorporating changes since Java 8.

A few of the 97 things you should know:

"Behavior Is Easy, State Is Hard"—Edson Yanaga
“Learn Java Idioms and Cache in Your Brain”—Jeanne Boyarsky
“Java Programming from a JVM Performance Perspective”—Monica Beckwith
"Garbage Collection Is Your Friend"—Holly K Cummins
“Java's Unspeakable Types”—Ben Evans
"The Rebirth of Java"—Sander Mak
“Do You Know What Time It Is?”—Christin Gorman

ISBN-13

978-1491952696
Edition

1st
Sticky notes

On Kindle Scribe
Publisher

O'Reilly Media
Publication date

May 15 2020
Language

English
File size

30407 KB
See all details

Due to its large file size, this book may take longer to download

See all supported devices

Product description

About the Author

Kevlin Henney is an independent consultant and trainer. His work focuses on patterns and architecture, programming techniques and languages, and development process and practice. He has been a columnist for various magazines and online publications, including The Register, Better Software, Java Report, CUJ, and C++ Report. Kevlin is co-author of two volumes in the Pattern-Oriented Software Architecture series: A Pattern Language for Distributed Computing and On Patterns and Pattern Languages. He also contributed to 97 Things Every Software Architect Should Know

--This text refers to the paperback edition.

Product details

ASIN ‏ : ‎ B088P8GV8X
Publisher ‏ : ‎ O'Reilly Media; 1st edition (May 15 2020)
Language ‏ : ‎ English
File size ‏ : ‎ 30407 KB
Simultaneous device usage ‏ : ‎ Unlimited
Text-to-Speech ‏ : ‎ Enabled
Screen Reader ‏ : ‎ Supported
Enhanced typesetting ‏ : ‎ Enabled
X-Ray ‏ : ‎ Not Enabled
Word Wise ‏ : ‎ Not Enabled
Sticky notes ‏ : ‎ On Kindle Scribe
Print length ‏ : ‎ 372 pages

Best Sellers Rank: #1,090,705 in Kindle Store (See Top 100 in Kindle Store)
- #307 in Java Programming (Kindle Store)
- #817 in Software Development
- #1,080 in Java Programming (Books)

Customer Reviews:
38 ratings

About the authors

Follow authors to get new release updates, plus improved recommendations.

Trisha Gee
Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.
Trisha has been working with Java since 1997, when her university was forward-looking enough to adopt this “shiny new” language to teach computer science. Since then, she’s worked as a developer and consultant, creating Java applications in a range of industries including banking, manufacturing, nonprofit, and low-latency financial trading.
Trisha is super passionate about sharing all the stuff she learned the hard way during those years as a developer, so she became a Developer Advocate to give her an excuse to write blog posts, speak at conferences, and create videos to pass on some of her knowledge. She spent five years as a Java Developer Advocate at JetBrains, and another two years leading the JetBrains Java Advocacy team. During this time she learned a lot about the kinds of problems real Java developers face.
See more on the author's page
Kevlin Henney
Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.
I'm an independent consultant, international speaker, writer and trainer. I live in Bristol and online.
My software development interests are in patterns, programming, practice and process. As well as contributing to a number of projects, I've been involved in (far too) many committees (for conferences, publications and standards, but as yet I've not been on a committee for committees).
My fiction writing tends to the short side — and occasionally to the dark side — spanning a number of genres.
See more on the author's page

Kevlin Henney
185
Kindle Edition
1 offer from $42.99
Joshua Bloch
1,349
Kindle Edition
1 offer from $31.72
Richard Monson-Haefel
109
Kindle Edition
1 offer from $17.59
Emily Freeman
44
Kindle Edition
1 offer from $50.68
Ian F. Darwin
37
Kindle Edition
1 offer from $78.53
Emil Stolarsky
42
Kindle Edition
1 offer from $20.44

Customer reviews

3.9 out of 5

38 global ratings

5 star		46%
4 star		24%
3 star		16%
2 star		9%
1 star		6%

How are ratings calculated?

Top reviews from other countries

Amrut P.

Nothing Great

Reviewed in Germany 🇩🇪 on November 7, 2021

Verified Purchase

There is nothing great to read in this book. The topic are really basic and you might have already heard of these via conference videos.
Better spend the 35 euros on other books.

One person found this helpful

Carlos Saltos

Why I did not find it before !!

Reviewed in Germany 🇩🇪 on November 27, 2020

Verified Purchase

A good book for nowadays development and not only for Java (Scala and other JVM languages can be included too). I love the sharing of so many experiences of such great people. The book is gold !!

Nilendu Misra

Relatively weaker book in the "97 Things" Series

Reviewed in the United States 🇺🇸 on August 20, 2020

Verified Purchase

It is difficult to aggregate “collective wisdom from the experts” for programming languages with ever-changing landscapes. Either the advice veers strongly toward “my opinion from that experience 7 years ago” (stale) or generally accepted good practice, often obvious, like “encapsulate everything”. This is a relatively weaker book in the series. The “actionable idea density” is fairly low. About 15 of the items are generic hand waving, a similar number on low level constructs (coroutines, record, new Garbage Collection algorithm etc) and a handful meet the high standard of codifying in a book.

Some ideas, opinions and tips I got from the book -

As apps move to serverless architectures, where the deployment units can be single functions, the benefits we get from application frameworks diminish.

“We have to reinvent the wheel every once in a while, not because we need a lot of wheels; but because we need a lot of inventors”

Ergonomics of older JVMs are fooled when running inside docker containers.

Containers’ key benefit - reduce the coupling between an app and the underlying platform.

JVM ergonomics enables JVM to tune itself by looking at two env metrics - (i) number of CPUs and (ii) available memory.

Behavior is easy, state is hard - offer only a carefully designed API surface for any state mutation. Hardest bugs are caused by inconsistent state.

One of the advantages of being a job hopper is that “I’ve seen the way many different teams work”.

Developer Productivity Engineering - practice and philosophy of improving developer experience through data.

Actor model reduces the consequences of mutable state by preventing sharing, and functional programming makes the state shareable by prohibiting mutation. Functional programs can be less efficient than imperative equivalents and may place a bigger burden on GC. Functions facilitate the use of reactive programming paradigm consisting in asynchronous processing of stream of events.

Countdownlatch is a powerful tool but blocks the current thread. Different concurrency models don’t play well together.

Imperative - code explicitly telling the computer what to do. Declarative - code expressing a goal abstracting over the way in which the goal is achieved.

You aren’t paid to write code. Change your focus from writing code to delivering software. Your job is designing change, not code. Code is a detail. Designing change means feature flags

Localizing the scope of anything that is variable into a supporting method makes the top-level code predictable. Broadly, trying to lock down anything that does not vary makes you think more carefully about design and flushes out potential bugs.

Embrace SQL thinking - the biggest failing of applied OO programming is the belief that you should faithfully reproduce your domain model in code. It leads to unnecessary classes. SQL is declarative and is a data DSL.

In the early 2000s, most Java developers were actually full-stack developers - they just did not know because the phrase had not yet been coined!

Heap access is geologically slow compared to instruction processing, so modern computers use caches.

Java profilers use either byte code instrumentation or sampling. Flame graph sorts and aggregates the traces up to each stack level.

Uncertainty is when we cannot quantify the risk.
Risk = (Likelihood of Failure X Worst-case impact of Failure)

Playing the lottery is low-risk, Free solo climbing is high risk.

Large, infrequent releases are riskier. There is no way to reduce the impact of a failure - the worst case is still the ENTIRE system down and incur severe data loss, but we lower the likelihood of failure with smaller releases.

Naming is important - Orwell said - “the worst thing one can do with words is surrender to them”.

Technical classes (e.g., Hashmap) rarely have a place in the vocabulary of the domains we’re working in. The need for utility classes should be a red flag that you’re missing an abstraction.

Try to crash your JVM to learn deep stuff - e.g., try using Unsafe to get access to low-level stuff (e.g., memory management)

Cost of going to RAM, relative to registers, kept growing.Thus, cache-friendly code is a much researched area.

Fun can have different faces - Exploration (focused investigation); Play (no goal, for its own sake); Puzzles (rules with a goal); Games (rules with a winner) and Work (satisfying goal).
Kintsugi is a Japanese art where a precious broken object - rather than thrown away - is put back together using gold powder along its cracking lines. We should similarly learn how to fix legacy code that should make us similarly proud.

Package-by-layer structure (e.g., tld.domain.project.controllers, ..model, ..service etc) for your classes requires a lot of methods to be public. In order to benefit from package-private access protection, package-by-feature package hierarchy is a better organizing principle (e.g., tld.domain.project.company, ..user etc). The latter reduces coupling.

Service hedging - multiple idempotent calls to identically configured service instances on discrete nodes are launched and all but the fastest response discarded.

Boolean literals are worse than hard coded numbers - a 42 in code might look familiar, but a “false” could be anything and anything could be false.

Classes that represent Value objects don’t need getters or setters. Why Java 14 introduced a record structure.

Marginality : what is the average diminishing marginal return of adding developers to a team?

Programmers writing automated tests suffer from positive test bias. Fuzz testing is an unreasonably effective technique for negative testing that is easy to include in automated test suites.

Comment only what the code cannot say. Code says “what”, comments should say “why”.

10 people found this helpful

PATRICK SWEENEY

Met expectations - diverse stories on Java for the people who love Java

Reviewed in the United States 🇺🇸 on November 21, 2020

Verified Purchase

This is a book to read, mark up, and pass around you team. Some of the "things" are purely technical and quirky (43 Java's Unspeakable Types) and stuff you should be using and probably are not (47 Know Thy Flatmap). There's 97 of them, so they don't all need to be home runs.

Sherman P. Winkledink

I KNOW JAVA

Reviewed in the United States 🇺🇸 on September 15, 2021

Verified Purchase

I was able to get a job at a FAANG company and have put my entire family in 4 bedroom houses across the bay area. This book is a life changer!

Amazon Music Stream millions of songs	Amazon Advertising Find, attract, and engage customers	Amazon Business Everything for your business	Amazon Drive Cloud storage from Amazon	Amazon Web Services Scalable Cloud Computing Services

Book Depository Books With Free Delivery Worldwide	Goodreads Book reviews & recommendations	IMDb Movies, TV & Celebrities	Amazon Photos Unlimited Photo Storage Free With Prime	Shopbop Designer Fashion Brands

Warehouse Deals Open-Box Discounts	Whole Foods Market We Believe in Real Food	Amazon Renewed Like-new products you can trust	Blink Smart Security for Every Home

Follow the Authors

97 Things Every Java Programmer Should Know: Collective Wisdom from the Experts 1st Edition, Kindle Edition

Product description

About the Author

Product details

About the authors

Trisha Gee

Kevlin Henney

Customers who bought this item also bought

Customer reviews

Top reviews from Canada

Top reviews from other countries