Private Fields with Getters and Setters in Java

Direct Answer

Making fields private enforces encapsulation — it stops external code from modifying state in unexpected ways. Getters give controlled read access; setters validate data before accepting a change. This protects data integrity and lets the internal implementation change without breaking callers.

Code Example

A realistic accessor does two jobs at once — it guards the value and it cleans it up. This Account rejects blank usernames and malformed emails, and it also normalizes whatever it keeps.

public class Account {
    private String username;
    private String email;

    public String getUsername() { return username; }

    public void setUsername(String username) {
        if (username == null || username.isBlank())
            throw new IllegalArgumentException("Username required");
        this.username = username.trim();      // normalize
    }

    public void setEmail(String email) {
        if (!email.contains("@"))
            throw new IllegalArgumentException("Invalid email");
        this.email = email.toLowerCase();     // normalize
    }
}

Because callers can never write the field directly, every value that lands in username or email is already trimmed and lower-cased. That guarantee is only possible when the field is private and the setter is the single doorway in.

Common Mistakes & Pitfalls

• Auto-generating a getter and setter for every field — fields meant to be set once at construction end up with a setter they never needed, throwing away immutability for no reason.
• Writing setters with no validation — this.age = age; with no checks is barely better than a public field; the validation is the entire reason the setter exists.
• Returning the live reference from a getter — return this.items; hands callers your internal List, and they can mutate it behind your back; return a copy or an unmodifiable view instead.
• Confusing private with secure — private is a compile-time visibility rule, not security; reflection can still reach the field, so this is about clean design and data integrity, not hiding secrets.