By Janice J. Heiss on Sep 26, 2012
Among the most celebrated developers in recent years, especially in
the domain of Java EE and JavaFX, is consultant Adam Bien, who, in
addition to being a JavaOne Rock Star for Java EE sessions given in 2009
and 20011, is a Java Champion, the winner of Oracle Magazine’s 2011 Top Java Developer of the Year Award, and recently won a 2012 JAX Innovation Award as a top Java Ambassador.
Bien will be presenting the following sessions:
- TUT3907 - Java EE 6/7: The Lean Parts
- CON3906 - Stress-Testing Java EE 6 Applications Without Stress
- CON3908 - Building Serious JavaFX 2 Applications
- CON3896 - Interactive Onstage Java EE Overengineering
I spoke with Bien to get his take on Java today. He expressed
excitement that the smallest companies and startups are showing
increasing interest in Java EE. “This is a very good sign,” said Bien.
“Only a few years ago J2EE was mostly used by larger companies -- now it
becomes interesting even for one-person shows. Enterprise Java events
are also extremely popular. On the Java SE side, I'm really excited
about Project Nashorn.”
Bien expressed concern about a common misconception regarding Java's mediocre productivity. “The problem is not Java,” explained Bien, “but rather systems built with ancient patterns and approaches. Sometimes it really is ‘Cargo Cult Programming.’ Java SE/EE can be incredibly productive and lean without the unnecessary and hard-to-maintain bloat. The real problems are ‘Ivory Towers’ and not Java’s lack of productivity.”
Bien remarked that if there is one thing he wanted Java developers to understand it is that, "Premature optimization is the root of all evil. Or at least of some evil. Modern JVMs and application servers are hard to optimize upfront. It is far easier to write simple code and measure the results continuously. Identify the hotspots first, then optimize.”
He advised Java EE developers to, “Rethink everything you know about Enterprise Java. Before you implement anything, ask the question: ‘Why?’ If there is no clear answer -- just don't do it. Most well known best practices are outdated. Focus your efforts on the domain problem and not the technology.”
Looking ahead, Bien said, “I would like to see open source application servers running directly on a hypervisor. Packaging the whole runtime in a single file would significantly simplify the deployment and operations.”
Check out a recent Java Magazine interview with Bien about his Java EE 6 stress monitoring tool here.