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.

With the rise of the smart phone, many people who have long seen themselves as non-gamers have began to download and play to occupy themselves throughout the day. If you're a game developer who has a history of writing your code in C#, then perhaps this still emerging market is something you should consider taking advantage of. This, however, will require the familiarization with other programming languages.

One option for moving away from the C# language is to learn Java. Java is the programming used for apps on the android platform, billions of phones run on this programming language.

If you want to break into the android market, then learning Java is an absolute must.

There are both some pros and some cons to learning java. Firstly, if you already know C# or other languages and understand how they work, then java will be relatively easy to learn due to having similar, but quite simplified, syntax to C-based languages, the class library is large and standardized, but also very well written, and you might find that it will improve the performance and portability of your creations. Not to mention, learning java opens you up to the entirety of the android app and game market, a very large and still growing market that would otherwise stay closed off to you. That's too much ad and sale money to risk missing out on.

The few cons that come with learning the language is that, when coming from other languages, the syntax may take some getting used to. This is true for most languages. The other problem is that you must be careful with the specifics of how you write your code. While java can be written in a very streamlined fashion, it's also possible to write working, but bulky, code that will slow down your programs. Practice makes perfect, and the knowledge to avoid such pitfalls within the language.

If you wish to develop for the iOS on the other hand, knowledge of Objective C is required. The most compelling reason to learn Objective C is the market that it will open you up to. According to the website AndroidAuthority.com, in the article "Google play vs. Apple app store", users of iPhones and other iOS devices are much more likely to spend money on apps rather than downloading free ones.

Though learning Objective C might be a far jump from someone who currently writes in C#, it's certainly learn-able with a little bit of practice.

How do top programmers work?

What are a few unique pieces of career advice that nobody ever mentions?

Good non-programmer jobs for people with software developer experience

There has been and continues to be a plethora of observational studies by different researchers in the publishing industry focused on how e-books have affected hard-copy book sales. Evidence from these studies has indicated that there is a significant and monumental shift away from hard-copy books to e-books.[1]These findings precipitate fears that hard-copy books might become more expensive in the near future as they begin to be less available.  This scenario could escalate to the point where only collectors of hard-copy books are willing to pay the high price for ownership.

The founder of Amazon, Jeff Bezos, made a statement in July 2010 that sales of digital books had significantly outstripped U.S. sales of hard-copy. He claimed that Amazon had sold 143 digital books for its e-reader, the Kindle, for every 100 hard-back books over the past three months. The pace of this change was unprecedented;  Amazon said that in the four weeks of June 2010, the rate of sales had reached 180 e-books for every 100 hard-backs sold. Bezos said sales of the Kindle and e-books had reached a "tipping point", with five authors including Steig Larsson, the writer of Girl with a Dragon Tattoo, and Stephenie Meyer, who penned the Twilight series, each selling more than 500,000 digital books.[2] Earlier in July 2010, Hachette said that James Patterson had sold 1.1m e-books to date.

According to a report made by Publishers Weekly, for the first quarter of 2011, e-book sales were up 159.8%; netting sales of $233.1 million. Although adult hard-cover and mass market paperback hard-copies had continued to sell, posting gains in March, all the print segments had declined for the first quarter with the nine mass market houses that report sales. Their findings revealed a 23.4% sales decline, and that children’s paper-back publishers had also declined by 24.1%.[3] E-book sales easily out-distanced mass market paperback sales in the first quarter of 2011 with mass market sales of hard-copy books falling to $123.3 million compared to e-books’ $233.1 million in sales.

According to .net sales report by the March Association of American Publishers (AAP) which collected data and statistics from 1,189 publishers, the adult e-Book sales were $282.3 million in comparison to adult hard-cover book sales which counted $229.6 million during the first quarter of 2012. During the same period in 2011, eBooks revenues were $220.4 million.[4] These reports indicate a disconcerting diminishing demand for hard-copy books.