Python and Ruby, each with roots going back into the 1990s, are two of the most popular interpreted programming languages today. Ruby is most widely known as the language in which the ubiquitous Ruby on Rails web application framework is written, but it also has legions of fans that use it for things that have nothing to do with the web. Python is a big hit in the numerical and scientific computing communities at the present time, rapidly displacing such longtime stalwarts as R when it comes to these applications. It too, however, is also put to a myriad of other uses, and the two languages probably vie for the title when it comes to how flexible their users find them.

A Matter of Personality...

That isn't to say that there aren't some major, immediately noticeable, differences between the two programming tongues. Ruby is famous for its flexibility and eagerness to please; it is seen by many as a cleaned-up continuation of Perl's "Do What I Mean" philosophy, whereby the interpreter does its best to figure out the meaning of evening non-canonical syntactic constructs. In fact, the language's creator, Yukihiro Matsumoto, chose his brainchild's name in homage to that earlier language's gemstone-inspired moniker.

Python, on the other hand, takes a very different tact. In a famous Python Enhancement Proposal called "The Zen of Python," longtime Pythonista Tim Peters declared it to be preferable that there should only be a single obvious way to do anything. Python enthusiasts and programmers, then, generally prize unanimity of style over syntactic flexibility compared to those who choose Ruby, and this shows in the code they create. Even Python's whitespace-sensitive parsing has a feel of lending clarity through syntactical enforcement that is very much at odds with the much fuzzier style of typical Ruby code.

For example, Python's much-admired list comprehension feature serves as the most obvious way to build up certain kinds of lists according to initial conditions:

a = [x**3 for x in range(10,20)]
b = [y for y in a if y % 2 == 0]

first builds up a list of the cubes of all of the numbers between 10 and 19 (yes, 19), assigning the result to 'a'. A second list of those elements in 'a' which are even is then stored in 'b'. One natural way to do this in Ruby is probably:

a = (10..19).map {|x| x ** 3}
b = a.select {|y| y.even?}

but there are a number of obvious alternatives, such as:

a = (10..19).collect do |x|
x ** 3
end

b = a.find_all do |y|
y % 2 == 0
end

It tends to be a little easier to come up with equally viable, but syntactically distinct, solutions in Ruby compared to Python, even for relatively simple tasks like the above. That is not to say that Ruby is a messy language, either; it is merely that it is somewhat freer and more forgiving than Python is, and many consider Python's relative purity in this regard a real advantage when it comes to writing clear, easily understandable code.

And Somewhat One of Performance

I will begin our blog on Java Tutorial with an incredibly important aspect of java development:  memory management.  The importance of this topic should not be minimized as an application's performance and footprint size are at stake.

From the outset, the Java Virtual Machine (JVM) manages memory via a mechanism known as Garbage Collection (GC).  The Garbage collector

• Manages the heap memory.   All obects are stored on the heap; therefore, all objects are managed.  The keyword, new, allocates the requisite memory to instantiate an object and places the newly allocated memory on the heap.  This object is marked as live until it is no longer being reference.
• Deallocates or reclaims those objects that are no longer being referened. 
• Traditionally, employs a Mark and Sweep algorithm.  In the mark phase, the collector identifies which objects are still alive.  The sweep phase identifies objects that are no longer alive.
• Deallocates the memory of objects that are not marked as live.
• Is automatically run by the JVM and not explicitely called by the Java developer.  Unlike languages such as C++, the Java developer has no explict control over memory management.
• Does not manage the stack.  Local primitive types and local object references are not managed by the GC.

So if the Java developer has no control over memory management, why even worry about the GC?  It turns out that memory management is an integral part of an application's performance, all things being equal.  The more memory that is required for the application to run, the greater the likelihood that computational efficiency suffers. To that end, the developer has to take into account the amount of memory being allocated when writing code.  This translates into the amount of heap memory being consumed.

Memory is split into two types:  stack and heap.  Stack memory is memory set aside for a thread of execution e.g. a function.  When a function is called, a block of memory is reserved for those variables local to the function, provided that they are either a type of Java primitive or an object reference.  Upon runtime completion of the function call, the reserved memory block is now available for the next thread of execution.  Heap memory, on the otherhand, is dynamically allocated.  That is, there is no set pattern for allocating or deallocating this memory.  Therefore, keeping track or managing this type of memory is a complicated process. In Java, such memory is allocated when instantiating an object:

String s = new String();  // new operator being employed
String m = "A String";    /* object instantiated by the JVM and then being set to a value.  The JVM
calls the new operator */

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

One of the biggest challenges faced by senior IT professionals in organizations is the choice of the right software vendor. In the highly competitive enterprise software industry, there are lot of vendors who claim to offer the best software for the problem and it can be really daunting to narrow down the best choice. Additionally, enterprise software costs can often run into millions of dollars thereby leaving very little margin of error. The real cost of choosing a wrong software can often result into losses much more than the cost of the software itself as highlighted by software disasters experienced by leading companies like HP, Nike etc. In such a scenario, senior IT professionals despite years of expertise can find it very difficult to choose the right business software vendor for their organization.

Here are some of the proven ways of short-listing and selecting the right business software vendor for your organization,

·         Understand and Define The Exact Need First: Before embarking on a journey to select the software vendor, it is critical to understand and define the exact problem you want the software to solve. The paramount question to be asked is what business objective does the software need to solve. Is the software required to “reduce costs” or is it to “improve productivity”? Extracting and defining this fundamental question is the bare minimum but necessary step to go searching for the right vendor. It will then form the basis of comparing multiple vendors on this very need that your organization has and will help drive the selection process going forward. The detailed approach involves creating a set of parameters that the software needs to meet in order to be considered. In fact, consider categorizing these parameters further in “must-haves”, “good to have” etc. which will help you assign relevant weights to these parameter and how the software’s fare on each of these parameters

·         Building The List of Vendors Who Meet The Need: Once you have defined your need and distilled that need into various parameters, it’s time to built the list of vendors who you think will meet the need. This is akin to a lead generation model wherein you want to identify a large enough pool and then filters your list down to the best ones. There are multiple ways of building a list of vendors and more often than not, you must use a combination of these methods to build a good enough list.

o   Use Industry Reports: We discussed the IT intelligence offered by leading industry firms Gartner and Forrester in How To Keep On Top Of Latest Trends In Information Technology. These firms based on their access to leading software vendors and CIO network publish vendor comparison research reports across specific verticals as well as specific technologies. Gartner’s Magic Quadrant and Forrester’s Wave are a very good starting point to get an insight into the best software vendors. For example, if you were looking for a CRM solution, you could look for Gartner’s Magic Quadrant for CRM and look at the vendors that make the list. These reports can be pricey but well worth the money if you are going to invest hundreds of thousands in the software. Having said that, you don’t have to trust these report blindly because how these firms define the best software may not match how you define the best software for your organization

o   Competitive Intelligence: If you are a smart professional, you are already keeping tabs of your competition. Chances are that if you are a big organization, you might see a Press Release either from your competitor or their vendor announcing the implementation of new software. Extrapolate that across 5-10 key competitors of yours and you might discover the vendors that your competitors are choosing. This gives you a good indicator that the vendors used by your competitors must be offering something right.