Basic Java Tutorial For Beginners

Getting Started With Java

You need three things before writing any code: a JDK installation, a text editor or IDE, and roughly twenty minutes to figure out why your first program won't compile. I installed Java on Windows at 2 AM once and wasted forty-five minutes because PATH wasn't set correctly. The error message literally said nothing useful. Just run java -version and javac -version separately after installing. If one works and the other doesn't, you have a PATH issue. Java is verbose by design. That's not a bug, it's the point. Every Java program needs a class, and every class needs a main method if you want to run it. Here's what that looks like: Save that file as Hello.java. The filename has to match the public class name exactly. I still see people skip this and then spend an hour wondering why the compiler complains about "class Hello is public, should be declared in a file named Hello.java."

To compile: javac Hello.java. To run: java Hello. That's the full lifecycle for a standalone program. No build tools, no frameworks, just the command line.

Variables and Types

Java is statically typed. You declare the type once and the compiler enforces it forever after. There's no implicit conversion from int to double either. This catches errors early but irritates people coming from Python. One thing beginners consistently miss: integer division. 5 / 2 gives you 2, not 2.5. Both operands are ints, so Java truncates the decimal. You need 5.0 / 2 or (double) 5 / 2 to get a floating point result. I spent weeks debugging a pricing calculation that was silently truncating before I caught it. if/else, for loops, and while loops work the same way they do in most C-style languages. The for-each loop is where Java actually gets nice:

But here's something most tutorials don't emphasize: the enhanced for loop creates a copy of the reference, not the element itself. If you're iterating over objects and trying to modify them in place through the loop variable, you're modifying the reference, not the object. For primitive arrays it doesn't matter. For object arrays it matters a lot. A method is just a function attached to a class. Return type goes first, then the name, then parameters in parentheses. The new keyword creates an instance. Without it, you can only call static methods. That's why main is static. It runs before any instance exists.

Every class has a constructor, even if you don't write one. The compiler inserts a no-arg version by default. Once you write any constructor at all, that default disappears. This bit me on a project where I added a parameterized constructor and suddenly everything that relied on the no-arg version started throwing compilation errors. Use this to distinguish between the parameter and the field. Without it, you're just assigning the parameter to itself. Strings in Java are immutable. Every operation that seems to modify a string actually creates a new one. String.concat(), substring(), replace() — they all return new strings. If you're doing heavy string manipulation in a loop, you're creating garbage at an alarming rate.

Use StringBuilder instead. It mutates in place. The difference between concatenating strings in a loop and using StringBuilder is the difference between a program that takes 3 seconds and one that takes 3 milliseconds when you hit large datasets.

StringBuilder sb = new StringBuilder();
for (int i = 0; i 10000; i++) {
    sb.append(i).append(", ");
}
String result = sb.toString();

Common Pitfalls

Null pointer exceptions. Every Java developer sees them. The fix isn't complicated — just check for null before dereferencing. But in practice, null checks everywhere makes code noisy. The real issue is usually that someone passed null up the call stack without documenting it. Array index out of bounds. Arrays are zero-indexed. The last element is at length - 1, not length. I've written this mistake more times than I care to admit. Comparing strings with ==. This is the one that costs people interviews. == checks reference equality, not content equality. Use .equals() instead. Always. == on strings will work sometimes by accident because of string interning, then fail unpredictably when it doesn't.

What Java Isn't Good At

It's slow to write. For quick scripts or one-off automation, Python or even PowerShell does the job faster. Java's verbosity pays off at scale but hurts at small scale. You also need to understand the build tool ecosystem — Maven or Gradle — before you can do anything non-trivial. The learning curve is steep because there are so many conventions to absorb before you feel productive. If you're just learning to program, consider starting elsewhere. Java is better suited for people who already understand programming basics and want to work in enterprise environments. The syntax is rigid, which is good for teaching discipline but painful for experimentation.

Where to Go From Here

Write a program that reads a file and counts words. Then one that parses CSV data. Then one that connects to a database. That's the actual progression. Tutorials that spend six chapters on syntax without a concrete project are wasting your time. The concepts only stick when you break them against something real. The official Oracle documentation is decent for reference but terrible for learning. docs.oracle.com/en/java/ has the Javadoc and language specification. Use it when you're stuck, not when you're starting. Download the JDK from adoptium.net if you don't want Oracle's licensing setup. Eclipse or IntelliJ IDEA Community Edition for editing. Both are free. IntelliJ has better auto-completion but takes longer to index large projects.