The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy.  Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

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.

No industry is as global as software development.  Pervasive networking means that software developers can, and do, work from anywhere. This has led many businesses to hiring development subcontractors in other countries, aiming to find good development talent at lower prices, or with fewer hassles on entry into the US.

While this is an ongoing and dynamic equilibrium, there are compelling reasons for doing software development in the United States, or using a hybrid model where some parts of the task are parceled out to foreign contractors and some are handled locally.

Development Methodologies

The primary reason for developing software overseas is cost reduction. The primary argument against overseas software development is slower development cycles. When software still used the "waterfall" industrial process for project management (where everything is budgeted in terms of time at the beginning of the project), offshoring was quite compelling. As more companies emulate Google and Facebook's process of "release early, update often, and refine from user feedback," an increasing premium has been put on software teams that are small enough to be agile (indeed, the development process is called Agile Development), and centralized enough, in terms of time zones, that collaborators can work together. This has made both Google and Facebook leaders in US-based software development, though they both still maintain teams of developers in other countries tasked with specific projects.

Localization For Americans

The United States is still one of the major markets for software development, and projects aimed at American customers needs to meet cultural norms. This applies to any country, not just the U.S. This puts a premium on software developers who aren't just fluent in English, but native speakers, and who understand American culture. While it's possible (and even likely) to make server-side software, and management utilities that can get by with terse, fractured English, anything that's enterprise-facing or consumer-facing requires more work on polish and presentation than is practical using outsourced developers. There is a reason why the leaders in software User Interface development are all US-based companies, and that's because consumer-focused design is still an overwhelming US advantage.

Ongoing Concerns

The primary concern for American software development is talent production. The US secondary education system produces a much smaller percentage of students with a solid math and engineering background, and while US universities lead the world in their computer science and engineering curricula, slightly under half of all of those graduates are from foreign countries, because American students don't take the course loads needed to succeed in them. Software development companies in the United States are deeply concerned about getting enough engineers and programmers out of the US university system. Some, such as Google, are trying to get programmers hooked on logical problem solving at a young age, with the Summer of Code programs. Others, like Microsoft, offer scholarships for computer science degrees.

Overall, the changes in project management methodologies mean that the US is the current leader in software development, and so long as the primary market for software remains English and American-centric, that's going to remain true. That trend is far from guaranteed, and in the world of software, things can change quickly.