Is it possible for anyone to give Microsoft a fair trial? The first half of 2012 is in the history books. Yet the firm still cannot seem to shake the public opinion as The Evil Empire that produces crap code.

I am in a unique position. I joined the orbit of Microsoft in 1973 after the Army decided it didn't need photographers flying around in helicopters in Vietnam anymore. I was sent to Fort Lewis and assigned to 9th Finance because I had a smattering of knowledge about computers. And the Army was going to a computerized payroll system.

Bill and Paul used the University of Washington's VAX PDP computer to create BASIC for the Altair computer. Certainly laughable by today's standards, it is the very roots of the home computer.

Microsoft became successful because it delivered what people wanted.

Today we live in the age of technology. It seems like everyone owns at least one computer, but few actually know how they work. We hear about Java tutorials and C# programming, but why are these things important?

There has been an increasing demand for those who are proficient in web development. It is a job field that has grown substantially in the past decade, and it is still continuing to flourish with no signs of stopping. Learning a web language is not only a useful skill, but a necessary one. So why, out of all of the available web languages, is Java the most valuable?

·         First off, it is a simple language that is easily learned and well known.

·         Java has been around for awhile now, and has earned its place as one of the pillars of modern day computer architecture. Information on Java is abundant, and ranges from online tutorials to books, such as "Java for Dummies."

Before we go to the list do you know what makes software skills most sought-after and hence more valuable than most of the other job skills? It is simply because unlike any other skill, software skills are global and are not at all location specific! With the evolution and penetration of internet technologies, the physical distance between the client and service provider hardly matters. So, with more advancement in technology, it is indeed going to rain opportunities on the right skilled developer. I’ll take the liberty to reproduce the following quotes here to prove my claims statistically:

Demand for “cloud-ready” IT workers will grow by 26 percent annually through 2015, with as many as 7 million cloud-related jobs available worldwide.

---IDC White Paper (November 2012).

In the United States, the IT sector is experiencing modest growth of IT jobs in general, with the average growth in IT employment between 1.1 and 2.7 percent per year through 2020.

---U.S. Bureau of Labor Statistics.

I suspect that many of you are familiar with the term "hard coding a value" whereby the age of an individual or their location is written into the condition (or action) of a business rule (in this case) as shown below:

if customer.age > 21 and customer.city == 'denver'

then ...

Such coding practices are perfectly expectable provided that the conditional values, age and city, never change. They become entirely unacceptable if a need for different values could be anticipated. A classic example of where this practice occurred that caused considerable heartache in the IT industry was the Y2K issue where dates were updated using only the last 2 digits of a four digit number because the first 2 digits were hard-coded to 19 i.e. 1998, 1999. All was well provided that the date did not advance to a time beyond the 1900’s since no one could be certain of what would happen when the millennia arrived (2000). A considerably amount of work (albeit boring) and money, approximately $200 billion, went into revising systems by way of software rewrites and computer chip replacements in order to thwart any detrimental outcomes. It is obvious how a simple change or an assumption can have sweeping consequences.

You may wonder what Y2K has to do with Business Rule Management Systems (BRMS). Well, what if we considered rules themselves to be hard-coded. If we were to write 100s of rules in Java, .NET or whatever language that only worked for a given scenario or assumption, would that not constitute hard-coded logic? By hard-coded, we obviously mean compiled. For example, if a credit card company has a variety of bonus campaigns, each with their own unique list of rules that may change within a week’s time, what would be the most effective way of writing software to deal with these responsibilities?