Last year, Hewlett-Packard purchased Autonomy for $10 billion, enduring a number of arrows from its competitor Oracle. What a difference a year is!

Since the purchase HP saw the leaving of Autonomy CEO Mike Lynch, which was not on friendly terms. It also saw the departure of the whole original management team and 20 percent of the staff. Now, the question is whether or not HP will see its move compensate or become another WebOS-style fiasco, marking the company needs to stay with hardware.

A business rule is the basic unit of rule processing in a Business Rule Management System (BRMS) and, as such, requires a fundamental understanding. Rules consist of a set of actions and a set of conditions whereby actions are the consequences of each condition statement being satisfied or true. With rare exception, conditions test the property values of objects taken from an object model which itself is gleaned from a Data Dictionary and UML diagrams. See my article on Data Dictionaries for a better understanding on this subject matter.

A simple rule takes the form:

if condition(s)

then actions.

An alternative form includes an else statement where alternate actions are executed in the event that the conditions in the if statement are not satisfied:

if condition(s)

then actions

else alternate_actions

It is not considered a best prectice to write rules via nested if-then-else statements as they tend to be difficult to understand, hard to maintain and even harder to extend as the depth of these statements increases; in other words, adding if statements within a then clause makes it especially hard to determine which if statement was executed when looking at a bucket of rules. Moreoever, how can we determine whether the if or the else statement was satisfied without having to read the rule itself. Rules such as these are often organized into simple rule statements and provided with a name so that when reviewing rule execution logs one can determine which rule fired and not worry about whether the if or else statement was satisfied. Another limitation of this type of rule processing is that it does not take full advantage of rule inferencing and may have a negative performance impact on the Rete engine execution. Take a class with HSG and find out why.

Rule Conditions

Recently, I asked my friend, Ray, to list those he believes are the top 10 most forward thinkers in the IT industry.  Below is the list he generated. 

Like most smart people, Ray gets his information from institutions such as the New York Times, the Wall Street Journal, the Huffington Post, Ted Talks ...  Ray is not an IT expert; he is, however, a marketer: the type that has an opinion on everything and is all too willing to share it.  Unfortunately, many of his opinions are based upon the writings/editorials of those attempting to appeal to the reading level of an 8th grader.  I suppose it could be worse.  He could be referencing Yahoo News, where important stories get priority placement such as when the voluptuous Kate Upton holds a computer close to her breasts.

Before you read further, note that missing from this list and not credited are innovators: Bill Joy, Dennis Ritchie, Linus Torvalds, Alan Turing, Edward Howard Armstrong, Peter Andreas Grunberg and Albert Fent, Gottfried Wilhelm Leibniz/Hermann Grassmann ... You know the type:  the type of individual who burns the midnight oil and rarely, if ever, guffaws over their discoveries or achievements.

Although the index is an important itemized guide of what people are searching for on the internet, it’s arguable that certain languages getting recognition is a direct result of early adopters posting tutorials and filling up discussion boards on current trends. Additionally, popular tech blogs pick up on technological shifts and broadcast related versions of the same themes.

When does the popularity of a software language matter?

1. If you want marketable skills, knowing what employers are looking for is beneficial. As an example, languages such as Java and Objective C are highly coveted in the smart-phone apps businesses.
2. A consistently shrinking language in usage is an indicator not only that employers are apt to pass on those skills but fall in danger of being obsolete.
3. Focusing on languages that are compatible with other developers increases your chances to participate on projects that companies are working on.