There's no need to write getters and setters

I don’t write getters and setters! There simpily is no need for them and they only pollute the code.

It has been discussed before with good arguments, however, I can make a few more, apart from the fact that they cut holes in the architecture, break encapsulation and leads to business logic residing outside the class to which it really belongs.

• First of all, if you are making immutable objects, (and you should), then there is obviously no need at all for any set-methods.

• Second, if you are in a functional paradigm then every method will by design return something so it becomes redundant to prefix methods with “get”. Account.balance() will obviously get the balance so there’s no need to name the method getBalance().

One can argue that balance() is in fact a getter method and that might be true, however, additional work can be done in that method apart from only returning a stored value:

Member fields stored as null internally can be converted to Optional.

@Nullable private final String myValue;
Optional<String> myValue() {
  return Optional.ofNullable(myValue)
}

Defensive copying (in the case of internal members that are mutable)

private final Date birthDate;
Date birthDate(){
  return new Date(birthDate);
}

The returned value might be calculated from other internal values

class Account {
  private final double balance;
  private final double interest;
  double revenue(){
    return balance * interest;
  }
}

All in all, it helps keeping the code clean and easy to read, while also reminding you to make you classes immutable!