Skip to main content

Top 10 Most Common Mistakes That Java Developers Make: A Java Beginner’s Tutorial (Publication)

Top 10 Most Common Mistakes That Java Developers Make: A Java Beginner’s Tutorial (Publication)

Java, a sophisticated programming language, has been dominating a number of ecosystems for quite a while. Portability, automated garbage collection, and its gentle learning curve are some of the things that make it a great choice in software development. However, like any other programming language, it is still susceptible to developer mistakes. This article explores the top 10 common mistakes Java developers make and some ways of avoiding them.

Common Mistake #1: Neglecting Existing Libraries

It’s definitely a mistake for Java Developers to ignore the innumerable amount of libraries written in Java. Before reinventing the wheel, try to search for available libraries - many of them have been polished over the years of their existence and are free to use. These could be logging libraries, like logback and Log4j, or network related libraries, like Netty or Akka. Some of the libraries, such as Joda-Time, have become a de facto standard. The following is a personal experience from one of my previous projects. The part of the code responsible for HTML escaping was written from scratch. It was working well for years, but eventually it encountered a user input which caused it to spin into an infinite loop. The user, finding the service to be unresponsive, attempted to retry with the same input. Eventually, all the CPUs on the server allocated for this application were being occupied by this infinite loop. If the author of this naive HTML escape tool had decided to use one of the well known libraries available for HTML escaping, such as HtmlEscapers from Google Guava, this probably wouldn’t have happened. At the very least, true for most popular libraries with a community behind it, the error would have been found and fixed earlier by the community for this library.Click here for full article

Original article:

http://www.toptal.com/java/top-10-most-common-java-development-mistakes


Comments

Popular posts from this blog

Java,ES,QT practical files

All practical files: Click below to start download Uploaded on special request||||

How to configure Network file system version 4 (NFSv4) client?

69.How to configure Network file system version 4 (NFSv4) client? Ans. 1. There are two new options listed in NFSv4 are introduced as: clientaddr and ports 2. The version 3 of NFS introduced NFS over TCP, which improved NFS’s reliability. 3. In NFSv3, users use the mount option i.e., tcp as client whether client wants to use TCP or UDP to communicate with the server. NFSv4 replaces tcp or udp with a single option i.e. ports=tcp or udp 4. The default buffer size for NFSv4 is 8192 bytes, but it can grow to as large and by 32,678 bytes, which results performance improvements. 5. Following are the mount options: clientaddr=n – Declares client to be multihomed proto=type – Declares port as either udp or tcp resize=n – declares read size of clients buffer wsize=n – Declares write size of clients buffer sec=mod – Declares security model as either krb, krb5 etc.

Absolute Links vs. Relative Links – SEO Value

Absolute Links vs. Relative Links – SEO Value The debate between  absolute links and relative links  continues to live on in the SEO world. The individual significance of each has been contested, but it is widely regarded that absolute links provide better SEO value on the whole than relative links. Many believe that absolute links have less potential for getting messed up when search engines index your page. It shouldn’t really make a difference, but many conclude that this is reason enough. Read more...