My first encounter with the Java programming language was during a one-week Java training session in 1997.
I did not get a chance to use Java in a project until 1999. I read two Java books and took a Java 2 programmer
certification examination. I did very well on the test, scoring 95 percent. The three questions that I missed
on the test made me realize that the books that I had read did not adequately cover details of all the topics. I
made up my mind to write a book on the Java programming language. So, I formulated a plan to cover most
of the topics that a Java developer needs to use Java effectively in a project, as well as to become certified. I
initially planned to cover all essential topics in Java in 700 to 800 pages.
As I progressed, I realized that a book covering most of the Java topics in detail could not be written in
700 to 800 pages. One chapter alone that covered data types, operators, and statements spanned 90 pages.
I was then faced with the question, “Should I shorten the content of the book or include all the details that
I think a Java developer needs?” I opted for including all the details in the book, rather than shortening
its content to maintain the original number of pages. It has never been my intent to make lots of money
from this book. I was never in a hurry to finish this book because that rush could have compromised the
quality and coverage. In short, I wrote this book to help the Java community understand and use the Java
programming language effectively, without having to read many books on the same subject. I wrote this
book with the plan that it would be a comprehensive one-stop reference for everyone who wants to learn
and grasp the intricacies of the Java programming language.
One of my high school teachers used to tell us that if one wanted to understand a building, one
must first understand the bricks, steel, and mortar that make up the building. The same logic applies to
most of the things that we want to unde
1