Recently, I was asked to participate in creating another Java application at my company.
It was to be our team's third major Java application since 2002.
We felt we had plenty of wisdom from our previous two Java applications to apply to our third one.
One of our first steps was to form an application architecture sub-team.
My company uses a large number of software applications to support all aspects of its business.
These software applications are either "bought" or "built".
The portions of the company that cannot be supported by purchased software are
supported by custom developed, in-house, applications.
A variety of technologies are used to create and build these custom applications.
A while ago, I was asked to evaluate another Java application that was being used at my company.
It was a point-of-sale app, developed entirely "in-house" by one of our overseas affiliates.
I wondered what their MVC model would look like.
How different would their Java app be from the ones I have worked on?
Very soon, it will be time for the annual Java One conference in San Francisco, California.
Thousands of Java-fanatics will make the journey to my favorite city "by the bay" (and my home town).
Thousands more Java-fanatics will not attend (including me) and wish they could.
I hope all attendees will have a great and productive time at Java One 2013.
As a developer, when you are building and/or designing a Java application;
the first (or one of the first) question you might ask is...
"What are the objects?"
This seems to be a very simple question. But it is not.
There probably is no single "right" answer to this question.
Nevertheless, careful consideration given to this question will contribute to
When we started building our first Java application, at my company Amway Corp, many years ago;
we learned our first lesson.
In spite of all the formal training we received, in spite of all the literature at our disposal;
we still needed help with our Java development on a regular basis.
Where would this assistance come from?
At the time, we had no in-house Java subject-matter experts.
Learning Java (or any programming language) can be a great challenge.
Any group of developers, learning Java, will bring with them a variety of backgrounds and experiences.
In our case, our first Java project began with developers that had COBOL language experience.
Our second Java project, began with developers that had RPG language experience.
Tuning Java code presents many challenges and addresses several goals.
One of these goals is to make the application "run faster".
Recently, our end-users were getting multiple-second response times from our web application's home page.
This was unacceptable.
We were asked to see what we can do to make the web application "run faster".
One of the first things we did as we began to learn about Java was to create our own library of Java books.
Every member of the development team was given the chance (and funding) to build their own collection of books.
In time, these book collections became a sort of "comfort blanket" for the developers.
In addition to being a valuable source of reference material,
One of the biggest challenges facing us during the creation of our first Java application
was learning to develop with the Java programming language.
We were concerned about how well our team of developers would learn and adapt to Java.
Since Java was an object-oriented programming language, we had object-oriented concepts to learn as well.