I hear you re: code bloat with too much boilerplate.
I stopped using get/set methods years ago in favor of public instance variables. Yeah, I understand the potential problems with kicking encapsulation to the street and into the gutter (I have written several Java books and I have done many projects in Java, so I am not a noob).
I have also started to favor using unchecked exceptions - that also makes code a lot shorter. This is also Controversial.
Its been a long day, I've been working non stop since 6 am this morning(I stay in India, Bangalore) and its 9 in the night now. I've been working on some Java code.
The AbstractSomethingFactoryFactoryFactoryClasses.java have taken a toll on me. I'm yet to rewind from the depth's of piles and piles of try/catch statements and Object.someMethod() methods buried deep in abyss of com.something.somethingElse.somethingInWonderland.whereTheHellAreWe folders.
But I will take your advice seriously though.
EDIT : After reading your bio and looking at your work on your site. I am your new fan :)
I stopped using get/set methods years ago in favor of public instance variables. Yeah, I understand the potential problems with kicking encapsulation to the street and into the gutter (I have written several Java books and I have done many projects in Java, so I am not a noob).
I have also started to favor using unchecked exceptions - that also makes code a lot shorter. This is also Controversial.