Javaero.Org

Edison’s Cup of Java (4/8/2007) - series 3 of 999

Ah, so you came back for more! Then I must say your passion to learn or perhaps curiosity motivated you to come spend some time with me for this “jump over the river” Java cup session. Having said that iterates my fair early warning that this topic will not be as specious as it looks. This article will be the deciding factor whether you will be more motivated to continue on in attaining a Java skill level-up or you go back to your “wish I can Java” day dream.Just to set things straight, I will stand pat with my principle to remain creative and thus up to a certain degree maintain my originality. For after all, since my chosen IP copyright is creative commons, my goal is to share to you my approach or my very own signature strategy in learning Java. Therefore, I will not rewrite or worse plagiarize what has been written by somebody else—the bane of many other bogus technical writers. Instead, if I see it fit, I will refer you to pages that will benefit both you and me.

Having that cleared out of my throat, let’s move on into achieving our goal. Continue Reading »

Comments Off

Edison’s Cup of Java (3/7/07) - series 2 of 999

Simple does it, but it gets no simpler—do brace for more sophistication though—I must forewarn. Be careful of what you wish for, you might just get it, so the saying goes.

With our freshly brewed (installed) Java, let us begin this session by testing it. Go to your command line or classic console. In MS Windows, this will be your Start/run, type cmd then press enter. For Linux users, I will assume you know better and are sharper when it comes to OS skills, so I will not compound this article by covering that field for now.

Continue Reading »

Comments Off

Edison’s Cup of Java (2/22/2007) - series 1 of 999 

System.out.println(”Hi, World”);

What on Earth, err, rather, digital world am I doing in this space? Perhaps it is the Dilbert principle, or maybe it is because I lack attention, or is it because I needed an outlet to channel some excess energy or even angst, the bottom-line is, it is more so because writing something technical but practical like my favorite MP3 have always been playing in my mind.

Continue Reading »

Comments Off

The second installment in our series on Design Patterns is the most popular ofall patterns, the MVC. MVC stands for Model-View-Controller. That means your application is separated into these three components. Let us discuss these components one by one.

• Model – a model is a representation of your business logic and/or data. For example, if you have an online shopping application, your shopping cart, items, and the codes that update your cart are the models.

• Controller – takes user input and decides what to do with the model.

• View – the one responsible for the presentation of the state of the model.

One good analogy for the MVC is a car. The model is the car engine. The brakes, steering wheel and other controls represent the controller. The tachometerand the thermometer are the views.

Continue Reading »

Comments Off

A software application’s main goal is to provide the user with a reliable, useful, and correct experience. However, as software grows overtime, so does complexity, and this leads to a variety of problems that could affect the reliability and performance of the application. The growth in complexity does not only refer to the lines of code but also includes the hardware. Design patterns address these software and hardware issues. Design pattern, by definition, is a repeatable solution for a commonly-occurring software problem, and they all came from developers and architects who have years of experience dealing with these software problems. But before we dive-in to the common design patterns being used today, let us discuss first the software requirements that these design patterns addresses. These are called the software “ilities”.

1. Performance – this is very important. In a website for example, if your website is slow, you’re going to lose your customers.
2. Modularity – your application should be composed of several parts (called modules) in order for different pieces of your application to run on different boxes at the same time.
3. Flexibility – your system should have the ability to adapt in a timely and cost-effective manner whenever there is an external/internal change. That means if there are some changes to be done, your system can be changed without going through some big development cycle.
4. Maintainability - you might need to change database vendors, and update your system quickly. You might get obscure bugs and need to track them down ASAP. Your system needs to be maintainable.
5. Extensibility - the guys over in marketing might need a new feature to land that big client. Your users might demand that you support a brand new feature that their browsers have. Your system had better be extensible.

The items discussed above are called the “non-functional” requirements of software. These requirements will be easily met using design patterns. Continue Reading »

Comments Off