With the rapid evolution that Java and open source frameworks have
made since the release of J2EE, enterprise Java IT seems to be
producing too many Java dinosaurs. Developers, technical managers, or
architects who no longer pursue their technical skills don't understand
the evolution of JEE in comparison to J2EE, persistence frameworks, IOC
frameworks, Web frameworks, or Web 2.0 and its effects on enterprise
Java. Yet decisions are made based on out-of-date J2EE experience.
To understand this better, we need to understand relevance.
Wikipedia defines relevance (the philosophical concept of relevance) as
"a term used to describe how pertinent, connected, or applicable some
information is to a given matter." We need to ask ourselves the
following questions:
- Are we relevant?
- Do we need to be relevant?
- What are the implications of not being relevant?
- How do we stay relevant?
Por
Jay Blanton