Java | Classes and Objects

A class is a blueprint; an object is one runtime instance created from it. Keep the blueprint focused on one concept and create objects with valid initial state. The goal is not to mirror database columns or screens mechanically, but to give meaningful data and operations one dependable boundary.

Class Versus Instance

The class defines fields and methods; each object has its own field values. This distinction matters whenever two accounts, requests or products must behave independently.

Create Valid Objects

Use a constructor or factory to require essential values at creation. An object that starts invalid forces every later method to defend against a state that should never have existed.

Use Clear Instance Methods

An instance method operates on the state of one object. Keep it close to the data it owns so the caller does not have to manually coordinate related fields.

Avoid Shared Mutable Defaults

Do not accidentally place per-object state in static fields. Static mutable state is shared by every instance and requires a deliberate concurrency and lifecycle policy.

Worked Examples

Example 1: Create Two Independent Objects

Each instance receives and retains its own name. Changing one object would not change the other because the field belongs to the instance, not the class.

Java

public class User {
    private final String name;

    public User(String name) { this.name = name; }
    public String name() { return name; }
}

User first = new User("Ada");
User second = new User("Lin");

Expected Result

first=Ada, second=Lin

Example 2: Give an Object an Operation

The method uses the object's own state. A caller asks the object for its label instead of reconstructing the formatting rule in every place that needs it.

Java

public class Ticket {
    private final int id;

    public Ticket(int id) { this.id = id; }
    public String label() { return "ticket-" + id; }
}

System.out.println(new Ticket(42).label());

Expected Result

ticket-42

Example 3: Reject Missing Required State

Validation at construction ensures every created object has a usable name. Later methods can rely on that invariant rather than repeatedly checking for blank state.

Java

public class Project {
    private final String name;

    public Project(String name) {
        if (name == null || name.isBlank()) throw new IllegalArgumentException("name");
        this.name = name;
    }
}

Expected Result

A Project always has a non-blank name

Build and Practice Plan

Build confidence by changing one rule at a time. Start with the normal case, make the expected value visible, then add the nearest boundary and a rejected input. Keep Java syntax in service of the contract: a program is useful only when its behavior remains understandable as inputs, scale and failure conditions change.

Step 1: create one normal case, one boundary case and one rejected or failure case for class versus instance before expanding the implementation.
Step 2: create one normal case, one boundary case and one rejected or failure case for create valid objects before expanding the implementation.
Step 3: create one normal case, one boundary case and one rejected or failure case for use clear instance methods before expanding the implementation.
Step 4: create one normal case, one boundary case and one rejected or failure case for avoid shared mutable defaults before expanding the implementation.

Design Review Questions

Before accepting a change, identify the valid values, the owner of mutable state, the behavior for missing or invalid input and the test that proves the important boundary. Keep I/O, storage and framework wiring outside the small Java rule until the local behavior is proven.

A clear result is better than a hidden side effect. Name the condition, return the calculation where possible and let the outer layer decide whether to print, store or transmit it.

Example 4: Make the input visible

Start by naming the value the next line depends on. This keeps the lesson input explicit before we apply a transformation or call an external boundary. We are applying that habit while revisiting Java Classes and Objects.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

public class Main {
    public static void main(String[] args) {
        String lesson = "Java Classes and Objects";
        System.out.println(lesson.toUpperCase());
    }
}

Expected Result

JAVA CLASSES AND OBJECTS

Try next: Replace the sample value with one from your own notes, predict the result, and then run it.

Example 5: Make the input visible

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

public class Main {
    public static void main(String[] args) {
        String lesson = "Java Classes and Objects";
        System.out.println(lesson.toUpperCase());
    }
}

Expected Result

JAVA CLASSES AND OBJECTS

Try next: Replace the sample value with one from your own notes, predict the result, and then run it.

Example 6: Make the input visible

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

public class Main {
    public static void main(String[] args) {
        String lesson = "Java Classes and Objects";
        System.out.println(lesson.toUpperCase());
    }
}

Expected Result

JAVA CLASSES AND OBJECTS

Try next: Replace the sample value with one from your own notes, predict the result, and then run it.

Example 7: Guard an empty boundary

A small guard makes the allowed and rejected path visible. We want a caller to receive an intentional result instead of discovering an unexplained failure later. We are applying that habit while revisiting Java Classes and Objects.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

public class Main {
    static boolean accepted(String value) {
        return value != null && !value.isBlank();
    }

    public static void main(String[] args) {
        System.out.println(accepted("Java Classes and Objects"));
    }
}

Expected Result

true

Try next: Try an empty value as well as the normal value and describe why the two outcomes differ.

Example 8: Keep the transformation pure

