Optional misuse: using get() without isPresent() check

Calling Optional.get() without checking isPresent() first throws NoSuchElementException when the value is absent. This is just as unsafe as the NullPointerException that Optional was designed to avoid, with worse error messages.

Use Optional's functional API to handle presence and absence declaratively:

Optional<User> user = userRepo.findById(id);

// BAD — unsafe
User u = user.get();

// GOOD options
// 1. orElseThrow with a meaningful exception
User u = user.orElseThrow(() -> new UserNotFoundException(id));

// 2. orElse with a default
User u = user.orElse(User.anonymous());

// 3. orElseGet for lazy default computation
User u = user.orElseGet(() -> createDefaultUser(id));

// 4. map/flatMap for transformation without unwrapping
Optional<String> email = user.map(User::getEmail);

// 5. ifPresent / ifPresentOrElse
user.ifPresentOrElse(
    u -> process(u),
    () -> log.warn("User {} not found", id)
);

Optional.get() was kept for compatibility but is considered an antipattern. The functional methods force explicit handling of the empty case at the call site, which is the entire point of Optional.