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?

Planning on a little spring cleaning and getting rid of all those old electronics? With the way technology changes so quickly, it seems like we no sooner have one new electronic piece and there’s a new one on the market that we absolutely have to have. The result is a ton of used electronics stored away. Now it’s time to get rid of everything, here are some tips on what to do with all that old tech stuff and how to do it safely.

Save on Landfill Waste

Few people really realize where their electronics wind up when they throw them in the trash or dumpster. They assume they’re getting taken care of and just forget about them. According to the Environmental Protection Agency, one of the fastest growing components of landfill waste is electronics. The unfortunate part of this is that these electronics are filled with lead, mercury and other toxic chemicals – chemicals that find their way into our soil and water.

This results in the contamination of our lakes, streams and soil. The best way to avoid this is by knowing where your electronics are going and to dispose of them safely. Contact the recycling center in your area and ask for the best place to dispose of your old electronics.

Think of Security

Our lives are filled with electronic technology, whether it’s in the form of computers, tablets, smart phones or video games. Most of these electronics allow network sharing with people all over the world. With identity theft such a growing concern, much of our private lives and personal information is entered in the hard drives of these items.

Before you dispose of any electronics, make sure the hard drives are wiped clean of all personal information. This requires more than just “deleting” files. If you’re not sure how to correctly get rid of the information, contact a professional to do this for you. Even if you have to pay to have it done, it’s a minimal expense compared to having your private information stolen.

Find New Homes for Your Electronics

Once you’ve cleaned out your electronics of personal information, they may still be worth something to other individuals. You may know of a child or elderly person who would really appreciate a “new” computer or a tablet. Someone who has never owned a smart phone or laptop may be thrilled to suddenly own one, even if they are obsolete to you.

If you can’t find anyone that wants them, consider selling them on places like eBay, Craigslist or one of the many other online auction sites. The old saying, “one man’s junk is another man’s gold” is especially true when it comes to electronics. Many people like building computers using their own parts.

Students in computer-related programs also utilize used electronics as a form of hands-on training. Most schools also take in donated computers, televisions and cell phones. Contact your electric company or school district to get information on where you can take your old electronics. You’ll be not only cleaning out your house but also helping the environment.

Related:

Cloud Computing: What It Means and How It Could Threaten the Traditional Outsourcing Model

The importance of variables in any programming language can’t be emphasised enough. Even if you are a novice, the chances are good that you will have been using variables for quite a while now.

They are the cornerstone of any language and without them we would not be able to accomplish much of anything. However, most of you up until this point have probably only been working with standard variables, variables which can hold single values such as an integer, a single character, or a string of text.

In this tutorial we are going to take a look at a more special type of variable called an array. Arrays can seem quite daunting at first glance but once you get used to working with them you will wonder how you ever managed to program without them.

The reason arrays are special is because they can hold more than one value. Think about this: say you create a variable which contains a line of text like the code below:

Millions of people experienced the frustration and failures of the Obamacare website when it first launched. Because the code for the back end is not open source, the exact technicalities of the initial failings are tricky to determine. Many curious programmers and web designers have had time to examine the open source coding on the front end, however, leading to reasonable conclusions about the nature of the overall difficulties.

Lack of End to End Collaboration
The website was developed with multiple contractors for the front-end and back-end functions. The site also needed to be integrated with insurance companies, IRS servers, Homeland Security servers, and the Department of Veterans Affairs, all of whom had their own legacy systems. The large number of parties involved and the complex nature of the various components naturally complicated the testing and integration of each portion of the project.

The errors displayed, and occasionally the lack thereof, indicated an absence of coordination between the parties developing the separate components. A failed sign up attempt, for instance, often resulted in a page that displayed the header but had no content or failure message. A look at end user requests revealed that the database was unavailable. Clearly, the coding for the front end did not include errors for failures on the back end.

Bloat and the Abundance of Minor Issues
Obviously, numerous bugs were also an issue. The system required users to create passwords that included numbers, for example, but failed to disclose that on the form and in subsequent failure messages, leaving users baffled. In another issue, one of the pages intended to ask users to please wait or call instead, but the message and the phone information were accidentally commented out in the code.

While the front-end design has been cleared of blame for the most serious failures, bloat in the code did contribute to the early difficulties users experienced. The site design was heavy with Javascript and CSS files, and it was peppered with small coding errors that became particularly troublesome when users faced bottlenecks in traffic. Frequent typos throughout the code proved to be an additional embarrassment and were another indication of a troubled development process.

NoSQL Database
The NoSQL database is intended to allow for scalability and flexibility in the architecture of projects that will use it. This made NoSQL a logical choice for the health insurance exchange website. The newness of the technology, however, means personnel with expertise can be elusive. Database-related missteps were more likely the result of a lack of experienced administrators than with the technology itself. The choice of the NoSQL database was thus another complication in the development, but did not itself cause the failures.

Another factor of consequence is that the website was built with both agile and waterfall methodology elements. With agile methods for the front end and the waterfall methodology for the back end, streamlining was naturally going to suffer further difficulties. The disparate contractors, varied methods of software development, and an unrealistically short project time line all contributed to the coding failures of the website.