Whether you’re starting out trying to learn a new skill, there’s no denying you’re going to make some new mistakes along the way, perhaps even more so than any other skill when it comes to coding. If you’re new to coding, Java is a great place to start, but it’s true that it’s not as simple as it may first appear.
Today, we’re going to highlight some of the key mistakes you’re probably making as a new beginner Java coder, as well as how to correct them, ensuring you’re becoming the best you can be and developing the best habits possible. Let’s get into it.
Ignoring Exceptions
One of the biggest mistakes made by beginner coders is not writing code to handle expectations. In essence, it’s just lazy, and of course your code is going to run perfectly when everything is cut and dry, but sooner or later you’re going to need to introduce this term, so implement it early to develop the healthy habit.
Of course, this can change a lot depending on what you’re coding, so be mindful of when and where you can use them. The truth is, a few seconds of adding in an exceptions code can save you hours in the long term.
For example;
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
public class Sum { public static void main(String[] args) { int a = 0; int b = 0;
try { a = Integer.parseInt(args[0]); b = Integer.parseInt(args[1]);
} catch (NumberFormatException ex) { }
int sum = a + b;
System.out.println("Sum = " + sum); } } |
Notice how the catch block is empty and it will fail. Instead, you’ll want to adjust by printing the stack trace, like so;
|
1 2 3 4 5 6 7 |
try { a = Integer.parseInt(args[0]); b = Integer.parseInt(args[1]);
} catch (NumberFormatException ex) { ex.printStackTrace(); } |
Implementing Less Restrictive Modifiers
If you use access modifiers but you don’t refer or take care of the visibility in any way, you can bet your bottom dollar you’re going to run into some problems. The Java coding language uses four main access modifiers; public > protected > default > private.
The least restrictive is, of course, public, and then it gets more restrictive along the line. Make sure you’re taking your time to learn which access modifiers are best for which part of the code, so you keep everything running smoothly. Ideally, you’ll want to use the most restrictive modifier possible in every situation.
Forgetting to Use Free Resources
There are a ton of free resources out there to help you learn to code Java, whether you’re looking at YouTube, blog posts, online guides, books, eBooks, and much more. No matter what kind of coding you’re facing, what kind of information you need, or what kind of problem you’re trying to overcome, you can bet there’s a free resource out there that can help.
Don’t forget about them when it comes to expanding your knowledge base and the information you have access too!
Not Checking the Versions of Said Resources
Hand in hand with the consideration above, it’s important to make sure you’re checking your resources, both paid and free, to ensure they are in date and the information provided is still relevant.
You don’t want to pour your heart and soul into learning about the language or an approach to the language, only for it to be outdated or contain errors. True, not much changes too often, but it’s something you need to be aware of.
You wouldn’t get advice from someone who doesn’t know what they’re talking about in any other subject, so why do the same here?
Not Using Closing Curly Braces
The curly brace bracket ( { ) is one of the most common forms of bracket to be used in java coding, and forgetting to use a } bracket at the end of a line of code can cause so many problems, it’s unreal.
The best way to counter this is use both {} brackets together, and then click the space in-between to write your code. This way, you know it’s always going to be closed and won’t cause you any problems.
Molly Crockett is a tech writer and blogger at Essayroo.com online writing service.