Java Best Practices

Usually, yes — returning `Optional<T>` is better than returning `null` when “no result” is a normal, expected outcome.

Why:
- `Optional` makes the absence explicit in the method signature.
- It reduces accidental `NullPointerException`s.
- It forces callers to handle the empty case intentionally.

Example:

```java
public Optional<User> findUserById(String id) {
    return repository.lookup(id);
}
```

Then the caller can do:

```java
findUserById(id).ifPresent(this::sendEmail);
```

or

```java
User user = findUserById(id).orElseThrow(() -> new UserNotFoundException(id));
```

A few caveats:
- Don’t use `Optional` for fields or most method parameters.
- For collections, return an empty collection instead of `Optional<List<T>>` in most cases.
- If the method is internal and performance-critical, `null` may still be acceptable, but it should be a deliberate choice.

So the general Java best practice is: don’t return `null` for “not found”; prefer `Optional<T>` or an empty collection, depending on the return type.