It’s a Great Idea

Sales Amount!

Now, I see the ability of the language. It works on all platforms, compiles and packages well, and can be served off the web. These are great things in it’s favor.

It provides the ability to build computer games and mobile information. It has a huge API and you can access numerous types of databases with it. It touts that you have to write less code than with C++.

This is a great start…

But, Something is Missing

Cloogy error messages!

My main problem with Java, as we’re learning it, is that there seems to be a better and easier way to do everything we’re doing in class, particularly if it’s meant to be accessed via the web.

We created a small program to calculate the commission on a sales amount. First, the user was prompted for the sales amount. Then, they were asked to enter the identification number of their role from a list given. This dictated what percent commission they received. Finally, it outputted a final number.

Go go gadget data errors!

I’m completely overwhelmed by questions…

Why is this not just on the web? Why are we not using lighter-weight technologies to accomplish this same thing? We could even throw in a little JavaScript to pull some real interactivity.

Why are we making them input the number on their own rather than selecting it from a drop down or radio button? Why are we not giving the information in the same window? Why are we making them bounce from window to window? This doesn’t even cover the errors that a person can enter.

The Learning Curve

Oh look, data errors.

The problem I’m having here is a problem I have frequently. When I think that I know a simpler, easier way to accomplish the same objective, I want to use that instead. I always want to use the best tool for the job, if I can.

I always want to run before I can walk. Learning to crawl is beyond painful for me.

At least in the next class, we’ll be making a game.