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!

Facebook has recently released a collection of C++ software modules that it uses to run the popular website.  With Facebook releasing Folly (the name it designated for the collection), more of the internal programs could become open source since they need different parts of the collection.

Jordan DeLong, a Facebook software engineer, said one concerning holdup to releasing additional work is that any open source project had to cut away from the dependencies on non-released internal collection code.

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.

Is it possible for anyone to give Microsoft a fair trial? The first half of 2012 is in the history books. Yet the firm still cannot seem to shake the public opinion as The Evil Empire that produces crap code.

I am in a unique position. I joined the orbit of Microsoft in 1973 after the Army decided it didn't need photographers flying around in helicopters in Vietnam anymore. I was sent to Fort Lewis and assigned to 9th Finance because I had a smattering of knowledge about computers. And the Army was going to a computerized payroll system.

Bill and Paul used the University of Washington's VAX PDP computer to create BASIC for the Altair computer. Certainly laughable by today's standards, it is the very roots of the home computer.

Microsoft became successful because it delivered what people wanted.