That Which We Call A POGO, By Any Other Name

Which would you rather write, the 100-line monstrosity from Java, or the 10-line (including the import statement) Groovy version? Sure, the IDE generated most of the Java code, but in Groovy all that code comes for free, and any code not present won’t develop bugs later. The Groovy attitude is that if the IDE can do it, why can’t the compiler? Even better, you can read this one, without swimming through all that generated code, and it works with the rest of your Java code simply by compiling it. So please consider using POGOs for all your mapped data.[6]
via That Which We Call A POGO, By Any Other Name.