I was in an all-hands call, which as usual apparently for any company, was largely a waste of time and money. Anyways, as a prelude to hearing about some wonderful tooling/toolkits we should all standardize on, we see this chart:
The “chart” bothers me on so many levels. First I’m not sure why gartner feels that the average skill level of J2EE developers peaked in 2002. Why 2002? Is that when the smart, early adopters of J2EE started fleeing for the greener pastures of python, php and ruby? Or was the field swamped by “Sun Certified” J2EE folks who can memorize APIs but not actually solve problems? Secondly, by what measure are J2EE applications getting more complicated? Did the world get dramatically more complicated since 2002? If your architecture or platform (J2EE) is so complicated that you need to slather on more layers of “architecture” to fix it, isn’t there something fundamentally wrong in the first place? Complexity is not a virtue.
Lastly, as a developer thinking about skills that are applicable to another job down the pike, why would I want to learn an proprietary wizard-hand-held way of doing things when there are so many great open source solutions to the same problems that would be applicable at many more jobs down the road?