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.

Getting involved with the IT, or Internet Technology industry, is a way for you to break into a variety of potential coveted career paths and job openings. Whether you prefer working with the back-end of programming or if you enjoy improve user experience while browsing online, there are many different in-demand IT skills that are useful to obtain today if you are seeking a career in the tech industry yourself.

Cloud Computing

Working with cloud computing, otherwise known as "the cloud", requires you to work within various types of servers that store and access data globally from any location. With the increase in mobile usage, cloud computing is becoming even more prevalent in today's society. When you want to work with cloud computing, understanding the basics of programming and network security is a must. Working in cloud computing is a way to help with building new applications, expanding companies online as well as allowing anyone internationally to locate and access a specific blog, website or mobile app.

UX Design

UX Design is also known as user experience design. A user experience designer specializes in understanding the usability and overall experience a web visitor has when browsing on a site or blog. UX design is essential to ensure that all visitors on a website are capable of navigating the blog properly and accessing the site's content with ease, regardless of the browser they are using or the type of device that is being used to access the site itself. Cross-browser compatibility and ensuring that all websites you are working with are accessible via mobile platforms is another responsibility of many UX designers today. Working in UX design is highly recommended if you believe you have an eye for "good" web design and if you have an interest in improving the overall experience web users for a specific audience have when visiting the blog or website you represent or that you are building for yourself.

IT Security

IT security is one of the fastest-growing positions throughout the entire IT industry and field. IT security requires you to understand network infrastructures as well as how to properly manage each server individually to provide security and protection from potential hackers and online thieves looking to steal sensitive data and information. Maintaining the security of a network and all servers for a company is only becoming more popular with the expansion of mobile phone usage along with the growth of the Internet altogether.

Understanding the variety of IT skills that are in demand today can help you to better decide on a path that is right for you. The more you understand about various IT skills, the easier it is to find a position or career in your future that is most suitable for the type of work you enjoy. Whether you are looking to develop new apps or if you are interested in managing the security of company servers, there are hundreds of positions and skills that are in demand in the IT industry today.

Password Management Tools

What are the best languages for getting into functional programming?

Net Neutrality for the Layperson

What little habits make you a better software engineer?

Let’s face it, fad or not, companies are starting to ask themselves how they could possibly use machine learning and AI technologies in their organization. Many are being lured by the promise of profits by discovering winning patterns with algorithms that will enable solid predictions… The reality is that most technology and business professionals do not have sufficient understanding of how machine learning works and where it can be applied.  For a lot of firms, the focus still tends to be on small-scale changes instead of focusing on what really matters…tackling their approach to machine learning.

In the recent Wall Street Journal article, Machine Learning at Scale Remains Elusive for Many Firms, Steven Norton captures interesting comments from the industry’s data science experts. In the article, he quotes panelists from the MIT Digital Economy Conference in NYC, on businesses current practices with AI and machine learning. All agree on the fact that, for all the talk of Machine Learning and AI’s potential in the enterprise, many firms aren’t yet equipped to take advantage of it fully.

Panelist,  Michael Chui, partner at McKinsey Global Institute states that “If a company just mechanically says OK, I’ll automate this little activity here and this little activity there, rather than re-thinking the entire process and how it can be enabled by technology, they usually get very little value out of it. “Few companies have deployed these technologies in a core business process or at scale.”

Panelist, Hilary Mason, general manager at Cloudera Inc., had this to say, “With very few exceptions, every company we work with wants to start with a cost-savings application of automation.” “Most organizations are not set up to do this well.”

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?