Assembling a team of Java developers can be a challenging task.
Getting the right people together requires a combination of luck, skill, and plenty of patience.
When someone new joins your team, they could also be new to your company.
Over the years, we have conducted many job interviews of Java developer candidates wishing to join our team and company.
Our team of Java developers consists of people with various backgrounds and skill levels.
Everyone has a role and is assigned tasks based on that role.
Team members are expected to know basic programming concepts, core Java and core J2EE.
In addition; database access, web-browser, client/server concepts are required as well.
I am back with more stories about our adventures in the world of Java.
From the distant past to recent events. I hope to entertain, enlighten, and encourage.
So hold on to your hats.
For software developers in IT, there are times when you find yourself present at the birth of a major application.
10 years ago, we began our journey into the world of Java and "J2EE".
It was a big risk for my company, Amway Corp, to do this.
We had no in-house expertise and we had critical applications to migrate to the new technology.
From the beginning, we were determined to succeed.
Today, 10 years after; I can say our Java adventure has been very successful.
A few years ago, we met with our business analysts to discuss security for our application.
Our goal was to implement our own authentication mechanism for the web-based or user-interface
portion of the application.
We defined authentication security as "access rights to resources of the application".
After some initial discussion, one of our business analysts suggested we look for an
When my company, Amway Corp, makes a sale; somewhere, somehow a computerized transaction of that sale is created.
This transaction is sent to a number of applications at Amway for processing.
One such destination is our Java application.
We created a capability, called the Transaction Monitor (or TM) to deliver transactions to our app.
We began creating our second Java application five years after we began the first app.
We were hoping the second application would give us a chance to use additional Java technologies.
We began by gathering all of the known functional requirements and matched them to the various
Java-related technologies we knew of.
The result was a high-level technical architecture of the application.
During our 10 years of using Java at Amway Corp., some of our solutions
required us to think a little "outside of the box".
Our application had a reporting requirement.
It had to generate reports from the application's various batch processes as they were running.
These batch processes performed transaction processing, data purging and data exporting functions.
It never ceases to amaze me where some solutions in application development come from.
We had a requirement for our application to allow a user to print pages of text.
The user would bring up a web page, from our app, and then create & print a list of customer names.
The list of names would be created by executing a SQL query against the database, using a variety of search criteria.
As we began our Java adventure at Amway Corp 10 years ago,
one of the most important tasks we had to do was to create our Object Model.
We had a variety of Java objects that we were planning to use in our application.
How were they going to be "wired" together inside of the application?
After 4 weeks of Object-Oriented, J2SE, J2EE training; we set out to define our Object Model.