Burn lombok with fire. Code you can't read, and cant debug, is horrible to work with. I find the best was to make your code grokable, is to have junit tests fo

Burn lombok with fire. Code you can't read, and cant debug, is horrible to work with. I find the best was to make your code grokable, is to have junit tests for everything that run fast in the ide. When code needs maintenance, you can run it in the debugger quickly and see what it actually does, instead of what it was intended to do. The worst Java code is lombok code that gets fsked by aop and/or hibernate. I call these abominations Nojos (not plain old java objects) Again: burn lombok with fire. Wrong line numbers, ungreppable code, obsure bugs, different depending on the lombok version 70% maintenance cost compared against, two seconds to have your ide automatically make explicit the code you are going to run.