Every programming language has a mechanism to allow the programmer to create variables which hold custom data entered in by either the coder themselves or by the user of the application.

Regardless of whether you’re new to programming or not, you will have used variables and you should understand that in javascript they can hold any value such as a number or a string of text.

There is also another type of variable called an Array. Now, depending on who you talk to, some will say an array is actually an object, while others say it is a variable. Neither one is wrong but for the sake of simplicity we’ll refer to it as a variable.

Now, arrays are special because they can hold multiple values as opposed to standard variables which can only hold a single value at one time. If you can, try and imagine that your computer’s memory is made up of thousands of little boxes, and each of those boxes has an address which javascript will use to retrieve the array values when needed.

In most business circles, the question of whether or not a website truly helps a company's business has become somewhat moot. Simply put, a website is a necessary evil, like it or not. The question is no longer, should a company have a website, but rather, is the website optimized to ensure the best potential results. Of course, it is important to understand what is meant by "helping a company."

Many businesses are under the assumption that a website is going to turn into cold hard cash for the company. Well, that could be the case if the organization is using a type of e-commerce platform to buy and sell goods. Many businesses are service oriented and as such, the website serves an entirely different purpose.

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.