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?

Due to the advancements in technology, teens and adults alike can now partake in virtual worlds thanks to video games. Video games are enjoyed as a hobby all over the globe, but some gamers have made it their career with help from the ever-growing e-sport community. This is an inside look at the professional level of gaming from an ex-MLG participant, and what I remember going through when starting to play video games at an elite level.

One of the premiere and most popular leagues within the United States happens to be Major League Gaming or MLG for short. This is a league that usually involves more of the most recent games out, and they create circuits for each major title and its subsequent releases. Two of the most major game circuits within the MLG league were the Halo series and the Call of Duty series, both which happened to be first person shooters (FPS). There were a potential hundred or so teams within each circuit, but much like other competitions, the circuits were ran with winner’s brackets and losers brackets. This means that out of all the teams that would show up to MLG events, about the top eight of each bracket would really be known as the "elite" players. I personally played in the Gears of War circuit at venues like MLG Raleigh and MLG Toronto, and we had very few teams compared to Call of Duty and Halo. The amount of participants at each event usually varies in each circuit based on the popularity of the game being played.

When you win tournaments, the payouts are split between the team members. This means that looking at playing in the MLG for a life career is an ill-advised move. The cost to get to events and buy team passes usually negates the prizes you win most of the time, considering by the time that the prize money is split you are left with about $800 in a popular circuit (Like Call of Duty). The payouts are usually only high in special and certain occasions, one for example being the million dollar showdown that Infinity Ward hosted for Call of Duty: Modern Warfare 3 a couple years back. The way that players that make professional gaming their career get the big money now is by being sponsored by the big companies that back the league like Red Bull and Hot Pockets. MLG players like "Walshy" and "FeaR Moho" were sponsored early on in the league and were able to make a living off of the games they played. I would imagine them getting around $60K in a good year off of sponsors alone. I would go even as far as to say that if you do not have a sponsor in e-sports, you will not be financially successful in the career.

Being an MLG gamer requires passion and understanding for the games. If you just want to make money, then you are better off working at McDonalds.

How to Keep a Start Up Team Motivated?

What People Should Know Before Getting Rid of Old Tech Stuff

Surprising Ways Viruses, Malware, Etc. are Infecting Computers

Over time, companies are migrating from COBOL to the latest standard of C# solutions due to reasons such as cumbersome deployment processes, scarcity of trained developers, platform dependencies, increasing maintenance fees. Whether a company wants to migrate to reporting applications, operational infrastructure, or management support systems, shifting from COBOL to C# solutions can be time-consuming and highly risky, expensive, and complicated. However, the following four techniques can help companies reduce the complexity and risk around their modernization efforts. 

All COBOL to C# Solutions are Equal 

It can be daunting for a company to sift through a set of sophisticated services and tools on the market to boost their modernization efforts. Manual modernization solutions often turn into an endless nightmare while the automated ones are saturated with solutions that generate codes that are impossible to maintain and extend once the migration is over. However, your IT department can still work with tools and services and create code that is easier to manage if it wants to capitalize on technologies such as DevOps. 

Narrow the Focus 

Most legacy systems are incompatible with newer systems. For years now, companies have passed legacy systems to one another without considering functional relationships and proper documentation features. However, a detailed analysis of databases and legacy systems can be useful in decision-making and risk mitigation in any modernization effort. It is fairly common for companies to uncover a lot of unused and dead code when they analyze their legacy inventory carefully. Those discoveries, however can help reduce the cost involved in project implementation and the scope of COBOL to C# modernization. Research has revealed that legacy inventory analysis can result in a 40% reduction of modernization risk. Besides making the modernization effort less complex, trimming unused and dead codes and cost reduction, companies can gain a lot more from analyzing these systems. 

Understand Thyself 

For most companies, the legacy system entails an entanglement of intertwined code developed by former employees who long ago left the organization. The developers could apply any standards and left behind little documentation, and this made it extremely risky for a company to migrate from a COBOL to C# solution. In 2013, CIOs teamed up with other IT stakeholders in the insurance industry in the U.S to conduct a study that found that only 18% of COBOL to C# modernization projects complete within the scheduled period. Further research revealed that poor legacy application understanding was the primary reason projects could not end as expected. 

Furthermore, using the accuracy of the legacy system for planning and poor understanding of the breadth of the influence of the company rules and policies within the legacy system are some of the risks associated with migrating from COBOL to C# solutions. The way an organization understands the source environment could also impact the ability to plan and implement a modernization project successfully. However, accurate, in-depth knowledge about the source environment can help reduce the chances of cost overrun since workers understand the internal operations in the migration project. That way, companies can understand how time and scope impact the efforts required to implement a plan successfully. 

Use of Sequential Files 

Companies often use sequential files as an intermediary when migrating from COBOL to C# solution to save data. Alternatively, sequential files can be used for report generation or communication with other programs. However, software mining doesn’t migrate these files to SQL tables; instead, it maintains them on file systems. Companies can use data generated on the COBOL system to continue to communicate with the rest of the system at no risk. Sequential files also facilitate a secure migration path to advanced standards such as MS Excel. 

Modern systems offer companies a range of portfolio analysis that allows for narrowing down their scope of legacy application migration. Organizations may also capitalize on it to shed light on migration rules hidden in the ancient legacy environment. COBOL to C# modernization solution uses an extensible and fully maintainable code base to develop functional equivalent target application. Migration from COBOL solution to C# applications involves language translation, analysis of all artifacts required for modernization, system acceptance testing, and database and data transfer. While it’s optional, companies could need improvements such as coding improvements, SOA integration, clean up, screen redesign, and cloud deployment.

In May 2012 Google Chrome hit a milestone. It kicked Microsoft's Internet Explorer into excess phone oh that oh that second place as the most used browser on planet Earth.
With Microsoft being in second place, it makes a dark hole for Firefox coming in at number three. Google likes to trumpet three key reasons: security, simplicity and speed.
Available for free on Android, Linux, Mac, and Windows. It gets its speed from the open source JavaScript engine written in C++ known as V8.
In my daily use I use Microsoft's Internet Explorer version 10, Apple's Safari (on OS X) and chrome on both Windows 8 and OS X.

Admittedly people do not know anything about Internet Explorer version 10 since you can only get it on Windows 8/RT.

I do not need a crystal ball to know that the Mother of All Browser Battles is set to begin in the fall of 2012 and beyond.

I have said this before and I'm going to say it again.