This step returns a value instead of mixing the rule with display or storage work. That separation gives us a small unit we can run, test, and reuse. We are applying that habit while revisiting Java Classes and Objects.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

public class Main {
    static int doubleValue(int value) { return value * 2; }

    public static void main(String[] args) {
        System.out.println(doubleValue(6));
    }
}

Expected Result

Try next: Call the same rule twice with different inputs and confirm that each result depends only on its input.

Example 9: Make a branch deliberate

Use a named branch where the business rule changes. A future reader should be able to point at the condition and state the result for both sides. We are applying that habit while revisiting Java Classes and Objects.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

public class Main {
    public static void main(String[] args) {
        int score = 7;
        String result = score >= 5 ? "ready" : "review";
        System.out.println(result);
    }
}

Expected Result

ready

Try next: Change the boundary value by one and explain exactly which branch becomes active.

Example 10: Use a collection without hidden mutation

Collections become safer when we can see which value is read, which value is derived, and whether the original collection remains owned by the caller. We are applying that habit while revisiting Java Classes and Objects.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

import java.util.List;

public class Main {
    public static void main(String[] args) {
        List<String> lessons = List.of("Java Classes and Objects", "boundary");
        System.out.println(String.join(" | ", lessons));
    }
}

Expected Result

Java Classes and Objects | boundary

Try next: Add one more item and predict the derived result before executing the code.

Example 11: Return a named outcome

A named outcome is easier to test than an implied side effect. We can now distinguish a successful path from a rejected path without guessing from console noise. We are applying that habit while revisiting Java Classes and Objects.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

public class Main {
    record Outcome(String status, String lesson) {}

    public static void main(String[] args) {
        Outcome outcome = new Outcome("ready", "Java Classes and Objects");
        System.out.println(outcome.status());
    }
}

Expected Result

ready

Try next: Rename the outcome in your own words while preserving the same success and failure rule.

Example 12: Trace a small loop

Work through one value at a time. The point is not to memorize syntax; it is to see how the accumulator or output changes after each repeatable step. We are applying that habit while revisiting Java Classes and Objects.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

public class Main {
    public static void main(String[] args) {
        int total = 0;
        for (int value : new int[] {1, 2, 3}) total += value;
        System.out.println(total);
    }
}

Expected Result

Try next: Use a shorter collection first, then add one value and trace the extra iteration aloud.

Example 13: Keep display at the edge

The core rule prepares a value, while the outer line decides how to show it. That keeps the result usable by a UI, test, API, or command-line caller. We are applying that habit while revisiting Java Classes and Objects.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

public class Main {
    static String display(String value) { return "Lesson: " + value; }

    public static void main(String[] args) {
        System.out.println(display("Java Classes and Objects"));
    }
}

Expected Result

Lesson: Java Classes and Objects

Try next: Change only the display text and verify that the underlying rule and result stay unchanged.

Example 14: Test the closest boundary

A useful example includes the nearest boundary, not only the happy path. We are making the behavior inspectable before a real caller relies on it. We are applying that habit while revisiting Java Classes and Objects.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

public class Main {
    static int quantity(int value) {
        if (value < 1) throw new IllegalArgumentException("quantity must be positive");
        return value;
    }

    public static void main(String[] args) {
        System.out.println(quantity(1));
    }
}

Expected Result

Try next: Try the lowest supported value and then one value just outside the accepted range.

Example 15: Write a tiny regression check

A compact assertion turns the lesson into a repeatable promise. It helps us catch a changed rule before a larger program hides the source of the mistake. We are applying that habit while revisiting Java Classes and Objects.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Java

public class Main {
    public static void main(String[] args) {
        String result = "Java Classes and Objects".toUpperCase();
        if (!result.equals("JAVA CLASSES AND OBJECTS")) throw new AssertionError("contract failed");
        System.out.println("contract holds");
    }
}

Expected Result

contract holds

Try next: Deliberately change the expected value once, observe the failed check, and then restore the correct contract.

Common Mistakes

Avoid: treating class versus instance as a syntax trick while leaving the domain rule, ownership or error behavior implicit.
Avoid: treating create valid objects as a syntax trick while leaving the domain rule, ownership or error behavior implicit.
Avoid: treating use clear instance methods as a syntax trick while leaving the domain rule, ownership or error behavior implicit.
Avoid: treating avoid shared mutable defaults as a syntax trick while leaving the domain rule, ownership or error behavior implicit.

Interview Checklist

State the input domain and the boundary value before explaining the syntax.
Explain the failure or rejected-input outcome rather than assuming the happy path.
Identify mutation, ownership and any value that must not be changed by a caller.
Name a focused test that would prove the rule still holds after a future change.
Separate the local Java decision from printing, persistence, networking or framework code.