Home > Articles > Programming > Java

How to Become a Better Java Developer

Cay Horstmann, author of the classic Core Java and the thoroughly modern Core Java for the Impatient, wasn't always a Java expert. In this article, he talks about the psychology of becoming an expert developer. Learn the effective strategies he suggests for beginners and programmers who have mastered the basics.
Like this article? We recommend

Like this article? We recommend

Jennifer Bortel, an editorial director for InformIT, asked me to write about becoming a better Java developer, figuring I might know a thing or two about that since I just published Core Java for the Impatient. I agreed. Nothing could be easier—I'd just tell you to buy a copy of the book! But then she let it slip that I would have to write 1,500 words. So far, it's just about 77.

I recently received an email message from a developer who had been asked in a job interview why the following code isn't threadsafe:


class ThreadSafeClass extends Thread
     private static int count = 0;

     public synchronized static void increment()

     public synchronized void decrement()

My friend thought this example was threadsafe, and I agreed, pointing out that, after inserting the missing static in the second method, access was controlled by the intrinsic lock of the class object. I also said that this wasn't a very good interview question, since surely everyone who needed a threadsafe counter would just use an AtomicInteger.

But in the middle of the night, I woke up and wondered: Maybe the static wasn't accidentally missing; maybe some fiendish interviewer had purposefully constructed this example to trip up candidates. So I wrote again to say that I was wrong, and in the parallel universe of interview questions, the correct answer was that the second method holds a lock on an object.

The developer then asked whether I had a YouTube channel from which he could learn how to deal with interview questions like this one. Unfortunately, I don't. I teach computer science and write books, but my goal has always been for my students and readers to become better programmers, not better interview candidates.

Peter Norvig wrote a great blog article in which he argued that books promising to teach you Java in 24 hours, or 21 days, are ludicrous. It takes 10 years, or maybe 10,000 hours, to become an expert at anything. And it is well known that experts have a very different way of processing information than novices do. In a classic experiment, expert and novice chess players are shown a chessboard for a few seconds, and then are asked to reconstruct it. The novices don't do very well, but the experts have no problem remembering where all the pieces were. Under one condition, that is: The board had to be from an actual game. If the pieces were positioned randomly, the experts remembered their locations no better than the novices did.

That's what happened to me with the interview question. My expertise is programming, not passing interviews, so I instinctively filled in the missing keyword and went to the "wrong" conclusion. I would like to think that I still would have been hired once I explained what happened, and why I would never code like the example in the first place. If I wasn't hired, I probably wouldn't have wanted to work for that outfit anyway.

I don't think that studying for certification exams or preparing for interview questions will turn you into a better programmer. What also doesn't work—though, as a book author, it pains me to tell you this—is buying more programming books and reading them cover to cover. On the other hand, a really good way of becoming a better programmer is to do more programming.

Every so often, I teach an introductory course in computer science at my university. It is by far the hardest course I teach—much harder than a graduate course. When I first started work as a young professor, I dutifully lectured students on programming concepts, such as the difference between while loops, for loops, and do loops, and I gave students four three-week projects to complete. That's how the subject had been taught since the beginning of time. The instructor of the second-semester course complained bitterly that most of the students, after an entire first semester of programming, still couldn't complete a simple loop. That too has been the case since the beginning of time. Remember FizzBuzz?

These days, I give beginning students lots and lots of automatically graded practice problems. By the end of the first semester, they have written so many loops that they can regard loops as experts do—as constructs with a purpose, and not random statements.

That's hardly revolutionary. When you learn a foreign language, the majority of instruction is drill and practice, not theory. It is crucial to push knowledge into the subconscious brain. Once you no longer need to actively think about each loop, or (in the case of French), about each irregular verb, you can go on to the next level.

The key is instant feedback. The autograder tells students right away when they did something wrong, and when they got it right. Some psychologists believe that we could do much more with computerized training and instant feedback. For example, in another classic experiment, novice pilot trainees took a training session in which they were required, over and over, to look at an instrument panel and describe the motion of the plane. They got instant feedback indicating whether they were right, and after two hours of training they outperformed seasoned pilots. Of course, that didn't mean they could start flying, but they no longer were nervous about all those dials on the instrument panel.

So, if you are just starting out learning Java, it is a great idea to do lots of drill-and-practice assignments. There are a good number of websites and online courses with automatically graded coding practice. Pick one that offers realistic problems, not gibberish code. After all, you want your subconscious to do well with the kind of code that you will actually write in practice. That's why I am not so keen on programming examples that use contrived situations, such as animal classes with methods that meow and bark.

After a while, you will have mastered the basics of programming. To go to the next level, you will want to complete projects. A couple of years ago, InformIT asked many experienced programmers this question: "What's the Best Way for a Programmer to Learn a New Language?" By far the most common answer: Put it to work in an actual project. Find something that you've always wanted to implement, and get going.

Twenty years ago, when Java had just got started, my friend and sometimes co-author Gary Cornell called me and said, "Cay, we are going to write a Java book." I pointed out that neither of us knew a thing about Java, but he said, "So what? We have a book contract." We had to hurry, because someone else had already announced "Teach Yourself to be a Java Dummy in 24 Hours," or some such title. And so I wrote a program that put up a user interface for retirement planning, a program that connected to a weather site and displayed a weather report, and a program that simulated cars moving along a freeway. (Those were exciting programs at the time.) In the process, I had no choice but to learn java.awt, java.net, and threading. And I had to learn how to actually get it to work, not just what the documentation said. At the time, those were entirely different things. That's why Core Java [1] was a hit when it came out—it was not for dummies.

Learning Java was much harder back then, because we had no sites like Stack Overflow. That relates to my next bit of advice: When you work on your pet project, you will get stuck, and then it is a really good idea to go to such a forum and try to find answers. At first, you'll have the same questions that everyone else already asks. But soon you will have become enough of an expert that your questions are more unique. That's a tremendous way to learn. Of course, you don't just want to dump some code and ask, "Now what?" You want to distill the code down to its essence and explain what research you already did before you got stuck. Most of the time, I say "duh" before I am done submitting the query, because the answer became clear in the process. And if it didn't, well, thoughtful questions tend to attract thoughtful answers. Be sure to pay back your social debt by answering other people's thoughtful questions. In both processes, you are becoming a better programmer.

But what about books? Are they obsolete, thanks to Google and Stack Overflow? Whenever I start out wrestling with a new technology, I figure that I am a manly man, and I can go it alone. After an hour of wasting my time, sanity sets in, and I buy a book. Nowadays, technical books are an unbelievable bargain. If I pay $40 for an e-book and get a quick answer for just one question, I got my money's worth already. It pains me to tell my fellow book authors this, but I never read the books from the beginning to the end. I dive right in where I think my problem and its solution are described, and I read just enough to pick out what I need. For that reason, nowadays I try to write books that can be read that way—hence the Impatient series.

Now I really need to stop—I have exceeded 1,500 words. In a nutshell, to become a better programmer, start by recognizing that there are many layers of expertise. At the beginning, push the basic language constructs into your subconscious mind through lots of drill and practice. As soon as possible, get to work on real projects that interest you. And then join a community where you can ask and answer questions. When you've done all that, you'll be able to speak with passion and experience in a job interview, and it won't matter whether you get tripped up by a contrived puzzle question.


[1] Gary Cornell and Cay S. Horstmann, Core Java. Prentice Hall PTR, 1996.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020