The short answer is, yes and no. It depends upon who you are. The purpose of this entry is to help you determine, yes or no.

Full disclosure. This entry is created on a Mac mini. And doing so on Windows 8 (Release Preview). If you are a developer, in my humble opinion you need to test on all platforms you expect your app to run or you are not much of a developer.

To be successful you need to leave politics in geographical territory known as Washington DC. My definition of that is: 14 mi.² of real estate surrounded by reality.

Only in politics can we afford to take sides. Those of us in IT, especially developers need to do our best to be all things to all people. Certainly this is a technical impossibility. However in our game we can get some points for at least being serviceable if not outstanding.

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.

Outsourcing IT needs in the corporate world has become extremely popular because it is cost-efficient and it gives IT resources to companies that may not otherwise be able to afford them. Another positive side effect of IT outsourcing is that it has brought many technology jobs back to the United States.

As convenient and patriotic as IT outsourcing has become, it also have several limitations that have caused many companies to re-think the idea of funding their own internal IT group. It is important for a company to be completely familiar with these limitations before developing any kind of company policy in regards to IT.

The Customer Could Outgrow The Outsource Company

When an IT outsourcing company first takes on a new client, the relationship is beneficial to both sides. But things can start to get inconvenient for the client when the client's business starts to outgrow the capabilities of the IT outsource group.

An IT outsourcing company can become entrenched in the daily routine of its clients, which is great at first. But when the IT company can no longer keep pace with the growth of its clients, then the clients are stuck trying to find a new solution and keep track of its own IT assets at the same time.

The IT Outsourcing Company Lacks The Necessary Technical Expertise

IT outsourcing clients like to believe that their support company knows everything there is to know about computers and the Internet. But every IT support company has its areas of expertise and they have the technical areas where they are not quite as strong. If the client starts to experience needs from the areas where the IT outsourcing company is not so strong, then that can become a significant business issue.

This problem can be amplified if the client is a small business experiencing growth. An IT outsourcing company is not as likely to bring on new personnel for a smaller client, which leaves the client without a solution.

The Client Losses A Measure Of Control Over Its Data

No matter how large or successful an IT outsourcing company may be, there will always be the limitation of client security and the protection of critical customer data. All it takes is one rogue employee of the IT outsourcing company to compromise all of the client's critical data.

Some IT outsourcing companies have safeguards put in place to try and prevent client data compromise, but those safeguards are limited by how much access the IT company has to the client network. In most cases, that access has to be comprehensive for the IT outsourcing company to be able to do its job.

Outsourcing IT responsibilities can take a lot of stress off of a client and allow that client to operate his business by focusing on his core competencies. But there are limitations to IT outsourcing that could make it necessary for a client to do his own IT support and pay the extra costs.

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.