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

Explain the tools used to monitor system security.

12.Explain the tools used to monitor system security. Ans. 1. People who, for purpose of larceny or to amuse themselves, like to break into computers, they are called ‘crackers’. 2. If there is a vulnerability in a system they will find it and use it against you. 3. Preventing use of your machine for nefarious purpose and guarding against intrusion are, in the end, your responsibility alone. 4. Red hat equips you with tools to detect and deal with unauthorised access of many kinds. 5. You need to configure those tools and understand how to sense the warning they provide. 6. Fortunately Linux is development community is quick to find potential exploits and to create ways of slamming the doors before crackers can enter in your system. 7. Red hat is careful enough to making available new, patched version in which potential exploits have been found. 8. You should make sure to download and install the repaired package. 9. This line of defence...

Explain the file systems supported by Linux.

21.Explain the file systems supported by Linux. Ans. 1. Linux can read/write to several file system that originated with other operating system much different from Linux. 2. One reason that Linux supports so many file systems is the design of its virtual file system (VFS) layer, its provides a fairly universal forms of file support, file systems supported by Linux are as follows: 3. ext3: • Ext3 stands for third extended file system. • Starting from Linux Kernel 2.4.15 ext3 was available. • The main benefit of ext3 is that it allows journaling. • Journaling has a dedicated area in the file system, where all the changes are tracked. • When the system crashes, the possibility of file system corruption is less because of journaling. (If no journaling, then fsck command (file system consistency check) is used to check for the corrupted file and to repair that file). • ext3 keeps a record of uncommitted file transactions and applies only those transactions when the sy...

Explain the rc script and how they can be managed by manually.

18.Explain the rc script and how they can be managed by manually. Ans. 1. ‘rc’ scripts are stored in ‘/etc/rc.d’ directory, rc scripts are used to stop and start services for runlevels. 2. In ‘/etc/rc.d’ directory we have some additional directories rc0.d, rc1.d, rc2.d, rc3.d, rc4.d, rc5.d and rc6.d, the numbers in directory name corresponds to the runlevel and contains the scripts for runlevels. 3. For example let’s take runlevel 5, init program looks in the ‘/etc/rc.d/rc5.d/’ directory for the processes to start and stop. 4. All the scripts in the rc5.d directory are symbolic like to the actual scripts that are located in the ‘/etc/rc.d/init.d/’ directory. The use of symbolic link means that the runlevel can be modified by adding or removing symlinks or changing the order the script run. 5. rc scripts contains symbolic links which can be modified to change the runlevels. 6. Symbolic links begins with a ‘k’ and a number or an ‘s’ and a number. Example: S25netfs -...