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?

A career in the field of software development remains immensely popular due to various factors. Chief among them of course is the higher compensation and lucrative pay scale in the IT industry when compared to other career options. In addition, the flexibility of work hours and the sheer sense of achievement experienced by one while creating new programs are unsurpassed by any other job.

Popularity and reach of Software Programs

Software programming has become a quintessential part of our day to day life, right from the smartphones in your pocket, to video gaming, and everything in between. The opportunities in this field are truly astounding. The niches for specializing are also diverse, from creating operating systems, to mobile app development, or web app development to name a few.

There are various ways in which you can distinguish yourself in the market for the much coveted title of software programmer. Here, we focus on some of them.

No matter what type of business you’re in, boosting your bottom line is always in the back of your mind. In a rough economy, it can be tempting to focus too much on pulling in more money and not enough on containing it from within.

That’s right, containing it. You have the potential to lose hundreds of thousands of dollars every year right under your nose from something as simple as lack of or ineffective computer training.

How much do the employees you have working for you right now really understand about technology? How good is your IT tech department? Technology changes faster than a blink of an eye and oftentimes, businesses struggle to keep their top employees trained.

With millions of dollars being lost to Internet espionage, file corruption and other computer crimes, staying on top of changes is essential. Recently, online learning centers have been emerging as the go-to method for quick and inexpensive learning. Unfortunately, this type of computer learning isn’t always the best solution.

Memory management is always a priority in pretty much any programming language you would want to use. In the lower level languages such as C, there are a number of functions which help you manage the memory your application uses, but they are not the easiest to use. Some of the more modern programming languages such as Python, Ruby, Perl, and of course the subject of this article, Javascript all have a built in feature called garbage collection.

Garbage collection essentially means that the languages compiler will automatically free the memory being occupied by unused variables and objects, but there is no telling when this could occur. It is purely down to the compiler to decide when the garbage collection process should be initiated.