I just finished delivering a talk at Oredev 2013 on better concurrency in Java 8. With Lambda’s being the biggest new feature I naturally needed to address what they had to offer.
I mentioned the idea to use Wordle as an execution profiler while presenting the profiling section of my performance tuning course in Paris last December. The idea was seeded by presentation that Neal Ford did a few years ago in which he used Wordle to expose the vocabulary of a Java application. Instead of vocabulary, I wanted to see if Wordle could be used to visualize an applications dominate behavior.
I talk about java.lang.ref.* in my performance tuning course because these things (along with anything that implements finalize) are more expensive to create than normal objects and require at least two rounds of GC before you're completely rid of them. Of the bunch, that includes Reference, WeakReference, SoftReference and two other private reference classes that get mixed up with finalization, PhantomReference has to be the strangest.
In 1996, a group that I was working with devised a development process which we called Defect Driven Design, otherwise known as D3 (D-Cubed). We were a bit disappointed by not surprised that D3 never really caught on but just recently I saw a glimmer of hope for a revival.