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.

Facebook was originally intended as a way for people to stay in touch with friends and family members by sharing pictures and status updates on their timeline. As the website's popularity has grown, so has criticism that it is becoming one giant, online high school.

Online Bullying

There has been a dramatic increase in recent years in the number of online bullying cases due to the introduction of social media. Bullying isn't just limited to younger Facebook users, either. Many adult users have also resorted to bashing others online through nasty status updates and cruel comments.

Prior to social media, bullying in high school involved "kick me" signs and toilet swirling. Facebook and other social media outlets have allowed users to take bullying to a whole other level. Victims can no longer escape bullying by leaving school or work. The torture continues online, at anytime and anyplace.

Status "Likes"

In high school, everyone wants to be part of the popular crowd; people who are outgoing, beautiful, and seem like they have everything.  Posting a status update is similar to wanting to be popular. Once an update is posted, many users wait with bated breath to see how many friends will "like" their status. They believe that the more "likes" they receive, the more popular they are.

If that isn’t enough, there are many Facebook games that involve "liking" someone's status. Games like "Truth Is", where someone likes a status update and in return the poster writes how they really feel about the friend on their Facebook wall. This can get touchy, especially if the two people aren't friends outside of Facebook. It's similar to high school where someone desperately wants another person to like them, but when they find out how that person really feels they are crushed.

Relationships Are Difficult to Keep Private

When someone signs up for Facebook they’re asked to complete their profile, which includes a relationship section. Users can select from different options including "single", "married", "widowed", and "divorced". Whenever someone changes their relationship status, the update shows up on each of their friend's news feeds.

It's easy to see how this feature correlates with high school where everyone talks about who is dating who or which couple broke up. It used to be that after graduation, people were able to keep their relationships more to themselves. Not so anymore in the age of social media. Now everyone has the ability to state their opinion on a friend's relationship status, either by "liking" their status change or by commenting on it.

Facebook has presented many benefits to its users, including the ability to rekindle old high school friendships. What one must understand when they sign up for the service is that they are opening themselves up to the same criticism and drama that takes place in a high school setting.

Proceed with caution!

I will begin our blog on Java Tutorial with an incredibly important aspect of java development:  memory management.  The importance of this topic should not be minimized as an application's performance and footprint size are at stake.

From the outset, the Java Virtual Machine (JVM) manages memory via a mechanism known as Garbage Collection (GC).  The Garbage collector

• Manages the heap memory.   All obects are stored on the heap; therefore, all objects are managed.  The keyword, new, allocates the requisite memory to instantiate an object and places the newly allocated memory on the heap.  This object is marked as live until it is no longer being reference.
• Deallocates or reclaims those objects that are no longer being referened. 
• Traditionally, employs a Mark and Sweep algorithm.  In the mark phase, the collector identifies which objects are still alive.  The sweep phase identifies objects that are no longer alive.
• Deallocates the memory of objects that are not marked as live.
• Is automatically run by the JVM and not explicitely called by the Java developer.  Unlike languages such as C++, the Java developer has no explict control over memory management.
• Does not manage the stack.  Local primitive types and local object references are not managed by the GC.

So if the Java developer has no control over memory management, why even worry about the GC?  It turns out that memory management is an integral part of an application's performance, all things being equal.  The more memory that is required for the application to run, the greater the likelihood that computational efficiency suffers. To that end, the developer has to take into account the amount of memory being allocated when writing code.  This translates into the amount of heap memory being consumed.

Memory is split into two types:  stack and heap.  Stack memory is memory set aside for a thread of execution e.g. a function.  When a function is called, a block of memory is reserved for those variables local to the function, provided that they are either a type of Java primitive or an object reference.  Upon runtime completion of the function call, the reserved memory block is now available for the next thread of execution.  Heap memory, on the otherhand, is dynamically allocated.  That is, there is no set pattern for allocating or deallocating this memory.  Therefore, keeping track or managing this type of memory is a complicated process. In Java, such memory is allocated when instantiating an object:

String s = new String();  // new operator being employed
String m = "A String";    /* object instantiated by the JVM and then being set to a value.  The JVM
calls the new operator */