Senior Java Developer Argues Lombok Saves Lines but Creates Hidden Long-Term Bugs

A developer with eleven years of enterprise Java experience contends that while Project Lombok reduces boilerplate code dramatically, it introduces hard-to-debug problems in real codebases. Annotations like @Data can cause serious issues with JPA entities, where auto-generated equals(), hashCode(), and toString() methods conflict with Hibernate's identity and lazy-loading mechanisms. A seemingly harmless log statement using a Lombok-generated toString() can trigger unintended database queries or even crash a logging pipeline through bidirectional association recursion. Attempts to fix these issues by layering additional Lombok annotations, such as @ToString(exclude) and @EqualsAndHashCode, ultimately defer complexity rather than eliminate it. The author's core argument is that hand-written methods remain visible, searchable, and fully owned in source code, whereas generated behavior is hidden and requires extra tooling knowledge from every future developer on the project.