 |
|
|
|
|
|
The Java Community Process (JCP) program runs smoothly thanks to the dedication of the
Program Management Office (PMO) staff. These individuals bring not only a wealth of diverse
technical, academic, and personal training and experience to the task of nurturing the community,
but they also share a passionate enthusiasm for Java technology and the community that is evolving
it.
|
|
Joe Strzemp (silent z!?) is the web engineer for the JCP Program
Management Office (PMO). Simply said, Joe writes, "Working through
various development technologies "du jour" over the years, Java has
become my absolute favorite for many of the often touted reasons for
others choosing Java as their first or favorite choice, but also
because it just plain works. The rich programming environment offered
by Java is just phenomenal. Though I do occasionally quietly promote
Java privately, I'm less about fanatical platform promote-ism and more
about getting *real* industrial strength, scalable, and secure work
done, and Java allows me to do that, so I'll just leave it at that."
In a small group like the JCP PMO, people take on several functional
roles and wear many hats. Besides creating new features for the
jcp.org web site, he also does servicing of the web server, database
support, back-end tools and ancillary services, and working on some of
the more complicated web content for jcp.org, along with general
support for the JCP PMO, and end-user support.
 |
|
| Joe Strzemp |
 |
Prior to his joining the JCP Program Management Office, Joe worked in
Rob Gingell's Architecture and Technology group at Sun Microsystems.
His last project while there was to help in delivering the Solaris
source code into the hands of the user community as part of what
eventually became OpenSolaris. The JCP program lived under Rob's
group, and Joe made the transition to a position within the JCP
utilizing his UNIX and web development skills.
Originally from Chicago, Illinois, Joe received his bachelor's degree
from the University of Illinois in Computer Science and Electrical
Engineering. While there, he led a study of how engineers debug code
and the radically different approaches they take to debugging. A
particularly interesting result of the study was how differently people
process conflicting, confusing, and incomplete information. Although
the participants had very similar academic experience, the study
illustrated the radically different techniques used by individuals and
the widely varying abilities of engineers in problem solving.
Joe's personal experience with Java are behind his saying, "I like many
things about Java technology. As a developer, I find that I don't run
into many programming problems in Java technology. Instead, you're
left with logic and design problems, which are, well, far more
interesting. For me, Java raises the level at which I view programming
issues, the proverbial programming silver bullet. Java technology
provides the protection against typical programming errors so that
those types of issues rarely come into play."
Joe also likes the way Java technology makes "gigantic and massive"
projects such as the portal projects (JSRs 162, 167, 168) approachable,
"Because they stand on the foundation of prior projects and therefore
have a chance of being largely successful." Joe recalls a recent
article that stated that about 95% of all software projects exceed time
and cost estimates, and he feels that Java technology allows companies
to improve on hitting their targets.
Joe's professional interests include programming algorithms,
(in particular concurrency and synchronization issues (JSR 166:
Concurrency Utilities) and text and pattern matching methods), neural
networking, security, visualization, and debugging tools and
techniques.
Besides spending time with his son and his daughter, his personal
interests include playing tennis, hiking, movies, music, and guitar.
He resides in the Bay Area in California.
Last updated: Oct 2009
 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
|
